There was an internal issue with the Domain Controller (port/service issue) as connection could not established to the Domain Controller specified in the config.xml file using LDP. Hence, Domain Controller was unable to authenticate the Service account.
The Production Server log file indicated:
<> <> <> <1496323175368> weblogic.security.SecurityInitializationException: Server installed as Windows NT service with incorrect password for user svc_WLSadmin; The password may have been changed since the server was installed as a Windows NT Service. Contact the Windows NT system administrator.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:945)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: javax.security.auth.login.FailedLoginException: Authentication Failed: User svc_WLSadmin doesn't exist.
at com.bluepumpkin.security.wlsproviders.authentication.DBLoginModuleImpl.throwFailedLoginException(DBLoginModuleImpl.java:256)
at
