0 Replies Latest reply on Aug 18, 2010 3:50 AM by 684134

    Unable to boot weblogic admin server after updating the password for OIDAut

    684134
      Hi,

      I have installed webcenter on my weblogic 10.3 and used OID for authentication. It was working fine. I changed the OIDAuthenticator password for the admin user 'weblogic_wc' in admin console. Now I am not able to boot the admin server itself. I am getting the following error.

      ===============================================================

      ####<Aug 17, 2010 8:08:12 PM PDT> <Notice> <Security> <RTDC79689VMC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1282100892730> <BEA-090082> <Security initializing using security realm myrealm.>
      ####<Aug 17, 2010 8:08:13 PM PDT> <Critical> <Security> <RTDC79689VMC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1282100893058> <BEA-090404> <User weblogic_wc 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.>
      ####<Aug 17, 2010 8:08:13 PM PDT> <Critical> <WebLogicServer> <RTDC79689VMC> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1282100893058> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: User weblogic_wc 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 weblogic_wc 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)
      >
      ####<Aug 17, 2010 8:08:13 PM PDT> <Notice> <WebLogicServer> <RTDC79689VMC> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1282100893121> <BEA-000365> <Server state changed to FAILED>
      ####<Aug 17, 2010 8:08:13 PM PDT> <Error> <WebLogicServer> <RTDC79689VMC> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1282100893121> <BEA-000383> <A critical service failed. The server will shut itself down>
      ####<Aug 17, 2010 8:08:13 PM PDT> <Notice> <WebLogicServer> <RTDC79689VMC> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1282100893121> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
      ####<Aug 17, 2010 8:08:16 PM PDT> <Info> <WebLogicServer> <RTDC79689VMC> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1282100896699> <BEA-000236> <Stopping execute threads.>
      ===============================================================

      Any help in in this regard is greatly appreciated.

      Thanks,
      Madan.