JAVA stack installation failed. Split ABAP+JAVA

[former_member245717]

Dear All,

I'm spiting ABAP+JAVA stack to ABAP and JAVA system.

Now i'm installing JAVA failed at final step 'Deploy configuration content for Dual-Stack Split',

The error message from sapinst log is as following:

Mar 29, 2016 11:22:53... Info: SDA to be deployed: /usr/sap/XC9/JC20/SDM/root/origin/sap.com/tc/lm/config/content/MAIN_NW702S_D/1/5579208/tc~lm~config~content.sda

Mar 29, 2016 11:22:53... Info: Software type of SDA: J2EE

Mar 29, 2016 11:22:53... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

Mar 29, 2016 11:22:53... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Mar 29, 2016 11:22:53... Error: Aborted: development component 'tc/lm/config/content'/'sap.com'/'MAIN_NW702S_D'/'5579208'/'1':

Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.

com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [MYHOSTNAME] with user name: [J2EE_ADMIN]

                                Check your login information.

                                Exception is:

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]

        at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:494)

        at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:363)

        at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)

        at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)

        at javax.naming.InitialContext.init(InitialContext.java:219)

        at javax.naming.InitialContext.<init>(InitialContext.java:195)

        at com.sap.engine.deploy.manager.DeployManagerImpl.checkCredentials(DeployManagerImpl.java:2983)

        at com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthMethodInvoker.invokeCheckCredentialsInternal(DeployManagerAuthMethodInvoker.java:53)

        at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:45)

        at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:32)

        at com.sap.sdm.serverext.servertype.inqmy.extern.EngineOnlineDeployerImpl.checkLoginCredentials(EngineOnlineDeployerImpl.java:173)

        at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:168)

        at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:97)

        at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)

        at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)

        at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)

        at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)

        at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)

        at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)

        at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)

        at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)

        at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)

        at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:128)

        at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:97)

        at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:68)

        at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:179)

        at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:53)

        at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)

        at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)

        at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)

        at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)

        at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)

        at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)

        at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)

        at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:54)

        at com.sap.sdm.control.command.decorator.SyntaxChecker.execute(SyntaxChecker.java:37)

        at com.sap.sdm.control.command.Command.exec(Command.java:42)

        at SDM.main(SDM.java:21)

Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.

        at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34)

        at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)

        at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)

        ... 36 more

Caused by: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.

        at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:726)

        at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:714)

        at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:171)

        at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:486)

        at java.lang.Thread.run(Thread.java:713)

For more inforation check CSN Note 1313644

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)

Mar 29, 2016 11:22:53... Info: Starting to save the repository

Mar 29, 2016 11:22:53... Info: Finished saving the repository for 129 ms.

Mar 29, 2016 11:22:53... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

Mar 29, 2016 11:22:53... Error: ---------------- At least one of the Deployments failed ---------------

Mar 29, 2016 11:22:53... Info: Summarizing the deployment results:

Mar 29, 2016 11:22:53... Error: Aborted: /70SWPM10SP10/COMMON/DSS/tc~lm~config~content.sda

Mar 29, 2016 11:22:53... Error: Admitted: /70SWPM10SP10/COMMON/DSS/tc~lm~ctc~util~basic_ear.sda

Mar 29, 2016 11:22:53... Error: Processing error. Return code: 4

I already checked note 1313644 but it did not help me out. 

1. i can see from MMC,  msg_server, enserver, dispatcher, server0 are all green, but SDM server is stopped.

2. I can start SDM server by the command below

sdm.sh jstartup mode=integrated

StartServer.sh

3. no matter SDM started or stopped,  portal still not available.

  SAP NetWeaver AS Java is starting...

If this state does not change within a few minutes,

please contact your system administrator.

Check the recommendations in SAP Notes: 943498, 764417

Message: Dispatcher running but no server connected!

  Details:

  No details available

4. If i started SDM in integrated mode, and restart sapinst, during the step 'Deploy configuration content for Dual-Stack Split', SDM will be stopped and set to standalone mode, later then SDM can not be started.

5. I checked the log dev_server0, dev_control, dev_dispatcher. there are no obvious errors.

Could you please advise what else should i check?

Appreciate.

[former_member245717]

Dear All,

Thanks a lot for your support on this case.  I noticed in my source system there was an upgraded stopped in downtime for long time and it was not cleaned up.

I suppose this could be the problem that we failed to split it.

We are now working on the cleaning the source system.

Thanks again.

BR

Dong Zhou

[AtulKumarJain]

Hi Dong,

Please check user J2EE_ADMIN is not locked in ABAP side ,if still you have not done the split.

As per log

o

m.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [MYHOSTNAME] with user name: [J2EE_ADMIN]
                                Check your login information.

BR

Atul

[former_member245717]

Hi Atul,

I confirmed J2EE_ADMIN is not locked and password is correct. I can use it logon in my ABAP stack.

What else could i check?

[AtulKumarJain]

Can you please stop and start the java and see if it starting or not.

If not please check default trace and server trace.If found any error please paste here

BR

Atul

[Former Member]

Hi,

Please check below sap note

1726902 - PREPARE/INIT/USER_PASSWORD Error while trying to get initial context during upgrade or EHP...

