J2EE Server startup problems WAS 6.4 SP8 EP SP7

[Former Member]

I had this J2EE server running fine, then this happened ... anyone seen this? Suggestions? The dispatcher and SDM start, but the server returns -11113. I don't believe that I made any changes, other than establishing some users in the portal. Here's the details:

EP SP7 Patch 2

WAS 6.4 SP8

<b>DEVELOPER TRACE in MMC says this:</b>

[Thr 5536] Wed Dec 01 15:46:55 2004

[Thr 5536] JLaunchIExitJava: exit hook is called (rc=-11113)

[Thr 5536] JLaunchCloseProgram: good bye (exitcode=-11113)

<b>SERVER LOG FILE says this:</b>

#1.5#000C29B92923000400000000000015600003EA34D7B46B33#1101937608313#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service cross started. (0 ms).#

#1.5#000C29B92923000600000000000015600003EA34D7C137AC#1101937609144#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_37##0#0#Error#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service file error. Nested exception is: java.lang.ExceptionInInitializerError

at com.sap.engine.services.file.FileFrame.start(FileFrame.java:60)

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

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

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

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

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

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

at javax.rmi.PortableRemoteObject.createDelegateIfSpecified(PortableRemoteObject.java:181)

at javax.rmi.PortableRemoteObject.<clinit>(PortableRemoteObject.java:58)

... 6 more

#

#1.5#000C29B92923000600000002000015600003EA34D7C14371#1101937609144#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_37##0#0#Error#1#/System/Server#Plain###Core service file failed. J2EE Engine cannot be started.#

#1.5#000C29B92923000600000004000015600003EA34D7C147A2#1101937609144#/System/Server##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_37##0#0#Fatal#1#com.sap.engine.core.Framework#Plain###Critical shutdown was invoked. Reason is: Core service file failed. J2EE Engine cannot be started.#

#1.5#000C29B92923000700000000000015600003EA34D7C1728A#1101937609160#/System/Server##com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run()#######SAPEngine_System_Thread[impl:5]_38##0#0#Error#1#com.sap.engine.core.service630.container.ContainerEventListenerWrapper#Plain###java.lang.NoClassDefFoundError occurred while service file processed interfaceAvailable(cross, com.sap.engine.services.cross.CrossImpl@c9630a) event null#

#1.5#000C29B92923000800000000000015600003EA34D7D9E5E2#1101937610775#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_32##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service tc_secwssec~service started. (1960 ms).#

#1.5#000C29B92923000500000002000015600003EA34D8045DB0#1101937613567#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_33##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service tc_secvsi~service started. (4580 ms).#

#1.5#000C29B92923000900000000000015600003EA34D818F191#1101937614916#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_22##0#0#Info#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service log_configurator started. (6588 ms).#

[Former Member · Accepted solution]

This is fixed. There was a typo in one of the parameters in the server java settings. I had modified those settings earlier and somehow 'Proxy' got chopped off of the end of the PortableRemoteObjectProxy class.

[Former Member · Accepted solution]

I am having the same problems I just changed slightly the configuration file for MSADS LDAP.

What can I do?

[Former Member · Accepted solution]

I just have the same problem, can anybody describe how to fix this.. please as easy as possible

Best Regards

Jonas

[Former Member · Accepted solution]

How did you fix it?

[Former Member · Accepted solution]

Hello,

Check in the configtool the java parameters of your server node for typing errors. This was the problem, which Timothy reported and solved by himself.

If you experience exactly the same error check if you have the following parameter:

-Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

Kind Regards

Vyara