J2EE Engine cannot be started: No active userstore is set

You tried to bring up the SAP NetWeaver AS JAVA, but the startup is failing with the below error message,

#
#1.#669E8E690DF800210000000D0000052D0005FA3C6634A004#1682512203258#com.sap.engine.core.service630.container.ServiceRunner#
#com.sap.engine.core.service630.container.ServiceRunner
#######SAPEngine_System_Thread[impl:5]_26##0#0#Error#1#/System/Server#Java###Core service security failed. 
J2EE Engine cannot be started.
[EXCEPTION]
 {0}#1#com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
        at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:183)
        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:81)
        at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
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:80)
        at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:405)
        at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:84)
        at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:58)
        at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:136)
        ... 5 more

Solution

Since it is a generic error, there are numerous potential causes. You may refer to SAP Note 1596462 – BaseSecurityException: No active userstore is set to get to the most prevalent causes.

Resolution 1:

Make sure the following users are present in the AS ABAP system,

J2EE_ADMIN
J2EE_GUEST
SAPJSF

Resolution 2:

Make sure the UME connection parameters are correct, There are two methods to connect, using logon groups or connecting using hostname and system number. You cannot use a combination of the two. Using the Hostname and system number method is the more straight forward of the two so set the following parameters to default (even if they are blank already):

ume.r3.connection.master.msghost
ume.r3.connection.master.r3name
ume.r3.connection.master.group
ume.r3.connection.master.msgserv

Then insure the following parameters are correct:

ume.r3.connection.master.user
ume.r3.connection.master.passwd
ume.r3.connection.master.client
ume.r3.connection.master.sysnr
ume.r3.connection.master.ashost
ume.login.guest_user.uniqueids
ume.persistence.data_source_configuration

Resolution 3:

This issue can also be caused by incorrect values in the security policy UME parameters. This issue is discussed in SAP Note 1042418

Resolution 4:

The reason of the issue can also be incorrect Guest user configuration on ABAP side.

On NetWeaver AS Java start the configtool and navigate to cluster-data >> template – Usage_Type_All_in_One >> services >> com.sap.security.core.ume.service and locate the parameter ume.login.guest_user.uniqueids. This parameter defines the username of the Anonymous or Guest user in the environment.
Log in to ABAP and make sure that the user identified in the previous step exists in ABAP and the SAP_J2EE_GUEST role is assigned to it.