Deployment Error when transporting to TEST server

[Former Member]

Hi experts,

I'm having a deployment error when transporting my dc from development server to test server using the Change Management Service - Transport Studio.

In the error message, there is the mention of the following sentence:

=============================================

Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine ?

=============================================

But the dc is using only the standard default dcs like:

com.sap.aii.proxy.framework (default)

com.sap.aii.util.misc (default)

com.sap.exception (default)

com.sap.mw.jco (default)

tc/cmi (default)

tc/ddic/ddicruntime (default)

td/ddic/metamodel/content (default)

tc/logging (default)

tc/wd/webdynpro (default)

tc/wdp/metamodel/content (default)

So could these dcs not have been deployed on the test server ?

How do we confirm this ?

Thanks in advance.

Rgds,

Daniel

[Former Member · Accepted solution]

What version of NWDI you are using?

As far as I know, you can transport DCs in the CMS from DEV (CONS) to TEST starting from NW7 EHP1, which is not available to general public yet and is expected to come out early next year.

CMS of NWDI NW7 prior to that allow transport of assembled SC only (Assembly tab between Cons and Test).

Are you sure you are not talking about post built deployment to DEV or Cons?

Regards,

Slava

[Former Member · Accepted solution]

Hi Slava,

Sorry i meant transport of assembled SC from DEV to TEST.

Do you know the reason and how to troubleshoot ?

Thanks.

Rgds,

Daniel

[Former Member · Accepted solution]

SCs have dependencies in other SCs for:

- built time;

- runtime

You probably have issue with runtime required components.

Analyze SLD information for the SC you are deploying and make sure all required for runtime SCs are delpoyed to TEST correctly and have proper versions.

You may compare sysinfo of your DEV or CONS with TEST to see if relevant SCs are missing or have wrong version.

If in doubt - redeploy to TEST.

Regards,

Slava

[Former Member · Accepted solution]

Hi Slava,

Thanks for the tips.

After looking at the sysinfo of the TEST server, i found out that

SAP_BUILDT is of an old version i.e 6.40 SP12 and i have upgraded to 7.00 SP13.

Could this be the reason for my failed deployment ?

Thanks.

Regds,

Daniel

[Former Member · Accepted solution]

Yes, it could be.

SAP_BUILDT is one of the SCs required for build time, it comes with the DC for DTR.

It was probably uploaded to DTR via CMS, so you should be able to propagate it in CMS.

Regard$,

Slava

[Former Member · Accepted solution]

Hi Slava,

Thanks for your feedback.

How do i propagate the new version of SAP_BUILDT to CMS ?

I mean how to i overwrite the old version of SAP_BUILDT 6.40 SP12 which is currently deployed with the new SAP_BUILDT 7.00 SP13 ?

Rgds,

Daniel

[thulasi_td · Accepted solution]

Hi Daniel,

Store the SAP_BUILDT sca in the cms inbox folder.

Goto CMS --> landscape configurator --> check in the archive --> and import into development.

Regards,

Thulasi

[Former Member · Accepted solution]

Guys,

Thanks for your help.

Is this SCA SAP_BUILDT important for deployment ?

Or just when doing the build ?

Because the issue i m facing is that i managed to create my application sca file successfully. e.g my_app.sca file through the assembly tab in CMS but when i import under test tab, i have deployment error. So i m wondering whether it could be due to this old version of SAP_BUILDT currently deployed on the TEST server.

The following are currently on my TEST server:

SAP-JEE 7.00 SP13 (1000.7.00.13.0.20070812015311)

SAP_JTECHS 7.00 SP13 (1000.7.00.13.0.20070812015951)

SAP_BUILDT 6.40 SP12 (1000.6.40.12.0.20050422050022)

I thought this SAP_BUILDT should only affect the built and not deployment. Correct me if i m wrong ?

Thanks loads.

Rgds,

Daniel

[Former Member · Accepted solution]

A dump of the exception i m getting.

Anyone has a clue or advice of how to overcome this problem ?

20081107165952 Info :Nov 7, 2008 4:46:03 PM Info: Starting: Update: Selected development component 'appl/main'/'com.diagonal'/'dev_devcias_C'/'823'/'0' updates currently deployed development component 'appl/main'/'com.diagonal'/'LOKAL'/'0.2006.01.12.14.18.23'/'0'.

20081107165952 Info :Nov 7, 2008 4:46:03 PM Info: SDA to be deployed: /usr/sap/WS5/JC00/SDM/root/origin/com.diagonal/appl/main/dev_devcias_C/0/823/appl~main.sda