1891477 - PI 7.1X upgrade deployment process fails due to missing ExecutionDetails class

Regards,

Prithviraj.

[former_member245717]

According to the note, although our system is nw7.0 ehp2, i changed 70SWPM10SP10_3/COMMON/DSS to 70SWPM10SP10_3/COMMON/DSS.old.

Sapint ignored to deploy tc~lm~config~content.sda  tc~lm~ctc~util~basic_ear.sda and passed the step of 'Deploy cofiguration content for Dual-Stack Split'

https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F6465...

1. the pure java stack restarted successfully.

2. from MMC every items are green.

Now i get new errors.

1. Portal still with message: SAP NetWeaver AS Java is starting...  (seems java system did not really started)

2. The final step 'Create RFC destinations in ABAP system'  failed with error below.

ERROR 2016-04-01 07:44:32.609 (root/sapinst) id=controller.java.exceptionDuringFunctionExecution errno=FCO-00141

The JVM reports an exception during execution of class ( com.sap.sdt.ins.component.dss_rfc_destinations.CreateRFCDestinations ) and function executeStepClass. DIAGNOSIS: The reported error message from JVM is: com.sap.conn.jco.AbapException: (126) CREATE_FAILURE: CREATE_FAILURE Message 016 of class SDEST type E, Par[1]: AS_JAVA_HTTP, Par[2]: G

        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.execute(MiddlewareJavaRfc.java:2083)

        at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:1185)

        at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:1014)

        at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:1458)

        at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:1428)

        at com.sap.conn.jco.rt.AbapFunction.execute(AbapFunction.java:332)

        at com.sap.sdt.ins.component.dss_rfc_destinations.CreateRFCDestinations.createHttpDestination(CreateRFCDestinations.java:119)

        at com.sap.sdt.ins.component.dss_rfc_destinations.CreateRFCDestinations.createRFCDestinations(CreateRFCDestinations.java:89)

        at com.sap.sdt.ins.component.dss_rfc_destinations.CreateRFCDestinations.execute(CreateRFCDestinations.java:41)

.

ERROR 2016-04-01 07:44:33.635 (root/sapinst) id=controller.stepExecuted errno=FCO-00011

The step CreateRFCDestinations with step key |DSS_Distributed_InstallJava_CI|ind|ind|ind|ind|0|0|dss_rfc_destinations_dialog|ind|ind|ind|ind|rfcDest|0|dss_rfc_destinations|ind|ind|ind|ind|0|0|CreateRFCDestinations was executed with status ERROR ( Last error reported by the step: The JVM reports an exception during execution of class ( com.sap.sdt.ins.component.dss_rfc_destinations.CreateRFCDestinations ) and function executeStepClass. DIAGNOSIS: The reported error message from JVM is: com.sap.conn.jco.AbapException: (126) CREATE_FAILURE: CREATE_FAILURE Message 016 of class SDEST type E, Par[1]: AS_JAVA_HTTP, Par[2]: G

        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.execute(MiddlewareJavaRfc.java:2083)

        at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:1185)

        at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:1014)

        at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:1458)

        at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:1428)

        at com.sap.conn.jco.rt.AbapFunction.execute(AbapFunction.java:332)

        at com.sap.sdt.ins.component.dss_rfc_destinations.CreateRFCDestinations.createHttpDestination(CreateRFCDestinations.java:119)

        at com.sap.sdt.ins.component.dss_rfc_destinations.CreateRFCDestinations.createRFCDestinations(CreateRFCDestinations.java:89)

        at com.sap.sdt.ins.component.dss_rfc_destinations.CreateRFCDestinations.execute(CreateRFCDestinations.java:41)

.).

[AtulKumarJain]

Please check

2288935 - Dual Stack Split fails with error: CREATE_FAILURE Message 016 of class SDEST type E, Par[1...

[former_member245717]

Yes, i'm checking,  but i did not find the so call AS_JAVA_HTTP in my source ABAP system, by run tcode:  SE37, Function Module: DEST_HTTP_EXT_READ

Test for function group      SDEST_API

Function module              DEST_HTTP_EXT_READ

Uppercase/Lowercase

RFC target sys:

  Import parameters               Value

  NAME

I did not find the so called RFC.

Could be the cause that i ignored one step?  cause1 is talking about it.

Cause

The step CreateRFCDestinations is not able to create RFC AS_JAVA_HTTP because the destination already exists in source ABAP system. The cause for that could be:

1. Previous issue during the execution of the dual stack split;
2. Repeated procedure that resulted on that.

[former_member245717]

HI Atul,

I deleted RFC AS_JAVA_HTTP and AS_JAVA_HTTPS from source ABAP system.

rerun sapinst finished.

The step  'Install Java Central Instance' is finished.

The only remain problem is my portal still not available.

503   Service Unavailable

  SAP J2EE Engine

  SAP NetWeaver AS Java is starting...

If this state does not change within a few minutes,

please contact your system administrator.

Check the recommendations in SAP Notes: 943498, 764417

Message: Dispatcher running but no server connected!

  Details:

  No details available

Should the portal up running or still need some other post steps?