"startManagedWebLogic.cmd ATGProduction" error

Question

Hi
I have installed ATG Commerce Reference Store and have been getting this error while starting the ATGProduction server as per this step on the install guide
http://docs.oracle.com/cd/E22630_01/CRS.1002/pdf/ATGCRSInstall.pdf
Starting the Publishing and Production Servers
<Nov 11, 2012 8:40:09 AM PST> <Critical> <Security> <BEA-090403> <Authentication for user weblogic denied>
<Nov 11, 2012 8:40:09 AM PST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
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)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
>
<Nov 11, 2012 8:40:09 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Nov 11, 2012 8:40:09 AM PST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Nov 11, 2012 8:40:09 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
I have tried the resolution available at this link to remove boot.properties from the managed server and delete the contents of ldap directory but it did not help
http://www.weblogic-tips.com/2010/05/12/20100512how-to-resolve-authentication-denied-boot-identity-not-valid/
Can some one suggest a resolution ?
Thanks

Answer 1

Forgot to mention this in the first reply itself that you would also need to have a machine associated with that managed server when starting it from console.
1. Create a Machine from Environment > Machines > New. Give any name you want (e.g. TestMachine/MyServer/...) in the name field, click next and then finish.
2. You should now be able to see your newly created machine in the summary of machines. Click on it and go to Servers tab.
3. The servers table will initially be empty as there is no managed server associated with that machine. Click on Add button and complete the wizard to assign your existing managed server instance to the machine.
4. When done, Environment > Machines > Summary of machines > Servers tab should display the managed servers that have been assigned to that machine.
5. Now start the node manager.
6. Once node manager is started then try to start your managed server using the Admin Console as you would have done previously.