cancel
Showing results for 
Search instead for 
Did you mean: 

Solman's j2ee engine, server0, wont start (exitcode -11113)

Former Member
0 Kudos
123

Hi experts,

I have a freshly installed solution manager, but the windows server had a reboot due to windows update and since the reboot, the server0 does not start and had an exit code -1113 -11113 (Core service or additional service start fails: "HaltOnAdditionalServiceFailure=true"(service manager)


I tried looking for some infos on the web and found this post :

https://scn.sap.com/thread/3300828

j2ee server process stopped with JLaunchCloseProgram: good bye (exitcode = -11113) - Toolbox for IT...

But I am fresh to Solution Manager and did not know which user to reset, nor how. I can't connect to http://host:5000 since the server isn't started and in SU01, I don't see any user created during the installation (J2EE_GUEST, SAPJSF and J2EE_USER)

Any informations ?

Regards,

Dimitri

Accepted Solutions (1)

Accepted Solutions (1)

former_member185239
Active Contributor
0 Kudos

Hi Dimitri,

You have to check the log std_server0.out file.

Moreover , you have to check the user in SU01 in 001 client.

Kindly paste the std_server0.out log file.

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hi, thanks for your answer,

For some reason, I managed to log in on 001 with J2EE-ADMIN, where all the Java users are declared, but they're neither in 000 nor 100 (copy from 000).

Here's a copy of part of the std_server0 log, I put in bold what is I guess, the cause of the issue :

Loading: LogManager ... 281 ms.

Loading: PoolManager ... 0 ms.

Loading: ApplicationThreadManager ... 1.303: [GC 1.303: [ParNew: 409600K->2793K(512000K), 0.0088284 secs] 409600K->2793K(1994752K), 0.0090847 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]

78 ms.

Loading: ThreadManager ... 16 ms.

Loading: IpVerificationManager ... 16 ms.

Loading: ClassLoaderManager ... 0 ms.

Loading: ClusterManager ... 140 ms.

Loading: LockingManager ... 63 ms.

Loading: ConfigurationManager ... 1416 ms.

Loading: LicensingManager ... 63 ms.

Loading: CacheManager ... 62 ms.

Loading: ServiceManager ...

Loading services.:

  Service memory started. (31 ms).

  Service cross started. (63 ms).

  Service file started. (63 ms).

  Service runtimeinfo started. (47 ms).

  Service trex.service started. (94 ms).

  Service timeout started. (94 ms).

  Service jmx_notification started. (31 ms).

  Service userstore started. (0 ms).

  Service p4 started. (149 ms).

  Service classpath_resolver started. (15 ms).

7.336: [GC 7.336: [GC 7.336: [ParNew: 361764K->20562K(512000K), 0.0488823 secs] 361764K->20562K(1994752K), 0.0491081 secs] [Times: user=0.09 sys=0.08, real=0.05 secs]

[1 CMS-initial-mark: 0K(1482752K)] 20562K(1994752K), 0.0533173 secs] [Times: user=0.09 sys=0.08, real=0.05 secs]

7.389: [CMS-concurrent-mark-start]

7.443: [CMS-concurrent-mark: 0.053/0.053 secs] [Times: user=0.13 sys=0.05, real=0.05 secs]

7.443: [CMS-concurrent-preclean-start]

7.448: [CMS-concurrent-preclean: 0.005/0.005 secs] [Times: user=0.03 sys=0.01, real=0.02 secs]

7.448: [CMS-concurrent-abortable-preclean-start]

10.666: [CMS-concurrent-abortable-preclean: 1.772/3.218 secs] [Times: user=6.69 sys=2.08, real=3.22 secs]

10.678: [GC [YG occupancy: 276681 K (512000 K)]10.678: [Rescan (parallel) , 0.0507833 secs]10.729: [weak refs processing, 0.0002500 secs]10.729: [class unloading, 0.0038638 secs]10.733: [scrub symbol table, 0.0051518 secs]10.738: [scrub string table, 0.0009705 secs][1 CMS-remark: 0K(1482752K)] 276681K(1994752K), 0.0628552 secs] [Times: user=0.23 sys=0.02, real=0.06 secs]

10.741: [CMS-concurrent-sweep-start]

10.741: [CMS-concurrent-sweep: 0.000/0.000 secs] [Times: user=0.05 sys=0.02, real=0.02 secs]

10.742: [CMS-concurrent-reset-start]

10.772: [CMS-concurrent-reset: 0.030/0.030 secs] [Times: user=0.05 sys=0.01, real=0.02 secs]

  Service log_configurator started. (5618 ms).

  Service locking started. (16 ms).

  Service naming started. (281 ms).

  Service failover started. (0 ms).

  Service appclient started. (31 ms).

  Service http started. (328 ms).

  Service jmsconnector started. (62 ms).

  Service licensing started. (156 ms).

  Service ts started. (110 ms).

  Service javamail started. (172 ms).

  Service connector started. (78 ms).

  Service iiop started. (94 ms).

  Service deploy started. (10109 ms).

16.114: [GC 16.114: [ParNew: 430162K->29182K(512000K), 0.0467578 secs] 430162K->29182K(1994752K), 0.0470010 secs] [Times: user=0.16 sys=0.03, real=0.05 secs]

  Service MigrationService started. (16 ms).

  Service configuration started. (47 ms).

  Service dbpool started. (1168 ms).

  Service UT started. (16 ms).

  Service tc~lm~nzdm~crrsrv started. (234 ms).

Aug 19, 2016 10:26:36...        com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_63] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "Name or password is incorrect (repeat logon)". This message is critical if it appears during the startup of the AS Java.

