Can't start Siebel Server after moving Gateway Server to different clustered node. (Doc ID 1476775.1)

Last updated on OCTOBER 14, 2016

Applies to:

Siebel CRM - Version 8.1.1 [21112] and later
Microsoft Windows x64 (64-bit) - Version: 2008 R2

Symptoms

 Can't start Siebel Server after moving Gateway Server to different clustered node.

Reproduce procedure is as follows,
1) Gateway Server is running on Node A and Siebel Server is running. No Problems.
2) Shutdown Siebel Server.
3) Shutdown the  Gateway Server on Node A
4) Move Gateway Server to Node B, and start it.
5) Startup Siebel Server, it fails.

NameSrvr.log (when starting Siebel Server):

SecAdptLog    Debug    5    00000003500816d8:0    2012-07-19 20:20:40    Invoking SecurityLogin with username=SADMIN ...
SecAdptLog    Debug    5    00000003500816d8:0    2012-07-19 20:20:40    ODBC security adapter configured: connectstring='', tableowner='', GlobalConnections=.
GenericLog    GenericError    1    00000003500816d8:0    2012-07-19 20:20:40    (secmgr.cpp (2697) err=4597538 sys=127) SBL-SEC-10018: data source connect string or table owner is empty.
GenericLog    GenericError    1    00000003500816d8:0    2012-07-19 20:20:40    (secmgr.cpp (2769) err=4597521 sys=0) SBL-SEC-10001: An internal error has occurred within the authentication subsystem for the Siebel application. Please contact your system administrator for assistance.
GenericLog    GenericError    1    00000003500816d8:0    2012-07-19 20:20:40    (client.cpp (313) err=4597521 sys=0) SBL-SEC-10001: An internal error has occurred within the authentication subsystem for the Siebel application. Please contact your system administrator for assistance.
SisnTcpIp    SisnSockError    1    00000003500816d8:0    2012-07-19 20:20:41      5236: [TCPIP-server] recv() failed for sd=-1 (err=10038 | Socket operation on non-socket (invalid socket handle).)
SisnTcpIp    SisnSockError    1    00000003500816d8:0    2012-07-19 20:20:41      5236: [TCPIP-server] send() failed for sd=-1 (err=10038 | Socket operation on non-socket (invalid socket handle).)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms