4 Replies Latest reply on Jun 27, 2011 3:29 PM by 871673

    Not able to start admin server after upgrading to 9.2 MP3 from 9.2 MP1

    666206
      Hi ,

      We are not able to start the admin server after upgrading it from 9.2 MP1 to 9.2 MP3.

      We can see below error:

      in Admin Server Log:

      ####<Sep 28, 2009 4:20:58 PM SGT> <Notice> <Security> <ssunu17> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1254126058891> <BEA-090082> <Security initializing using security realm myrealm.>
      ####<Sep 28, 2009 4:21:00 PM SGT> <Notice> <Stdout> <ssunu17> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1254126060451> <000000> <ManageableCitiLoginModuleImpl.initialize>
      ####<Sep 28, 2009 4:21:00 PM SGT> <Notice> <Stdout> <ssunu17> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1254126060451> <000000> <ManageableCitiLoginModuleImpl.login>
      ####<Sep 28, 2009 4:21:00 PM SGT> <Notice> <Stdout> <ssunu17> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1254126060453> <000000> <userName = xxxxxx>
      ####<Sep 28, 2009 4:21:00 PM SGT> <Notice> <Stdout> <ssunu17> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1254126060457> <000000> <ManageableCitiLoginModule.commit>
      ####<Sep 28, 2009 4:21:00 PM SGT> <Critical> <Security> <ssunu17> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1254126060671> <BEA-090404> <User xxxxxx 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.>
      ####<Sep 28, 2009 4:21:00 PM SGT> <Critical> <WebLogicServer> <ssunu17> <AdminServer> <main> <<WLS Kernel>> <> <> <1254126060674> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: User xxxxxxx 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 xxxxx 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:991)
      at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
      at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
      at weblogic.security.SecurityService.start(SecurityService.java:141)
      at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
      >
      ####<Sep 28, 2009 4:21:00 PM SGT> <Notice> <WebLogicServer> <ssunu17> <AdminServer> <main> <<WLS Kernel>> <> <> <1254126060727> <BEA-000365> <Server state changed to FAILED>



      any idea????
        • 1. Re: Not able to start admin server after upgrading to 9.2 MP3 from 9.2 MP1
          716227
          The admin username and password is encrypted based on the domain version, domain name and so on.

          To get your new domain admin server to startup normally I would suggest you rename the ldap folder under the admin server domain folder.

          user_projects\domains\base_domain\servers\AdminServer\data\ldap

          Starting the admin server after this would create a new ldap folder with all necessary files, and you should be able to start your admin server.

          Try starting the managed servers after this, and if it fails follow the above steps for the managed server ldap folder too.

          Thanks
          Sridhar S
          • 2. Re: Not able to start admin server after upgrading to 9.2 MP3 from 9.2 MP1
            666206
            Hi Sridhar,


            Thnks...its working. but got below error. anyway i will post it in new thread.

            i am able to start the admin server. But while starting managed server, we are hit with below error while deploying weblogic libraries:




            ####<Sep 29, 2009 11:23:38 AM SGT> <Info> <J2EE> <ssunu17> <CBK_MNG_SVR_1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1254194618703> <BEA-160151> <Registered library Extension-Name: wlp-services-web-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1.1 (WAR).>
            ####<Sep 29, 2009 11:23:38 AM SGT> <Error> <Deployer> <ssunu17> <CBK_MNG_SVR_1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1254194618746> <BEA-149205> <Failed to initialize the application 'wlp-tools-admin-app-lib [LibSpecVersion=9.2.0,LibImplVersion=9.2.1]' due to error weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: wlp-tools-admin-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.3, because of conflicting library Manifest values, and library information registered with the server: [Implementation-Version: 9.2.3 vs. 9.2.1]. Check the library"s MANIFEST.MF file, and correct version info there to match server settings. Or undeploy the misconfigured library..
            weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: wlp-tools-admin-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.3, because of conflicting library Manifest values, and library information registered with the server: [Implementation-Version: 9.2.3 vs. 9.2.1]. Check the library"s MANIFEST.MF file, and correct version info there to match server settings. Or undeploy the misconfigured library.
            at weblogic.application.internal.library.LibraryDeploymentFactory.getLibData(LibraryDeploymentFactory.java:110)
            at weblogic.application.internal.library.LibraryDeploymentFactory.createDeployment(LibraryDeploymentFactory.java:50)
            at weblogic.application.internal.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:90)
            at weblogic.deploy.internal.targetserver.BasicDeployment.createDeployment(BasicDeployment.java:146)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:110)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:38)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

            Edited by: user4912937 on Sep 29, 2009 11:26 AM

            Edited by: user4912937 on Sep 29, 2009 2:12 PM
            • 3. Re: Not able to start admin server after upgrading to 9.2 MP3 from 9.2 MP1
              720250
              Thanks a lot ... this solution saved my ***
              • 4. Re: Not able to start admin server after upgrading to 9.2 MP3 from 9.2 MP1
                871673
                Thanks a ton Sridhar. This saved my day. Works great on 10.x too