Clusterwide exception: deploy customised ess~tra~tre.ear file. HELP.

[Former Member]

We are customising ess/mss business package to suit to Verizon Wireless.What are the dependent modules/packages. (as per the trace below)..

How do we proceed to deploy it ? It is an Unix Portal Dev machine with SP13 and current patches.

EPBC213P_2-10003489.SCA

EPPSERV13P_2-10003474.SCA

SAPJEE13P_2-10003469.SCA

SAPJEECOR13P_6-10003466.SCA

SAPJTECHS13P_4-10003467.SCA

UMEADMIN13P_2-10003471.SCA

Some SDN postings talk about SP13 patch 3 issue.

However, We were able to deploy successfully

before with SP11.

Also at the local desktop where I have the Developer Workplace with

SP09, I face the same issues.

-

---

com.sap.engine.services.deploy.container.DeploymentException:

Clusterwide exception: Failed to deploy application

sap.com/ess_tratre. 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:568)

at

com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.deploy

(DeployRuntimeControlImpl.java:262)

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.pj.jmx.introspect.DefaultMBeanInvoker.invoke

(DefaultMBeanInvoker.java:58)

at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke

(AdditionalInfoProviderMBean.java:289)

at com.sap.pj.jmx.server.MBeanServerImpl.invoke

(MBeanServerImpl.java:944)

[Former Member]

Check the default trace.

I think you have two components with the same name, creating a conflict. Use Visual Administrator to undeploy the old component before deploying the new component.

Look at this wiki:

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/04/25/webdynpro%20dc%20fails%20to%20...;