SBL-ADM-01043: Server connect string is stale, desired server not available

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.2 [18325] Com/Med
Database: Oracle 9.2.0.4
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9

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

Symptoms

SBL-ADM-01043

Siebel Tech

On eComm PROD servers , below error is ocurring in the enterprise log files.

ServerLog       ProcessExit     1       0       2005-04-25 06:15:11     ServerMgr       44223     SBL-ADM-01043   Process exited with error - Server connect string is stale, desired server not available

ServerLog       ProcessExit     1       0       2005-04-25 09:15:11     ServerMgr       44233     SBL-ADM-01043   Process exited with error - Server connect string is stale, desired server not available

ServerLog       ProcessExit     1       0       2005-04-25 12:15:11     ServerMgr       44252     SBL-ADM-01043   Process exited with error - Server connect string is stale, desired server not available"



I have uploaded the enterprise log now and the individual ServerManager tasks logs.

Solution

Message 1

For the benefit of other users,

It was found out that the root cause of ' SBL-ADM-01043' errors in Enterprise log for Server Manager was due to cron job which customer set in order to take a backup of siebns.dat every 15 min. Once they switched off this job, above mentioned error stopped occuring.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Oracle 9.2.0.6
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8

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

Symptoms

SBL-ADM-01043

Hello,

The additional Production siebel server 7722 was installed on Unix.
The some tasks for Server Manager have "Exited" status.
The log: SBL-ADM-01043: Server connect string is stale, desired server not available.

I increased the events for the component but i haven't get any + information.
Please find attached log files.

Solution

Message 1

For the benefit of other readers,

from the siebns.dat file it was found that one of the Siebel servers within the enterprise was not shutdown correctly, because for the ServerMgr component the "Connect Strings" parameter was still set, for example to     "Machine_name:TCPIP:49163:SMI:NONE:NONE:NONE"

In this particular case the affected server was no longer used and after removing the server with
    srvredit -g SiebelGateway -e SiebelEnterprise -s SiebelServer -x \$Server
the error message was no longer seen.

Keywords : SBL-ADM-01043, Server connect string is stale, desired server not available, srvredit, server manager, srvrmgr

Applies to:

Product Release: V7 (Enterprise)
Version: 7.8.2.4 [19224] FRA Fin Svcs
Database: Oracle 10.1.0.4
Application Server OS: Sun Solaris 10
Database Server OS: Sun Solaris 10

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

Symptoms

SBL-SVC-00163, SBL-ADM-02044

Hello,

We want to encrypt the CTI users password that is stored into Siebel Oracle database :
-> BusComp CommSrv CM Agent General Profile / Field Password
-> Table S_USER / Column CTI_PWD

To perform the requirement, we intend to follow instructions from Bookshelf 'Security Guide' / 'Communication & Data Encryption'. But we are not sure about the roadmap, so could you please confirm that the above mentionned steps are correct and necessary :

1. Turn on Encryption for BusComp fields
    -> Create column S_USER.X_CTIPWD_ENCRPKEY_REF as Varchar30
    -> Create fields in CommSrv CM Agent General Profile
        -> I1_CTI Password Key Index = S_USER.X_CTIPWD_ENCRPKEY_REF
        -> I1_CTI Password Read Only = Calc field w/o calculated Value (as it is defined in Quote BusComp)
    -> Add User Properties for Password field
        -> Encrypted = Y
        -> Encrypt Service Name = RC2 Encryption
        -> Encrypt Key Field = I1_CTI Password Key Index
        -> Encrypt Read Only Field = I1_CTI Password Read Only

2. Run Key Database Manager

Are the steps, and their order, correct ? Do we miss some step or add unnecessary steps ?
We would like to secure this encryption operation because we fear some regressions in our development environment...

Best Regards,
Emmanuel

Solution

Message 1

For the benefits of the others:

Customer’s configuration was correct, however he run into the following issue when running the keydbmgr utility:
keydbmgr /u sadmin /p sadmin /l enu /c /devapp/FR/siebelfr/current/siebsrvr/bin/fra/fins.cfg

Please choose one of the following options:
   Enter 1 to change the key database password
   Enter 2 to add a key to the system
   Enter 3 to quit the application
>2
Please enter the seed for a new key generation:PIPOPIPO

A new key has been added successfully.

Please choose one of the following options:
   Enter 1 to change the key database password
   Enter 2 to add a key to the system
   Enter 3 to quit the application
>3
Updating key database...

Error: Fail to complete the key cache version updating operation.
Cleaning up... this may take a while.

Here is what was in the keydbmgr.log:

2021 2007-02-15 19:56:00 2007-02-15 19:56:02 +0100 00000003 001 003f 0001 09 keydbmgr 11031 1 /devapp/FR/siebelfr/7.8.2/siebsrvr/log/keydbmgr.log 7.8.2.4 [19224] ENU
GenericLog    GenericError    1    0    2007-02-15 19:56:00    (sasess.cpp (701) err=1801004 sys=901043) SBL-NET-01004: Internal: invalid connect string (DB instance)
GenericLog    GenericError    1    0    2007-02-15 19:56:00    (sasess.cpp (701) err=901043 sys=0) SBL-ADM-01043: Server connect string is stale, desired server not available

Message 2

After some testing in my environment I was able to reproduce the error. However even though I get the error " Error: Fail to complete the key cache version updating operation" when I try to add a key, the key is added successfully and encryption is working.

Change Request #12-17B65FB has been logged for this error.


However, encryption was not working for the customer, so he was advised to check the following:
1. When running keydbmgr, that there gateway server is up and running
2. Data Source in the configuration file used by the keydbmanager has the correct connection information.
3. That all parameters in the cfg file (DataSource, ClientRootDir , Gateway) are correct.
4. Change the DataSourceName in the cfg file (customer had it set toLocal):
[DBSecAdpt]
SecAdptDllName = sscfsadb
DataSourceName = ServerDataSrc

After making changes to the cfg file, as per above, the data encryption started working.