Thursday, October 1, 2015

Weblogic Admin Failed During Startup due to


Boot identity file got corrupted.


Logs : $DOMAIN_NAME/servers/AdminServer/logs/AdminServer.out

<Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file ( is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.


“” files contains the username and password details in encrypted format.
There could be various reasons for above errors-
  1. Weblogic user password got changed.
  2. file got corrupted.
  3. Someone must have modified the file.


Option 1)

Step 1) Tale backup of existing file and create a new one.
cd $DomainHome/servers/AdminServer/security
mv boot.properties_ORG
Enter i
ESC :wq!

Step 2) Start Weblogic Admin Server.
Once Admin server is up and running will be encrypted.

Note : Most of time server will get restarted without problem, but some time we have noticed that even if you give correct weblogic username and password in text format but Weblogic does not pick that information from this file. In that case please proceed with Option 2.

Option 2)

If Option 1 doesn’t work then follow below steps

Step 1) Tale backup of file
cd $DomainHome/servers/AdminServer/security
mv boot.properties_ORG

Step 2) Start Weblogic Admin Server using script without nohup.
Enter Weblogic Password when it asks.
It will create the file in background (in encrypted form) and server will come up.
Once server is up, then you can shut down the server (Press Ctrl C) and can start the server again using “nohup” command as background process.
$ nohup ./ &

No comments:

Post a Comment

Other Posts