SBL-DAT-00587: An error occurred setting the default locale for the session. See additional error messages for more information.

Applies to:

Siebel System Software - Version: 8.x - Release: V8
Microsoft Windows Server 2003
Product Release: V8 (Enterprise)
Version: 8.0 [20405]
Database: Oracle 10.1.0.2
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: HP 9000 Series HP-UX

This document was previously published as Siebel SR 38-3392791581.

Symptoms

SBL-DAT-00587

When starting Tools, several developers are getting an error: An error occurred setting the default locale for the session. See additional error messages for more information.(SBL-DAT-00587). There were no more error messages following this first window. The Tools splash screen appears, the error window, and then Tools closes.

The happened after a repository upgrade and a fresh get was performed.

I will attached the log file.

Thanks!

Cause

The developer's local database might have been corrupted.

Solution

 

When starting Tools, several developers are getting the following error

“An error occurred setting the default locale for the session. See additional error messages for more information.(SBL-DAT-00587).”

For this customer, the issue was resolved after the customer re-extracted the developer's local database. The developer's local database might have been corrupted.

The error was not encountered anymore after the customer re-extracted the developer's local database.

Please log a Service Request if the same error is encountered but re-extracting the local database does not help or if there is any clarifications required and doubts regarding this issue.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221]
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.

Symptoms

SBL-DAT-00587, SBL-DAT-00178, SBL-DBC-00105, SBL-SVC-00208

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?

Solution

Message 1

For the benefit of other readers:

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.

Regards,

Oracle | Siebel Technical Support

Applies to:

Siebel System Software - Version: 7.5.3 [16157] to 8.1 [21039] - Release: V7 to V8
Information in this document applies to any platform.
Product Release: V7 (Enterprise)
Version: 7.5.3.15 [16279] Fin Svcs
Database: IBM DB2 8.1 FixPack 4a
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: IBM AIX 5L 5.3

This document was previously published as Siebel SR 38-3490548231.

Goal

Which version of Siebel Tools should be used to perform which upgrade steps?

Solution

When performing an upgrade, it is not always clear which version of Siebel Tools should be used to perform which steps of the upgrade.

Until the Upgrade Repository (UpgRep) process is complete, the newer version of Siebel Tools will not be able to connect to the Siebel database. The UpgRep process will modify the tables in the Siebel database to allow the new version of Siebel Tools to connect successfully.

Until the UpgRep is complete, using the newer version of Siebel Tools to connect to the database will result in an error. The prior version of Siebel Tools should be used to perform any upgrade steps before the UpgRep process is complete.

For example: SBL-DAT-00587 is received when logging in with 8.0 Tools to a 7.5 db