User is not permitted to boot the server weblogic

Managed server was not starting up when we change the StartScriptEnabled=true In Nodemanager.properties.

Server logs shows below details:

<03/10/2012 12:37:20 PM EST> <Info> <Security> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server oim_server1 for security realm myrealm.>
<03/10/2012 12:37:20 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<03/10/2012 12:37:20 PM EST> <Critical> <Security> <BEA-090404> <User is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.>
<03/10/2012 12:37:20 PM EST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: User is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
weblogic.security.SecurityInitializationException: User is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.

at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:1009)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<03/10/2012 12:37:20 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<03/10/2012 12:37:20 PM EST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<03/10/2012 12:37:20 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

It works fine when we make the StartScriptEnabled=false in nodemanager.properties file.
This error occurs due to the StartScriptEnabled=false in nodemanager.properties file, it was basically picking up the username and password defined in the Weblogic Admin Console- Servers–Start Tab but when we change the value of StartScriptEnabled to TRUE then the server picks the username and password from server start up boot.properties. The boot.properties for servers starting in Production mode is not created by default.

To solve this error please follow below steps:

1) Enable the “Refresh Replica At StartUp” from weblogic admin console. Below is the path of the “Refresh Replica At StartUp”

Navigate to weblogic admin console ->Domain->Security->Embedded LDAP->Refresh Replica At StartUp

Since Security data (e.g., password) is stored in the Embedded LDAP by default and it is replicated from the admin server to the managed servers. If there is an inconsistency of the security data between the admin and managed servers, the error will occur.

Hence you have to refresh all replicated data at boot time, in order to do this you need to set ‘Refresh Replica At Startup’ from the Admin Console. This option specifies whether a Managed Server should refresh all replicated data at boot time.

2) Manually create a boot.properties under $Domain_Home/servers/<Managed_Server>/security/* and provide the same username and password which is used to login to the admin console.

Now you are ready to start the server from nodemanager using StartScriptEnabled=true In Nodemanager.properties.

In case of any ©Copyright or missing credits issue please check CopyRights page for faster resolutions.