Applies to:Product Release: V7 (Enterprise)
Version: 188.8.131.52 
Database: Microsoft SQL Server 2005
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: Microsoft Windows 2003 Server SP2
This document was previously published as Siebel SR 38-3395412005.
On Monday night or Tuesday morning, our Siebel Server (Test) stopped responding.
We have stopped and restarted the App server services. Stopped and restarted MS SQL server. And cold rebooted the App, DB and WAS servers. Production is fine, and no recent changes were made to Test.
We keep getting a "The server you are trying to access is either busy or experiencing difficulties. Please close the Web browser, open a new browser window, and try logging in again.[15:28:01]" message, when trying to log onto http://ustemt232/sales_enu
All three servers appear to be in good shape at the Windows level, but because we can't even log into SADMIN, we are at a loss why we can't initiate a web session.
What can we look at to trouble shoot the problem?
The Object Manager log files provided by customer was writing the following errors:
SBL-DBC-00105: An error has occurred executing a Sql statement.
CAUSE: A SELECT SQL statement failed to be executed against the database server.
CORRECTIVE ACTION: Review the error message returned by the database, which should be logged in the Siebel log files. It is important to obtain the failing SQL statement as well but SQL statements are not logged unless SQL tracing is enabled.
SBL-DAT-00178: The Locale Code is invalid. Please check the value of the parameter LocaleCode for this component. A row corresponding to the Locale Code must exist in the S_LOCALE table.
SBL-DAT-00587:An error occurred setting the default locale for the session.
CAUSE: Could be caused by programming logic error or misconfiguration.
CORRECTIVE ACTION:Ensure the server parameter "Locale Code" is set to a valid 3 letter locale code.
SBL-SVC-00208:Please login first.
Based on the above errors, Siebel Technical Support suggested customer to check if the database user GUESTCST had sse_role. If not the dba should grant the guest user the sse_role and after that restart the Siebel services.
The following is what their DBA found:
The GUESTCST account had db_denydatareader checked. Then after removing it customer was able to log into Siebel Application.
Oracle | Siebel Technical Support