I was trying to migrate one of my BSO outline to ASO and in the process, EAS on a sudden stopped working.
I checked the logs and found some strange error messages in the log.
weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider
………………………………………………………………………………………
Caused By: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider
…………………………………………………………………….
Caused By: oracle.security.jps.service.credstore.CredStoreException: PKI-02002: Unable to open the wallet. Check password.
I thought of restarting the server and when the server was up, Foundation Services stopped working with the same error.
If you come across the same error. (This resolution is provided in Oracle Support)
You will need to delete the corrupted wallet file and recreate it using the following steps:
I checked the logs and found some strange error messages in the log.
weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider
………………………………………………………………………………………
Caused By: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider
…………………………………………………………………….
Caused By: oracle.security.jps.service.credstore.CredStoreException: PKI-02002: Unable to open the wallet. Check password.
I thought of restarting the server and when the server was up, Foundation Services stopped working with the same error.
If you come across the same error. (This resolution is provided in Oracle Support)
You will need to delete the corrupted wallet file and recreate it using the following steps:
- Locate the WebLogic wallet file “cwallet.sso” located in %ORACLE_MIDDLEWARE_HOME%/user_projects/domains/EPMSystem/config/fmwconfig/
- Remove the cwallet.sso
- Re-create the wallet file using orapki utility, for example:
%ORACLE_MIDDLEWARE_HOME%/oracle_common/bin/orapki wallet create -wallet %ORACLE_MIDDLEWARE_HOME%/user_projects/domains/EPMSystem/config/fmwconfig -auto_login_only - Re-start the EPM Web Applications.
Thought of sharing this with wider audience 😉
I always encounter that error as well. It's nice to know how to deal with it. Thanks.
business consulting company
I've been having this kind of error lately, thanks for sharing this. I hope it will work for me.
What is the secret enable a person to delete the cwallet.sso file?
I have seen this occur as a bug if the hard drive has reached its full capacity where Essbase lives.
You can also copy an older cwallet.sso file from one of the other directories. Search for cwallet.sso, and you'll find several instances. The one that is corrupt is generally 0 bytes. Any of the locked cwallet.sso files should work, but in general several are created upon original installation, so if you know the services were logging in and staying stable when installed, then anything with that date as a timestamp should work.