Error in SDM-deploy Step

[Former Member]

<h5>Good Morning Gentleman,</h5>

<h5>"When i'm trying to import a transport order to our productive system the import fails in step SDM-deploy with the following error:</h5>

<h5>20120228122646 Info :Starting Step SDM-deploy at 2012-02-28 12:26:46.0143 +0:00

20120228122646 Info :start deployment of archives:http://sapsps.sonaesierra.com:50004

20120228122646 Fatal :caused by Exception:com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.:The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.

com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.

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

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

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

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

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

at $Proxy225.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:1640)

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

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

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

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

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

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

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

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

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(Native Method)

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

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

20120228122646 Info :Step SDM-deploy ended with result 'fatal error' ,stopping execution at 2012-02-28 12:26:46.0306 +0:00"</h5>

<h5>I'm new to NWDI and related subjects. I've already checked:</h5>

<h5>1. Port 50004 is available in the productive system</h5>

<h5>2. J2EE Visual Administrator in productive is accessible by j2ee_admin</h5>

<h5>3. j2ee_admin isn't locked in productive system</h5>

<h5>What more should i check? What could be the reason behind this error?</h5>

<h5>Thank you.</h5>

<h5>Best Regards,</h5>

<h5>Pedro Gaspar</h5>

[hemanth2 · Accepted solution]

Dear Pedro,

Hope you are doing good.

Are you using the correct port and user? Just curious as you mentioned SDM.

Yo should be using port 5<nr>08 and user should be the SDM user to deploy, not j2ee_admin.

50004 is the P4 server port.

Thank you and have a nice day :).

_____________

Kind Regards,

Hemanth

SAP AGS

[Former Member · Accepted solution]

Good Morning Kumar,

If i tell you what happened you're going to laugh... But i'll tell you anyway.

After watching your post i went to the CMS Landscape Configurator in order to look into the configuration. I noticed that the Selected Tool for deployment in the Productive Runtime system was configured as Deploy Controller (this is a NW 7.01 and as far as i've read before... in this version it's advisable to configure it as you told me in your post - SDM Deploy, thanks for that).

So i tried to change it, but nothing happened, i've tried a second time, but the changes wouldn't take effect and no message was generated. I've spent a few hours trying to understand what was happening... So i told to myself, let me try it with another browser (was using Firefox 3.6.27, changed to IE 9.0.8112) and when trying to change the runtime system configuration a message outputs... "... More than one name server configured in SLD"

Immediately searched and got SAP note 1118009 - SLD name-server configuration error in CMS. After executing note steps i was able to change the runtime system tool for deployment, and i could finish the transport.

The difference a message and the browser version can do in your life

Thanks for your reply, which helped me solve the problem.

Best Regards,

Pedro Gaspar

[hemanth2 · Accepted solution]

Dear Pedro,

Good job

Kind Regards,

Hemanth

[junwu]

check if you can ping from nwdi server to the prd

[Former Member]

Hello John,

Thanks for your reply.

Already did that. I can ping the host.

Regards,

Pedro Gaspar