1 Reply Latest reply on Dec 8, 2012 6:17 AM by Ganesh..

    Can't start managed server - Authentication for user denied


      I have a WebLogic 10.3.6 based domain. The admin server works correctly. Using the admin console, I created a managed server. It is not associated to any machine and I don't use node manager. The managed server listens on localhost:7101 while the admin listens on localhost:7001. Starting the managed server asks for an user/password authentication. Using the same as the one used for the admin console says:

      <7 dÚc. 2012 13 h 55 CET> <Critical> <Security> <BEA-090403> <Authentication for
      user nicolas denied>
      <7 dÚc. 2012 13 h 55 CET> <Critical> <WebLogicServer> <BEA-000386> <Server subsy
      stem failed. Reason: weblogic.security.SecurityInitializationException: Authenti
      cation for user nicolas denied
      weblogic.security.SecurityInitializationException: Authentication for user nicol
      as denied
      at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.do
      at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
      at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
      at weblogic.security.SecurityService.start(SecurityService.java:141)
      at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      Truncated. see log file for complete stacktrace
      Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Auth
      entication Failed: User nicolas weblogic.security.providers.authentication.LDAPA
      tnDelegateException: [Security:090295]caught unexpected exception
      at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.log
      at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(Log
      at java.security.AccessController.doPrivileged(Native Method)
      at com.bea.common.security.internal.service.LoginModuleWrapper.login(Log
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      Truncated. see log file for complete stacktrace
      <7 dÚc. 2012 13 h 55 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state c
      hanged to FAILED>
      <7 dÚc. 2012 13 h 55 CET> <Error> <WebLogicServer> <BEA-000383> <A critical serv
      ice failed. The server will shut itself down>
      <7 dÚc. 2012 13 h 55 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state c
      hanged to FORCE_SHUTTING_DOWN>

      I googled a while and found a post saying that the realm is probably altered or in an incorrect status. I reset the the admin's credentials using weblogic.security.utils.AdminAccount but this disn't change anything. Of course, upon the managed server creation, I initialized the fierlds user and password in the server starting tab of the admin console.

      Many thanks for any help.