Skip to Main Content

SSO failing after moving catalog and repository

738807Dec 3 2009
As a test, we recently copied the repository and catalog files from one OBIEE server to another in development. The configuration of the servers is virtually identical. After the copy, SSO is no longer working on the second server. After the user authenticates, analytics gives a "Not Logged In" message. The error shows up like this in sawlog:

---------------------------------------
Type: Error
Severity: 40
Time: Wed Dec 02 16:18:45 2009
File: project/webodbcaccess/odbcconnectionimpl.cpp Line: 371
Properties: ConnId-1,1;ThreadID-3628
Location:
saw.odbc.connection.open
saw.connectionPool.getConnection
saw.subsystem.security.checkAuthenticationImpl
saw.threadPool
saw.threads

Odbc driver returned an error (SQLDriverConnectW).
State: 08004. Code: 10018. [NQODBC] [SQL_STATE: 08004] [nQSError: 10018] Access for the requested connection is refused.
[nQSError: 43001] Authentication failed for {user_name} in repository Star: invalid user/password. (08004)
---------------------------------------
Type: Error
Severity: 42
Time: Wed Dec 02 16:18:45 2009
File: project/webconnect/connection.cpp Line: 276
Properties: ThreadID-3628
Location:
saw.connectionPool.getConnection
saw.subsystem.security.checkAuthenticationImpl
saw.threadPool
saw.threads

Authentication Failure.
Odbc driver returned an error (SQLDriverConnectW).
---------------------------------------

The log doesn't actually say {user_name} - it shows the user ID of the authenticated user, so at least it's retrieving the ID of the user. Everything else seems to be functioning. The connection pools in the repository are connecting successfully. If you get into Analytics using a repository account like Administrator, the catalog objects are there and pulling the expected results.

Any ideas for why the SSO would be failing in that way?
Comments