CMS import failed in production : TCSDeployException

[Former Member]

Hi All ,

I am transportind activities from devlopment server to production server through CMS. I could reach till approve step of CMS transport , but import failed in production giving following error

20090408134707 Info :Starting Step SDM-deploy at 2009-04-08 13:47:07.0106 +5:00

20090408134707 Info :start deployment of archives:http://apj2p.asianpaints.com:50004

20090408134707 Fatal :caused by Exception:com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'NWDI_CONNECT' could not be connected to the specified host 'apj2p.asianpaints.com'and port '50004'.:The user 'NWDI_CONNECT' could not be connected to the specified host 'apj2p.asianpaints.com'and port '50004'.

com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'NWDI_CONNECT' could not be connected to the specified host 'apj2p.asianpaints.com'and port '50004'.

at com.sap.cms.tcs.beans.deployer.DeployConnector.openConnection(DeployConnector.java:158)

at com.sap.cms.tcs.beans.TCSDeployBean.performDirectDeployment(TCSDeployBean.java:195)

at com.sap.cms.tcs.beans.TCSDeployObjectImpl0_0.performDirectDeployment(TCSDeployObjectImpl0_0.java:1342)

at com.sap.cms.tcs.beans.TCSDeploy_Stub.performDirectDeployment(TCSDeploy_Stub.java:1386)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)

at $Proxy73.performDirectDeployment(Unknown Source)

at com.sap.cms.tcs.core.SDMDeployTask.processImport(SDMDeployTask.java:302)

at com.sap.cms.tcs.core.SDMDeployTask.process(SDMDeployTask.java:366)

at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)

at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)

at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:447)

at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:176)

at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)

at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:113)

at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:648)

at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:620)

at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:1252)

at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1640)

at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2815)

at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:978)

at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2866)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)

at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

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(AccessController.java:207)

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

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

20090408134707 Info :Step SDM-deploy ended with result 'fatal error' ,stopping execution at 2009-04-08 13:47:07.0787 +5:00

Please Help me to resolve this error.

Regards

Kavita

[Former Member]

Hi Kavitha,

Some of the possibilites:

1) First Check the SDM password (either password may be wrong or new password given) and whether SDM is alive or not.

2) I guess production system is in not sync with DEV or CONS or TEST (please check just suggestion) (check all the components which should be same as in DEV and TEST).

3) Check the Runtime Systems Tab in Track for production.

if all these are in place then definitely there will be no problem.

Regards,

Anil.

[Former Member]

one more thing check whether the user is having required roles or not. If you have done the imports with same user in TEST then its not problem with user also..

[Former Member]

I checked for the user , its password , roles are correct. how to check if SDM is alive or not?? I don't think there is issue in sync as i am facing same error in all tracks

[Former Member]

Hi Kavitha,

Consult your basis consultant and check whether SDM is up or not. at the same time ask whether any change in SDM password.

If you are using NWDS then in java prospective check the j2ee console there you can see whether SDM is alive or not. Otherwise if you the SDM deployed server ip or hostname just ping that in your command prompt.

Regards,

Anil.

[Former Member]

i am worknig on Netweaver CE 7.1. We are not using SDM , v are using deploy port for deployment. and for the user we hv provided with administrator rights so no issue in roles.

[Former Member]

Hi Kavita,

SDM is jlaunch process which starts with your central instance I mean when you start your WAS/Portal. You can look if SDM is up and running with correct port inofrmation using following URL:

http://<servername>:<port no>/sap/monitoring/SystemInfo

There under your CI instance you will see dispatcher; server0 and SDM details. Confirm if SDM is up and running. If its not then you can start SDM jlaunch process manually from:

/usr/sap/<SID>/JC$$/SDM/program/ StartServer.sh if its unix or StartServer.bat if its windows.

And after you start SDM you can confirm if its running from above given URL.

Bhavin

[jeffrushlow]

Hello. Did you find a solution to your problem? We have the same error in our CE environment which does not have SDM.