Search This Blog

SBL-ADM-02044: No connections found to any active servers.

Applies to:

Product Release: V7 (Professional)
Version: 7.5.3.5 [16183]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Sun Solaris 8

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

Symptoms

SBL-CSO-01031, SBL-ADM-01105, SBL-ADM-01108

I work for expert service and i am helping the customer. They get this following error message whenever they go to Server -configuration screen.
Hi All

I am at a customer site and everytime sadmin uses server - configuration the following error message appears in the srvrmgr log.

Log file :

GenericLog GenericError 1 0 2004-07-08 12:18:12 (ss2klogapi.cpp (2362) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:12 (ss2klogapi.cpp (2080) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:12 (ss2klogapi.cpp (2362) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:16 (ss2klogapi.cpp (2080) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:16 (ss2klogapi.cpp (2362) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:16 (ss2klogapi.cpp (2080) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:16 (ss2klogapi.cpp (2362) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:16 (ss2klogapi.cpp (2080) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:16 (ss2klogapi.cpp (2362) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:17 (ss2klogapi.cpp (2080) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:17 (ss2klogapi.cpp (2362) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 ...

Solution

Message 1

For the benefit of other users:

I was able to reproduce this behavior in our internal 7.7.1 [18306] environment. I created a change request (12-N2L48T) to address this behavior. This change request will be appropriately prioritized and addressed in a future release.

I researched on any workaround (e.g: increasing event log levels) that could help eliminate these errors. Unfortunately, these errors do come up with all the event log levels – hence there is no workaround available. However, as SBL-ADM-01108 and SBL-ADM-01105 are benign errors, none of your other functionality would be affected because of these errors. Please continue to ignore these errors and educate your administrators to do the same.

Thank you,

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.


No comments:

Post a Comment