Siebel Server Failing to Start With Logon Errors After UPGRADE to 8.1.1.14 / IP 2014 / IP 2015 or Higher
(Doc ID 2059597.1)
Last updated on MARCH 01, 2024
Applies to:
Siebel CRM - Version 16.0 [IP2016] and laterInformation in this document applies to any platform.
Symptoms
After upgrading from 8.1.1.11 to IP2014 or higher (IP2015 / IP2016 / IP2017) login is no longer possible
The <enterprise>.<siebelserver>.log file has logon errors for multiple components, e.g.
And a
that per this component's log is also caused by a login failure:
ServerLog LstnObjInherit 3 00005f4955e00394:0 2015-08-28 13:35:22 Inherited listening object for port 49157
ServerLog LstnObjPrivCreate 3 00005f6355e00394:0 2015-08-28 13:35:22 Created port 49162 for Server Request Processor
DBCLog DBCLogError 1 00005f6355e00394:0 2015-08-28 13:35:23 [Microsoft][SQL Native Client][SQL Server]Login failed for user 'SADMIN'.
Changes
IP 2014 / 8.1.1.14 and above use different encryption libraries (AES)
While the Siebel installer should create a new Siebel Server service with a correctly AES encrypted password allowing the Siebel Server to connect to the Gateway
the existing passwords in the Gateway Server's siebns.dat can no longer be decrypted and need to be set again (need to be "reencrypted" per bookshelf)
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 |
| What is the easiest way to check if SADMIN password was set at different levels |
| References |