Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Deployment aborted when I deploy an application...

Dear All,

When I deploy an application, I got this error message. What's the reason? How to fix it? Thanks!

11/05/25 13:40:11 - ***********************************************************

11/05/25 13:40:12 - Start updating EAR file...

11/05/25 13:40:12 - start-up mode is lazy

11/05/25 13:40:12 - EAR file updated successfully for 78ms.

11/05/25 13:40:12 - Start deploying ...

11/05/25 13:40:12 - EAR file uploaded to server for 63ms.

11/05/25 13:40:13 - ERROR: Not deployed. Deploy Service returned ERROR:

java.rmi.RemoteException: Cannot deploy application cat/eee~xds..

Reason: Clusterwide exception: Failed to deploy application cat/eee~xds. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:

com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application cat/eee~xds. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?

at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)

at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)

at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application cat/eee~xds. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?

at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1050)

at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)

at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)

at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)

at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)

at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)

... 10 more

For detailed information see the log file of the Deploy Service.

11/05/25 13:40:13 - ***********************************************************

May 25, 2011 1:40:13 PM Info: End of log messages of the target system.

May 25, 2011 1:40:13 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

May 25, 2011 1:40:13 PM Error: Aborted: development component 'eee/xds'/'cat'/'LOKAL'/'0.2011.05.25.13.39.51'/'0':

Caught exception during application deployment from SAP J2EE Engine's deploy service:

java.rmi.RemoteException: Cannot deploy application cat/eee~xds..

Reason: Clusterwide exception: Failed to deploy application cat/eee~xd

Former Member
replied

Hi Jie,

Please check all the used Dc for this dc are deployed properly in the server or not. if not then first deploy the used dc and try to deploy again.

Check the NWDS Error log for more details under NWDS windows > show view > othere..> Portal runtime

Best Regards

Arun Jaiswal

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question