After Siebel Update 21.2 or Later is Applied, "Can not initialize cryptographic mechanism" Error May Occur to Cause Various Issues.
(Doc ID 2782751.1)
Last updated on JUNE 08, 2021
Applies to:
Siebel CRM - Version 21.2 and laterInformation in this document applies to any platform.
Symptoms
After Siebel Update 21.2 or later is applied, following jar files may become out of sync to cause various issues. Here are some examples.
Case 1) Login to SMC fails with "The user ID or password that you entered is incorrect.", and Starting Siebel Server fails with the error SBL-SCM-00018.
Case 2) SMC login page cannot be accessed with the error "Unable to connect".
Error information for the case 1.
- SiebSrvr.log
While the actual log file can be either localhost.YYYY-MM-DD.log (for SES) or catalina.YYYY-MM-DD.log (for AI), both show "Can not initialize cryptographic mechanism" and "Policy files are specific per major JDK release.Ensure the correct version is installed"
Changes
Siebel Update 21.2 or later is applied on top of existing Siebel version.
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 |