Search found 2 matches

by folderol
21 Feb 2013, 14:51
Forum: Help
Topic: Invalid SessionID after Upgrade to 3.2.1
Replies: 4
Views: 4385

Re: Invalid SessionID after Upgrade to 3.2.1

The issue is fixed by executing the following query on the OTRS database in effect changing the data_value text encoding to binary (it basically behaves as a blob field then).

Code: Select all

ALTER TABLE sessions MODIFY data_value TEXT CHARACTER SET binary;
by folderol
21 Feb 2013, 14:21
Forum: Help
Topic: Invalid SessionID after Upgrade to 3.2.1
Replies: 4
Views: 4385

Re: Invalid SessionID after Upgrade to 3.2.1

After upgrading from OTRS 3.1.x to OTRS 3.2.2 Agent logins work but the Customer Frontend doesn't allow session creation anymore: [Thu Feb 21 11:31:16 2013][Error][Kernel::System::AuthSession::DB::CreateSessionID][333] Incorrect string value: '\x80\x00\x00\x00\x08C...' for column 'data_value' at row...