Cannot Log In To Srvrmgr In Siebel 2017 and Later After Migration Installation From Pre-2017 Version
(Doc ID 2376212.1)
Last updated on AUGUST 27, 2024
Applies to:
Siebel CRM - Version 17.5 [IP2017] and laterInformation in this document applies to any platform.
Symptoms
Unable to connect to Server Manager (srvrmgr) after migration installation of Siebel 2017 or later on existing pre-2017 environment
srvrmgr.log:
GenericLog GenericError 1 000000025aaa4f50:0 2018-03-15 13:40:27 ($Header: (1191) err=1181597 sys=0) SBL-NET-01949: Failed to establish TLS connection.
NameServerLayerLog Error 1 000000025aaa4f50:0 2018-03-15 13:40:27 -143357728: [cgclientservice] TLS handshake to gateway failed hostname26:3330
GenericLog GenericError 1 000000025aaa4f50:0 2018-03-15 13:40:27 (scmnsclnt.cpp (135) err=2555922 sys=0) SBL-SCM-00018: Could not open connection to Siebel Gateway configuration store (hostname26:3330).
GenericLog GenericError 1 000000025aaa4f50:0 2018-03-15 13:40:27 (scmobj.cpp (211) err=2555922 sys=0) SBL-SCM-00018: Could not open connection to Siebel Gateway configuration store (hostname26:3330).
GenericLog GenericError 1 000000025aaa4f50:0 2018-03-15 13:40:27 (srsctx.cpp (275) err=2555922 sys=0) SBL-SCM-00018: Could not open connection to Siebel Gateway configuration store (hostname26:3330).
The issue can be reproduced with following steps:
1. Install Siebel 2017 or later on top of existing Siebel 15.6 environemnt
2. Log in to srvrmgr using the below command and error reported.
srvrmgr /g gatewayhostanme:tlsport /e esia17 /u sadmin /p password
Changes
Installed Siebel 2017 or later as migration installation on top of existing pre-2017 environment
Cause
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
Symptoms |
Changes |
Cause |
Solution |