<4-Dec-2007 5:13:18 o'clock PM GMT+05:30> <Critical> <Security> <BEA-090402> <Au thentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may ha ve 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 fir st time the updated boot identity file is used to start the server, these new va lues are encrypted.> <4-Dec-2007 5:13:18 o'clock PM GMT+05:30> <Critical> <WebLogicServer> <BEA-00038 6> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationExc eption: Authentication denied: Boot identity not valid; The user name and/or pas sword from the boot identity file (boot.properties) is not valid. The boot ident ity 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 passwor d. The first time the updated boot identity file is used to start the server, th ese new values are encrypted. weblogic.security.SecurityInitializationException: Authentication denied: Boot i dentity not valid; The user name and/or password from the boot identity file (bo ot.properties) is not valid. The boot identity may have been changed since the b oot identity file was created. Please edit and update the boot identity file wit h the proper values of username and password. The first time the updated boot id entity file is used to start the server, these new values are encrypted. at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.do BootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:941) at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in itialize(CommonSecurityServiceManagerDelegateImpl.java:1029) at weblogic.security.service.SecurityServiceManager.initialize(SecurityS erviceManager.java:849) at weblogic.security.SecurityService.start(SecurityService.java:141) at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) Truncated. see log file for complete stacktrace > <4-Dec-2007 5:13:18 o'clock PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED> <4-Dec-2007 5:13:18 o'clock PM GMT+05:30> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down> <4-Dec-2007 5:13:18 o'clock PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
tried changing the boot properties and still not starting please provide your inputs or suggestions
Madusudhanan Ragothaman
Greenhorn
Joined: Dec 19, 2007
Posts: 6
posted
0
Open the boot.properties file.
Use your admin user name and password and save it. And then restart the server it should work fine.
The second time, it will be encripted.
This happens if you copy the domain files from another box.
madhuri rajan
Greenhorn
Joined: May 07, 2007
Posts: 28
posted
0
Any idea where i can find this boot.properties? I am using weblogic81
jigar vyas
Greenhorn
Joined: May 12, 2008
Posts: 3
posted
0
Originally posted by madhuri rajan: Any idea where i can find this boot.properties? I am using weblogic81
Hi, You can find the boot.properties in bea/user_projects/domains/your_domain directory. Thanks & Regards, Jigs.
Kaushik Yeleswarapu
Greenhorn
Joined: Aug 27, 2009
Posts: 5
posted
0
This error would occur incase you are having security realm setup on your weblogic server.
Go to Weblogic Admin console
Security Realms>myrealm > Providers >Adjudication> DefaultAdjudicator >Provider Specific
Uncheck Require Unanimous Permit
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.do
BootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:941)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
itialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:849
)
I have seen that many of us gets the same error at many time. What could be the possible scenario for this. ? any clue???
I then tried to change the admin user itself ( offline commands) and then admin server started fine . However managed server start up shows me the same error . Then i deleted the managed server directory so that it will get the copy of ldap from admin server. But error remain same.
@Deepak
Do you have any idea about this. How could server sub system failed.