20081107165952 Info :Nov 7, 2008 4:46:03 PM Info: Software type of SDA: J2EE

20081107165952 Info :Nov 7, 2008 4:46:03 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

20081107165952 Info :Nov 7, 2008 4:46:07 PM Info: Begin of log messages of the target system:

20081107165952 Info :08/11/07 16:46:03 - ***********************************************************

20081107165952 Info :08/11/07 16:46:04 - Start updating EAR file...

20081107165952 Info :08/11/07 16:46:04 - start-up mode is lazy

20081107165952 Info :08/11/07 16:46:04 - EAR file updated successfully for 70ms.

20081107165952 Info :08/11/07 16:46:04 - Start updating...

20081107165952 Info :08/11/07 16:46:06 - EAR file uploaded to server for 861ms.

20081107165952 Info :08/11/07 16:46:07 - ERROR: Not updated. Deploy Service returned ERROR:

20081107165952 Info : java.rmi.RemoteException: Cannot deploy application com.diagonal/appl~main..

20081107165952 Info : Reason: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:

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

20081107165952 Info : at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:681)

20081107165952 Info : at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)

20081107165952 Info : at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:313)

20081107165952 Info : at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)

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

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

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

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

20081107165952 Info : at java.security.AccessController.doPrivileged(AccessController.java:215)

20081107165952 Info : at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

20081107165952 Info : at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

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

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

20081107165952 Info : at com.sap.engine.services.webdynpro.WebDynproContainer.makeUpdate(WebDynproContainer.java:1281)

20081107165952 Info : at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)

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

20081107165952 Info : at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)

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

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

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

20081107165952 Info : at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:669)

20081107165952 Info : ... 10 more

20081107165952 Info : For detailed information see the log file of the Deploy Service.

20081107165952 Info :08/11/07 16:46:07 - ***********************************************************

20081107165952 Info :Nov 7, 2008 4:46:07 PM Info: End of log messages of the target system.

20081107165952 Info :Nov 7, 2008 4:46:07 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

20081107165952 Info :Nov 7, 2008 4:46:07 PM Error: Aborted: development component 'appl/main'/'com.diagonal'/'dev_devcias_C'/'823'/'0', grouped by :

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

20081107165952 Info :java.rmi.RemoteException: Cannot deploy application com.diagonal/appl~main..

20081107165952 Info :Reason: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:

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

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

20081107165952 Info :Nov 7, 2008 4:46:07 PM Info: Starting to save the repository

20081107165952 Info :Nov 7, 2008 4:46:07 PM Info: Finished saving the repository

20081107165952 Info :Nov 7, 2008 4:46:07 PM Info: Starting: Update: Selected software component 'CIAS_WD_APPLICATIONS'/'diagonal.com'/'dev_devcias_C'/'1000.1.0.6.0.20081107075633''/'0' updates currently deployed software component 'CIAS_WD_APPLICATIONS'/'diagonal.com'/'dev_devcias_C'/'1000.1.0.0.0.20061122075934''/'1'.

20081107165952 Info :Nov 7, 2008 4:46:07 PM Error: Aborted: software component 'CIAS_WD_APPLICATIONS'/'diagonal.com'/'dev_devcias_C'/'1000.1.0.6.0.20081107075633''/'0':

20081107165952 Info :Failed deployment of SDAs:

20081107165952 Info :development component 'appl/main'/'com.diagonal'/'dev_devcias_C'/'823'/'0' : aborted

20081107165952 Info :Please, look at error logs above for more information!

20081107165952 Info :Nov 7, 2008 4:46:07 PM Info: Starting to save the repository

20081107165952 Info :Nov 7, 2008 4:46:08 PM Info: Finished saving the repository

20081107165952 Info :Nov 7, 2008 4:46:08 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

20081107165952 Info :Nov 7, 2008 4:46:08 PM Error: -

---

At least one of the Deployments failed -

---

20081107165952 Info :end of log

20081107165952 Info :RC of deployment: 12

20081107165952 Info :Step SDM-deploy ended with result 'fatal error' ,stopping execution at 2008-11-07 16:59:52.0155 +9:00

[Former Member · Accepted solution]

Daniel,

there are more than one application with same name.

try to change the appliccation of the dc com.diagonal/appl~main.

if that doesnot work redeploy it

Thanks

Bala Duvvuri

[Former Member · Accepted solution]

Hi Bala,

Thanks for your answer. Indeed there were another application with the same name.

Problem solved.

Regards,

Daniel