Unable to Access Siebel Application with Fresh Installation (Doc ID 2286961.1)

Last updated on NOVEMBER 12, 2019

Applies to:

Symptoms

Siebel server and swse installed on separate machines as fresh installation. While trying to access Siebel application, it is taking nearly one min and giving server busy error. There is no session created at Siebel server component level, request is not reaching to Siebel server. 

SWSE logs reported with below error message

ERROR
-----------------------
SessMgr ConnOpen 3 000000045969139c:0 2017-07-14 20:00:30 5088: [SESSMGR] Open(siebel.TCPIP.None.None://<SiebelAppServerHost>:2321/CDA_PRD/PSCcObjMgr_enu, 60, 300)

SisnTcpIp SisnSockWarning 2 000000045969139c:0 2017-07-14 20:00:51 5088: [TCPIP-client] connect() to <SiebelAppServerHost>:2321 failed (err=10060 | Connection timed out.)

SessMgr ConnOpen 3 000000045969139c:0 2017-07-14 20:00:51 5088: [SMCONN] Failed to open connection to (siebel.TCPIP.None.None://<SiebelAppServerHost>:2321/CDA_PRD/PSCcObjMgr_enu) in 21 sec(s)

GenericLog GenericError 1 000000045969139c:0 2017-07-14 20:00:51 (smconn.cpp (284) err=1180849 sys=10060) SBL-NET-01201: Internal: connect() failed: Connection timed out.

SisnTcpIp SisnSockDetail 4 000000045969139c:0 2017-07-14 20:00:51 5088: [TCPIP-client] socket() closed descriptor = 860 from :8451 to :8451

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.