Server Busy Error In AD URL But DB URL Is Opening Fine
(Doc ID 2090962.1)
Last updated on NOVEMBER 04, 2019
Applies to:Siebel CRM - Version 22.214.171.124 [IP2014] and later
Information in this document applies to any platform.
The enterprise is having 4X application servers,2 webservers, 2 gateway servers in which eRetail oM is being configured for DB authentication and eConsumerSector has been configured as AD authentication. This is a non-prod environment(UAT) and we have done DB refresh from Production recently. After that while opening AD URL but DB authenticated URL is opening fine.
Server Busy Error in AD URL but DB URL is opening fine
In OM logs, error message
SBL-DAT-00254: The username you have entered is invalid. Please try to log on again or contact your system administrator for assistance.
SBL-DAT-00546: The user-context could not be established. Something is wrong with the assigned primary position or login related repository objects. See additional error messages for more information.
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