Skip to Content
0
Former Member
Jan 16, 2007 at 05:03 PM

Error when upgrade the EP server from NW2004s SP9 to SP10

33 Views

Hi

I was trying to upgrade the EP server from NW2004s SP9 to SP10

In the JSPM the final message status is as follows:

Overall deployment messages:

ActionStateUpdater.getStateForFurtherSCAction:Couldn't find any on the known states in groupedStatesSet

Now the J2EE runs in safe mode. 😔

Your help is appreciated.

Thank you

Regards

Luke

The SDM error log file line are given below

C'/'7.0010.20060210155432.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.10.0.20061022040900''/'1'

Jan 16, 2007 10:16:54... Info: Starting to save the repository

Jan 16, 2007 10:16:55... Info: Finished saving the repository

Jan 16, 2007 10:16:55... Info: Starting: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'7.0010.20050520154317.0000'/'1' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'7.0009.20050520154317.0000'/'1'.

Jan 16, 2007 10:16:55... Info: SDA to be deployed: C:\usr\sap\ABC\JC01\SDM\root\origin\sap.com\tc\bcb\api\SAP AG\1\7.0010.20050520154317.0000\bcb.sda

Jan 16, 2007 10:16:55... Info: Software type of SDA: library

Jan 16, 2007 10:16:55... Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****

Jan 16, 2007 10:17:06... Info: Begin of log messages of the target system:

07/01/16 10:16:55 - ***********************************************************

07/01/16 10:16:55 - Start deploying library JAR C:\usr\sap\ABC\JC01\SDM\root\origin\sap.com\tc\bcb\api\SAP AG\1\7.0010.20050520154317.0000\bcb.sda...

07/01/16 10:17:06 - ERROR: Cannot deploy library: C:\usr\sap\ABC\JC01\SDM\root\origin\sap.com\tc\bcb\api\SAP AG\1\7.0010.20050520154317.0000\bcb.sda. Reason: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library C:\usr\sap\ABC\JC01\SDM\root\origin\sap.com\tc\bcb\api\SAP AG\1\7.0010.20050520154317.0000\bcb.sda. Reason:

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

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

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

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

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

Exception is:

at com.sap.engine.deploy.manager.component.ServerComponentsManager.makeComponent(ServerComponentsManager.java:236) at com.sap.engine.deploy.manager.component.ServerComponentsManager.deployLibrary(ServerComponentsManager.java:138) at com.sap.engine.deploy.manager.DeployManagerImpl.deployLibrary(DeployManagerImpl.java:2404) at com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.performDeployment(EngineCompOnlineDeployerImpl.java:153) at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96) 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:120) at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:89) at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127) at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38) at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84) at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67) at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76) at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286) at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43) at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39) at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50) at java.lang.Thread.run(Thread.java:534) Jan 16, 2007 10:17:06... Info: End of log messages of the target system. Jan 16, 2007 10:17:06... Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) ***** Jan 16, 2007 10:17:06... Error: Aborted: development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'7.0010.20050520154317.0000'/'1', grouped by : Caught exception during library deployment from SAP J2EE Engine's deploy service: java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library C:\usr\sap\ABC\JC01\SDM\root\origin\sap.com\tc\bcb\api\SAP AG\1\7.0010.20050520154317.0000\bcb.sda. Reason: 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:701) at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:689) at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180) at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:424) at java.lang.Thread.run(Thread.java:534) Exception is:

; nested exception is:

com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library C:\usr\sap\ABC\JC01\SDM\root\origin\sap.com\tc\bcb\api\SAP AG\1\7.0010.20050520154317.0000\bcb.sda. Reason:

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

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

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

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

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

Exception is:

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

Jan 16, 2007 10:17:06... Info: Starting to save the repository

Jan 16, 2007 10:17:07... Info: Finished saving the repository