Not able to start J2ee Engine

[Former Member]

Hi,

Recently upgrade from NW04 to NW04s.As a post work started deploying few SP.During deploying it tried to restart the J2ee Engine and now its not coming up.

This is the error details:

com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:

at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.

at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)

at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)

at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)

at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)

at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)

... 5 more

[Framework -> criticalShutdown] Core service security failed. J2EE Engine cannot be started.

Jul 27, 2007 4:36:16 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_15] Fatal: Critical shutdown was invoked

. Reason is: Core service security failed. J2EE Engine cannot be started.

Can anybody have any idea on this ?

Thanks

Venkat

[Former Member]

This is what i found in defaultTrace file

com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)

at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1015)

at com.sap.mw.jco.JCO$Client.connect(JCO.java:3238)

at com.sap.mw.jco.JCO$Pool.getClient(JCO.java:5380)

at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6149)

at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6099)

at com.sap.mw.jco.JCO.getClient(JCO.java:8766)

at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy$Client640.fetchClient(R3JCo640Proxy.java:441)

at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy$Client640.execute(R3JCo640Proxy.java:367)

at com.sap.security.core.persistence.datasource.imp.R3Persistence.doBapiUserExistenceCheck(R3Persistence.java:7408)

at com.sap.security.core.persistence.datasource.imp.R3Persistence.getExistenceCheckResult(R3Persistence.java:2754)

at com.sap.security.core.persistence.datasource.imp.R3Persistence.searchPrincipalDatabags(R3Persistence.java:1228)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.searchPrincipalDatabagsInternal(PrincipalDatabagFactoryIns

[Former Member]

you need to resolve this in the abap stack.

<i>Password logon no longer possible - too many failed attempts</i>

Run SUIM, and check for for locked users (failed logon attempts).

[Former Member]

In order to find the reason for this, first ensure that the UME and especially the connectivity between the UME and its persistence is working properly, that is, it has access to its configured persistence option.

With a second check you should verify that the configured guest user actually exists in the persistent repository. (J2EE_GUEST)

If an ABAP stack is used as UMEpersistence, then check whether the file defaultTrace.trc.<x> contains any messages with the string RFC in it. If you find such a message, this message contains a detailed description of the reason why some operation failed, for example, the ABAP stack was not started or the configured guest user does not exist. If another persistence option is used, then also check the file defaultTrace.trc.<x> for the error message of the security service startup which should contain a similar message.

See SAP Note 699557

[Former Member]

first ensure that the UME and especially the connectivity between the UME and its persistence is working properly, that is, it has access to its configured persistence option.

Can you explain me how to check this ?

Thanks

Kalyan

[Former Member]

com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)

at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1015)

at com.sap.mw.jco.JCO$Client.connect(JCO.java:3238)

at com.sap.mw.jco.JCO$Pool.getClient(JCO.java:5380)

at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6149)

at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6099)

at com.sap.mw.jco.JCO.getClient(JCO.java:8766)

at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy$Client640.fetchClient(R3JCo640Proxy.java:441)

at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy$Client640.execute(R3JCo640Proxy.java:367)

at com.sap.security.core.persistence.datasource.imp.R3Persistence.doBapiUserExistenceCheck(R3Persistence.java:7408)

at com.sap.security.core.persistence.datasource.imp.R3Persistence.getExistenceCheckResult(R3Persistence.java:2754)

at com.sap.security.core.persistence.datasource.imp.R3Persistence.searchPrincipalDatabags(R3Persistence.java:1228)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.searchPrincipalDatabagsInternal(PrincipalDatabagFactoryIns