Crashes observed when using ADSISecAdpt profile on IP2014 and trying to exit out of Server manager command prompt
(Doc ID 2186863.1)
Last updated on APRIL 01, 2019
Applies to:Siebel Consumer Goods - Version 18.104.22.168 [IP2014] and later
Information in this document applies to any platform.
On : 22.214.171.124 [IP2014 version
When attempting to exit out of the server manager command with gateway/Siebel server using ADSISecAdpt profile to connect to AD server, crashes like below were observed:
sslcshar +0x42fc5 = ccfThrdCtx::~ccfThrdCtx() +0x85
sslcshar +0x43b76 = ccfProgCtx::Initialize() +0x126
sslcshar +0x43a31 = ccfProgCtx::~ccfProgCtx() +0x11
sslcshar +0x68f38 = CcfGetHostname() +0x8f28
sslcshar +0x611a8 = CcfGetHostname() +0x1198
sslcshar +0x613ce = CcfGetHostname() +0x13be
sslcshar +0x612f8 = CcfGetHostname() +0x12e8
ntdll +0x545f6 = RtlAnsiStringToUnicodeString() +0x7a0
ntdll +0x54643 = RtlAnsiStringToUnicodeString() +0x7ed
ntdll +0x609a8 = LdrShutdownProcess() +0x105
ntdll +0x6088d = RtlExitUserProcess() +0x63
KERNEL32 +0x23a90 = ExitProcess() +0x13
MSVCR110 +0x2fb9c = strstr() +0x2f9
MSVCR110 +0x2fdee = cexit() +0x17c
MSVCR110 +0x2fe12 = exit() +0xf
sslcosd +0x12e1 = OSDProcExit() +0x21
siebsess +0x548c = SmiBeginTrace() +0x277c
KERNEL32 +0x28624 = BaseThreadInitThunk() +0xe
ntdll +0x5bd99 = RtlInitializeExceptionChain() +0x85
ntdll +0x5bd6c = RtlInitializeExceptionChain() +0x58
The issue can be reproduced at will with the following steps:
1. Setup Gateway Server and Siebel server to use ADSISecAdpt for AD authentication (for server admin view access)
2. Make sure that the ADSISecAdpt profile is defined correctly and test AD authentication to see if it is successful.
3. Connect to the server manager command prompt and try to invoke some commands.
4. Exit out of the Server manager command and check to see if there are any crash files in $SIEBEL_ROOT/siebsrvr/BIN directory with above call stack.
The issue has the following business impact:
Due to this issue, users are seeing many crashes due to invoking many server manager commands and this was causing a setback.
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