If the ODBC/SQLError component is enabled in the Policy Server trace log, Single Logout Services may cause the following errors to be written to the trace log:
[13:42:44.0][CSmDbODBC.cpp:189][CSmDbConnectionODBC::MapResult][][][-1][[Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'PK__ss_sessionvar5__571DF1D5'. Cannot insert duplicate key in object 'ss_sessionvar5'.][][][] [13:42:44.0][CSmDbODBC.cpp:277][CSmDbConnectionODBC::MapResult][][Mapped Result: -1059 Error Message: "[Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'PK__ss_sessionvar5__571DF1D5'. Cannot insert duplicate key in object 'ss_sessionvar5'." SQL State: 23000.][][][][][] [13:42:44.0][CSmDbODBC.cpp:189][CSmDbConnectionODBC::MapResult][][][-1][[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been terminated.][][][] [13:42:44.0][CSmDbODBC.cpp:277][CSmDbConnectionODBC::MapResult][][Mapped Result: -1059 Error Message: "[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been terminated." SQL State: 01000.][][][][][] [13:42:44.0][CSmDbODBC.cpp:189][CSmDbConnectionODBC::MapResult][][][-1][][][][] [13:42:44.0][CSmDbODBC.cpp:277][CSmDbConnectionODBC::MapResult][][Mapped Result: -1059 Error Message: "" SQL State: .][][][][][]
This is normal and the data is ultimately written to the session server database.
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |