SerializedSystemIni.Dat recover in Weblogic
While starting WebLogic Server fails to initialize and the following exception used to get thrown
<Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: weblogic.descriptor.ResourceUnavailableException: Missing SerializedSystemIni.dat> service failed. The server will shut itself down>
We came to know that SerializedSystemIni.dat is used for encryption/decryption of plain-text/ciphertext within a WebLogic domain.
If missing or corrupted, then the decryption failure prevents WebLogic from initializing.
Please follow the below steps to recover SerializedSystemIni.dat file:
1. Go to $DOMAIN_HOME/config folder and open the config.xml file and remove any encrypted sections from the <credential-encrypted> attributes.
2. Replace its content with “”.(NULL) and save the file.
3. Go to $DOMAIN_HOME/servers/AdminServer/security and remove the boot.properties file(if exists).
4. Go to $DOMAIN_HOME/security and remove SerializedSystemInit.dat.
5. Go to $DOMAIN_HOME and rename the fileRealm.properties to fileRealm.properties.src.
6. Open fileRealm.properties.src and Change all the hashed passwords (encrypted passwords) to clear text passwords and save the file.
For example:
user.system=0xaasmme787xs5ff739b5536904c to user.system=password
Notes: Use the same password that was set to the domain.
7. Open a terminal and go to $DOMAIN_HOME/bin and execute setDomainEnv.sh (or .cmd).
8. Once the domain env is setup correctly, execute (in the same open terminal) the following command to regenarate SerializedSystemIni.dat and fileRealm.properties files :
java weblogic.security.acl.internal.FileRealm fileRealm.properties SerializedSystemIni.dat
9. Once the above two files regenrated, open startWeblogic.sh located at $DOMAIN_HOME/bin and add below mentioned argument in JAVA_OPTIONS and saev the startWeblogic.sh file:
-Dweblogic.system.StoreBootIdentity=true
Note: This will recreate the boot.properties file.
10. Start Weblogic with startWeblogic.sh or startWeblogic.cmd and enter the user and password.
In case of any ©Copyright or missing credits issue please check CopyRights page for faster resolutions.
Hi.. nice tutorial on resetting the keys. However it is failing on my end. Complaining about credential-encrypted being empty.
Server failed. Reason: [Management:141266]Parsing failure in config.xml: java.lang.IllegalArgumentException: In production mode, it’s not allowed to set a clear text value to the property: CredentialEncrypted of SecurityConfigurationMBean.
Did all the steps… in the end when you start weblogic with startWebLogic.sh … it never prompts for username/password….?
Should I also have removed *.ldift files from $domain/security ? Might try that…. before I regenerate Serial.dat
Any other ideas?
Thanks!