Siebel Application Is Giving Server Busy Error After Enabling SISNAPI TLS from Siebel 17.x & Later
(Doc ID 2556213.1)
Last updated on FEBRUARY 14, 2024
Applies to:
Siebel CRM - Version 19.2 and laterInformation in this document applies to any platform.
Symptoms
After enabling SISNAPI SSL as per Siebel Security Guide, Siebel application is not accessible. It is giving server busy error and log contains below errors:
UCM Object Manager: (UCMObjMgr_enu_0040_41943043_IP19.log
GenericLog GenericError 1 000000075cf96f8c:0 2019-06-07 03:42:44 ($Header: (1191) err=1181201 sys=0) SBL-NET-01553: Failed to establish SSL connection.
GenericLog GenericError 1 000000075cf96f8c:0 2019-06-07 03:42:44 (smimtpool.cpp (469) err=1376284 sys=0) SBL-SMI-00028: Internal: Failed to get the HELLO acknowledge
SisnTcpIp SisnSockError 1 000000075cf96f8c:0 2019-06-07 03:42:44 1674578800: [TCPIP-server] send() failed for sd=-1 (err=9 | Bad file descriptor)
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create server certificates
2. Updated siebel parameters using srvrmgr or GUI at Siebel server parameters or enterprise parameters:
-
Certificate File Name (CertFileName)
-
Certificate Authority (CA) Certificate File Name
Private Key File Name
-
Private Key File Password
- set the Communication Transport parameter (alias CommType) to TLS as appropriate for each Application Object Manager that is to use TLS
3. Re-start servers
Changes
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 |