6 Replies Latest reply on Oct 6, 2010 9:47 AM by praveenap-790230

    the console can't start managed servers after upgrading WLS from 8.1 to 10

    Alex Ding
      When I start managed servers from the console after upgrading a WLS from 8.1 to 10.3, I got the following error message:

      <Feb 15, 2009 6:59:06 PM CST> <Info> <Security> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
      <Feb 15, 2009 6:59:06 PM CST> <Info> <Security> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server CAinter for security realm myrealm.>
      <Feb 15, 2009 6:59:06 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
      <Feb 15, 2009 6:59:07 PM CST> <Critical> <Security> <BEA-090402> <Authentication 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 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.>
      <Feb 15, 2009 6:59:07 PM CST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication 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 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.
      weblogic.security.SecurityInitializationException: Authentication 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 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.
      at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
      at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
      at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
      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)
      >
      <Feb 15, 2009 6:59:08 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
      <Feb 15, 2009 6:59:08 PM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>