skip to main content

SAP NetWeaver Newbie

J2EE Engine Doesn't Start (exitcode=-11113)

Attempt to start the J2EE engine fails with an exit code -11113 (check dev_* trace file). The exit code -11113 means that a mandatory service has failed to start. You need to check the std_* trace file to determine which service has failed.


Sample Error 1: Core service p4 failed. J2EE Engine cannot be started.

Solution: Check bindHost property using Config Tool.

Navigate to configtool -> Instance -> dispatcher -> services -> p4 -> bindHost
Make sure that a correct value is maintained there. Remove any additional IP(backup IP) maintained.


Sample Error 2: Core service file failed. J2EE Engine cannot be started.

Caused by: org.omg.CORBA.INITIALIZE: cannot instantiate com.sap.engine.system.PortableRemoteObject vmcid: 0x0 minor code: 0 completed: No

Solution: In this example, one of the Java parameters is set incorrectly. The parameter should have been com.sap.engine.system.PortableRemoteObjectProxy instead of com.sap.engine.system.PortableRemoteObject.
Navigate to  configtool -> Instance, Java Parameters and correct it.
In this case, the property should have been -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy


Sample Error 3: Core service security failed. J2EE Engine cannot be started.

Caused by: com.sap.security.api.NoSuchUserAccountException: 
USER_AUTH_FAILED: User account for logonid "j2ee_guest" not found!

Solution: You are likely to face these problems if you have made changes to the user at the data source or changed the data source itself. Example: You have deleted the user; if using dual stack changed to some other client number; changed the data source to LDAP.


Follow these instructions:

http://wiki.sdn.sap.com/wiki/display/JSTSG/(SIM)Q0111

If you see "Io exception: There is no process to read data written to a pipe" in the default trace files, take java thread dumps. See if you find java.net.Inet6AddressImpl in the thread dumps. The JDK is configured to use IPv6. If the network environment is not configured to use IPv6, the threads that are showing the 
java.net.Inet6AddressImpl* classes are hanging. add "-Djava.net.preferIPv4Stack=true" to the JVM setting using config tool and restart the cluster.

No comments:

Post a Comment

Email Subscription

Get every new post into your inbox by subscribing us.

Want a reason to subscribe?
1. This sitemap might convince you to subscribe.
2. We do not misuse email IDs. We respect privacy.

© 2008 - 2017 sapnwnewbie. All rights reserved.