Aug 19, 2016 10:26:36... ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_63] Fatal:

  service com.sap.security.core.ume.service ================= ERROR =================

Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is incorrect (repeat logon)

    at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:407)

    at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

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

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

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)

    at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)

    at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:447)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)

    at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)

    at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:288)

    ... 6 more

com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is incorrect (repeat logon)

    at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:407)

    at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

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

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

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)

    at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)

    at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:447)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)

    at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)

    at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)

    at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:288)

    ... 6 more

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

Aug 19, 2016 10:26:36...            com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_63] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Heap

par new generation   reserved 614400K, committed 614400K, used 111494K [0x0000000080000000, 0x00000000a5800000, 0x00000000a5800000)

  eden space 409600K,  20% used [0x0000000080000000, 0x00000000850622d8, 0x0000000099000000)

  from space 102400K,  28% used [0x000000009f400000, 0x00000000a107f8a0, 0x00000000a5800000)

  to   space 102400K,   0% used [0x0000000099000000, 0x0000000099000000, 0x000000009f400000)

concurrent mark-sweep generation reserved 1482752K, committed 1482752K, used 0K [0x00000000a5800000, 0x0000000100000000, 0x0000000100000000)

Metaspace       used 32392K, capacity 34690K, committed 34764K, reserved 292864K

  class space    used 3373K, capacity 4036K, committed 4044K, reserved 262144K

manish_singh13
Active Contributor
0 Kudos

Hi Dimitri,

As per the logs issue seems to be related with UME connection, and as you mentioned that you did the client copy from 000 client which is not correct.

In new installation Java users exists in 001 client and while creating new client you should select 001 as source client for user master record.

Currently it seems to be that your master client has been changed to your new client 100 where none of these Java user exists which can be rectified by bringing user master records from 001 client.

Please check and let us know.

Thanks,

Manish

Former Member
0 Kudos

I did a copy of the users from 001 to 100 and it works now, thanks a lot !

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Dimitri,

It may be that the JAVA instance cannot start due to something else using its port.

Check the ports in use and output to a file, for example:

CMD Prompt: netstat -aonb >> c:\temp\PIDS.txt

Or find the port in use by the JAVA system:

netstat /o /a | find "<insert_port_number_here>"

Then you can go to task manager to see what is using it.

Also, it may be the ABAP stack using the port! Try starting JAVA a little bit before ABAP.

Andy