OBIEE 11g Error: Login Fails With 'The GUID (8fd96b1f8b4c47dca6992a8e12adb12d) For User xxxxxx Already Exists In The Catalog With Username Xxxxx Xxxxxx'
(Doc ID 1663436.1)
Last updated on AUGUST 18, 2021
Applies to:Business Intelligence Server Enterprise Edition - Version 18.104.22.168.12 and later
Information in this document applies to any platform.
Working through our implementation of our 11g environments and have been able to attach Weblogic to our AD server and pull our users in, but we are now seeing the following error when a user attempts to log in. This is because initially pulled in the user name, ex: FirstName LastName, instead of the AD account name, flastname. Was indeed able to log in with "FirstName LastName" with AD credentials, but when you change the Weblogic AD setup to pull in the account name and use that instead of the user name, you see that the user is authenticated but then there is an error.
GUIDs were refreshed and it had no effect.
The environment is configured with Active Directory LDAP as the authenticator.
An initial LDAP configuration was used when beginning the implementation. Later, the Active Directory LDAP was re-configured an the provider information changed to use the account name instead of the user name.
The following error now occurs:
"The GUID (8fd96b1f8b4c47dca6992a8e12adb12d) for user flastname already exists in the catalog with username FirstName LastName. The user and its home directory will be renamed now in the catalog."
The GUIDs have been refreshed.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document