server0 fails to start during SolMan 7.0 installation

[ThomasKjelsrud]

Hi all.

I know this is a well discussed topic, but so far I have not been able to solve my issue by trying the proposed solutions in other threads or notes.

I am installing Solution Manager 4.0(7.0) SR4 on X64 Windows 2003 server with MSSQL 2005 SP2, an ABAP+Java (dual stack) installation.

This is the second SAP instance on this server, as I have installed another SAP instanse on this host as well, normally not a problem.

The issue is that during installation step 33 (Start Java engine), the server0 process fails with error code -11113.

Excerpt from std_server0.out log:

Core service security failed. J2EE Engine cannot be started.

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

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

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:77)

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:135)

... 5 more

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

Nov 19, 2008 8:23:01 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_52] Fatal: Critical shutdown was invoked. Reason is: Core service security failed. J2EE Engine cannot be started.

Excerpt from defaultTrace0.trc:

#1.5 #00145EB4162C00200000000B0000068400045C096E8C80DE#1227095485998#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_24##0#0#Fatal#1#/System/Server/Critical#Plain###Critical shutdown was invoked. Reason is: Core service security failed. J2EE Engine cannot be started.#

#1.5 #00145EB4162C001F0000000200000DE400045C0971A12436#1227095537700#com.sap.security.core.server.userstore.GroupContextUME##com.sap.security.core.server.userstore.GroupContextUME#######SAPEngine_System_Thread[impl:5]_31##0#0#Error##Java###Error during creation of default groups or role assignments: {}

[EXCEPTION]

#2#Cannot set unique name to null!#com.sap.security.api.UMRuntimeException: Cannot set unique name to null! at com.sap.security.core.imp.AbstractPrincipal.setUniqueName(AbstractPrincipal.java:1602) at com.sap.security.core.imp.GroupFactory.newGroup(GroupFactory.java:519) at com.sap.security.core.server.userstore.GroupContextUME.engineCreateGroup(GroupContextUME.java:157) at com.sap.security.core.server.userstore.GroupContextUME.enginePropertiesChanged(GroupContextUME.java:477) at com.sap.engine.services.security.userstore.context.GroupContext.<init>(GroupContext.java:35) at com.sap.engine.services.security.server.UserStoreImpl.<init>(UserStoreImpl.java:160) at com.sap.engine.services.security.server.UserStoreFactoryCache.registerUserStore(UserStoreFactoryCache.java:142) at com.sap.engine.services.security.server.UserStoreFactoryImpl.<init>(UserStoreFactoryImpl.java:59) at com.sap.engine.services.security.userstore.UserStoreService.<init>(UserStoreService.java:51) at com.sap.engine.services.security.server.SecurityContextImpl.getUserStoreContext(SecurityContextImpl.java:213) 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:135) 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) # #1.5 #00145EB4162C001F0000000400000DE400045C0971A5A2B9#1227095537997#com.sap.engine.services.security##com.sap.engine.services.security#######SAPEngine_System_Thread[impl:5]_31##0#0#Error#1#/System/Security#Java#security_0001##Unexpected exception:## #1.5 #00145EB4162C001F0000000500000DE400045C0971A5A6AF#1227095537997#com.sap.engine.services.security##com.sap.engine.services.security#######SAPEngine_System_Thread[impl:5]_31##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception: at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:181) 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:77) 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:135) There seems to be two things that stand out "No active userstore set" and "Error during creation of default groups or role assignments" / "Error during creation of default groups or role assignments: {} [EXCEPTION] #2#Cannot set unique name to null!"

Any one got any bright ideas that can help me fix this issue?

A few things I have done/checked:

My ABAP stack is up, and I can log on to it with J2EE_ADMIN.

I have set the password for the J2EE_ADMIN in configtool to the same password as I logged on with on the ABAP stack.

I am unable to open the viaual admin, error message: Unable to lookup default connection. "server:8101/msgserver/text/logon" returned empty list of connection parameters.

Please let me know if you require more information in order to troubleshoot.

Regards,

Thomas

[Former Member]

Hi,

Normally error -1113 related to JVM Settings, which needs to be configured as per recommended by SAP.

Please follow below mentioned note & try your luck...

723909 Java VM Settings

[ThomasKjelsrud]

Hi.

I restarted the installation a few times, and finally it went through successfully. I have no idea why it succeeded the last time, I changed nothing.

Regards,

Thomas

[vincentlim826]

Return code -11113 : Essential service fails to start so the server/dispatcher process should exit.

Please check on the files:

- dev_jcontrol

- dev_server<n>

- dev_bootstrap

- dev_dispatcher

- std_server<n>.out

- std_bootstrap.out

- std_dispatcher.out

What Java Version and build are you running (JDK)?

Could it be UME Service related ?

If it is "No active userstore set", probably check SAP Note 1042418.

Normally this error appears when there is a problem with the UME parameters.

You should also make sure that the communication user, SAPJSF

has the correct authorizations. You should make sure that you can logon to the R/3 with both SAPJSF

and J2EE_ADMIN.

Finally, you should check that the appropriate settings are in place

for the R3 in the propertysheet com.sap.security.core.ume.service

and also in the Secure Store area of the ConfigTool.

Please also check the help page below:

http://help.sap.com/saphelp_nw04/helpdata/en/49/9dd53f779c4e21e10000000a

1550b0/content.htm

Regards,

Vincent