Logon error in 1st attempt but works after 2nd attempt

[bensah]

I am getting the xml page where I can find the error as below.

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<SOAP-ENV:Fault>
<faultcode>Client</faultcode>
<faultstring>CM-REQ-4342 An error occurred with the client.</faultstring>
<detail>
<bus:exception>
<severity>error</severity>
<errorCode>caf</errorCode>
<bus:message>
<messageString>
CM-REQ-4159 Content Manager returned an error in the response header. The error "cmAuthenticateFailed CM-CAM-4005 Unable to authenticate. Check your security directory server connection and confirm the credentials entered at login." can be found in the response SOAP header.
</messageString>
</bus:message>

But when I am refreshing once again then login page is appearing.

It was fine before and not sure what was wrong now.
Appreciate any clue on it.

[smiley]

Could you try clearing your browser cache?

[bensah]

Thank you for your reply.

This is not the browser issue. we are getting the same issue across the globe.

we have recently activated SSO in our websphere. I am not sure if that is causing the issue or not.
We have not changed any cognos configuration.

Thanks,
Benu

[bensah]

This is fixed after changing the  Load Balancing Mode to Cluster Compatible.

Reason is explained the below url.

https://www.ibm.com/developerworks/data/library/cognos/infrastructure/cognos_specific/page510-pdf.pdf.

http://www-01.ibm.com/support/docview.wss?uid=swg21432682


Two alternative Solutions are available:
Solution 1 (Recommended)

1. Log into IBM Cognos Connection as an Administrator
2. In the upper-right corner, click Launch, IBM Cognos Administration.
3. On the Status tab, click System.
4. Click the arrow for the Actions menu next to System and click Set properties
5. Click the Settings tab.
6. Select Tuning from the Category list.
7. In the Value column, select the value for the Load Balancing Mode, Cluster Compatible
8. Click OK

The new value takes effect immediately.

Solution 2:
Turn off the Presentation Service In Cognos Configuration on the second dispatcher