SDM deployment

i am trying to deploy some missing components and get the following error. I have checked the j2ee_admin in the abap stack for client 001 and the password is the same for visual administrator and in secure store. any ideas?
===========================================================================
Deployment started Fri Feb 01 08:21:29 GMT 2008
===========================================================================
Starting Deployment of com.sap.ip.bi.broadcasting
Deployment of com.sap.ip.bi.broadcasting finished successfully (Duration 4781 ms)
Starting Deployment of com.sap.ip.bi.broadcasting.kmmimes
Deployment of com.sap.ip.bi.broadcasting.kmmimes finished successfully (Duration 4828 ms)
Starting Deployment of com.sap.ip.bi.portalheartbeat
Deployment of com.sap.ip.bi.portalheartbeat finished successfully (Duration 4594 ms)
Starting Deployment of com.sap.ip.bi.portallogger
Deployment of com.sap.ip.bi.portallogger finished successfully (Duration 4531 ms)
Starting Deployment of com.sap.ip.bi.portalnavigation
Deployment of com.sap.ip.bi.portalnavigation finished successfully (Duration 4515 ms)
Starting Deployment of com.sap.ip.bi.portalrfc
Deployment of com.sap.ip.bi.portalrfc finished successfully (Duration 4516 ms)
Starting Deployment of com.sap.ip.bi.portalrfctest
Deployment of com.sap.ip.bi.portalrfctest finished successfully (Duration 4484 ms)
Starting Deployment of com.sap.ip.bi.biloggingconfig
Aborted: development component 'com.sap.ip.bi.biloggingconfig'/'sap.com'/'SAP AG'/'7.0007.20060316173253.0000', grouped by software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.00.7.0.20060319093500':
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [OFCOMTOLS039] with user name: [J2EE_ADMIN]                     Check your login information.                     Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.checkLoginCredentials.DMEXC)
Deployment of com.sap.ip.bi.biloggingconfig finished with Error (Duration 6594 ms)
Starting Deployment of BI-IBC
Aborted: software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.00.7.0.20060319093500':
No further description found.
Deployment of BI-IBC finished with Error (Duration 3968 ms)

Hello Mike,
Your issue is described in note 997810:
If deployment fails with the error:                                                                               
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.         
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [sapmef1d] with user name: [Administrator] Check your login information.                                        
Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext.
[Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)                                          
Either the connection details in Secure Store are incorrect, or the j2ee engine is not running at all. First check the admin/port/<SID>entry in Secure Store and make sure it corresponds to the p4 port on the dispatcher. If the j2ee engine is not running (no jlaunch processes on os level), check the std_<XXX> and dev_<XXX> files in  the instance work folder, located on the same level as the j2ee one.
Regards,
Ventsi Tsachev
Technology Development Support (J2EE Engine)
SAP Labs, Palo Alto, Ca (USA)

Similar Messages

  • J2ee Admin User locked on SDM Deployment - BI 7.0 and EP 7.0

    Hi,
    We had a recent issue on BI iview publishing from the BEX WAD 7.0 in our Production Portal server.
    The BEX WAD had the error " Java communication error"
    " An Error occured during communication with the BI Components of the J2ee engine"
    We traced down to identify that the current stack NW 7.0 SP14 BI Components had issues and had to patch to the next level
    However, during deployment of the patch using SDM, the components (all) failed posting the following error. The SDM deployment got struck and the J2ee Engine user j2ee_admin was locked.
    Only a restart of the j2ee engine is allowing us to get the Visual Admin connected. But the SDM deployment again is failing and admin user gets locked. Is there any tested solution to solve this.
    Kindly help asap.
    Trace:
    SDM:
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [xxxx] with user name: [j2ee_admin]check your login information.
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]          
    J2ee Engine:
    Error while connecting
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: This call must be performed from a system thread.
         at com.sap.engine.services.security.login.SecuritySession.setExpirationPeriod(SecuritySession.java:479)
         at com.sap.engine.services.security.login.TicketGenerator.getSecuritySession(TicketGenerator.java:180)
         at com.sap.engine.services.security.login.SecurityContext.load(SecurityContext.java:313)
         at com.sap.engine.services.rmi_p4.Message.loadContextObject(Message.java:345)
         at com.sap.engine.services.rmi_p4.Message.parseMessage(Message.java:239)
         at com.sap.engine.services.rmi_p4.Message.getByteArrayInputStream(Message.java:314)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:212)
         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)

    Hi Anup,
    The restart unlocks the j2ee engine admin user and i am able to login to Visual admin and SDM and not otherwise (SDM is hanged and doesnot allow another session and hence only restart helps me to get into SDM again)
    Admin Pwds reset etc from config tool secure store and all possible solutions have been tried before restart.
    However, after restart, when we try to deploy again, the deploy fails saying the same msg
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [xxx] with user name: [j2ee_admin]check your login information.
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
    Any clues ?
    Regards
    Venkat.

  • SDM Deployment fails - Dependency caf/core/ear missing

    crosspost from: SDM Deployment fails - Dependency caf/core/ear missing
    deploying a DC from NWDS into SDM the following Exception is thrown:
    07.01.2008 16:20:38 /userOut/daView_category (eclipse.UserOutLocation) [ThreadDeploy Thread,5,main] INFO:
    002Additional log information about the deployment
    <!LOGHEADERSTART/>
    <!HELPManual modification of the header may cause parsing problem!/>
    <!LOGGINGVERSIONhttp://1.5.3.7185 - 630/>
    <!NAME[/usr/sap/IT1/DVEBMGS00/SDM/program/log/sdmcl20080107151422.log]/>
    <!PATTERNhttp://sdmcl20080107151422.log/>
    <!FORMATTERcom.sap.tc.logging.TraceFormatter(%24d %s: %m)/>
    <!ENCODINGUTF8/>
    <!LOGHEADEREND/>
    Jan 7, 2008 4:14:22 PM Info:
    Starting deployment
    Jan 7, 2008 4:14:22 PM Info: Error handling strategy: OnErrorStop
    Jan 7, 2008 4:14:22 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    Jan 7, 2008 4:14:22 PM Info: Update strategy: UpdateAllVersions
    Jan 7, 2008 4:14:22 PM Info: Starting deployment prerequisites:
    Jan 7, 2008 4:14:23 PM Info: Loading selected archives...
    Jan 7, 2008 4:14:23 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23425innobis.dewkbtmetadata.ear'
    Jan 7, 2008 4:14:24 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23426innobis.dewkbtear.ear'
    Jan 7, 2008 4:14:24 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23427innobis.dewkbtdictionary.sda'
    Jan 7, 2008 4:14:25 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23428innobis.dewkbtpermissions.ear'
    Jan 7, 2008 4:14:26 PM Info: Selected archives successfully loaded.
    Jan 7, 2008 4:14:26 PM Error: Unresolved dependencies found for the following SDAs:
    1.: development component 'wkbt/ear'/'innobis.de'/'NetWeaver Developer Studio'/'20080107144202'/'0'
    dependency:
    name: 'caf/core/ear'
    vendor: 'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    Deployment will be aborted.
    Jan 7, 2008 4:14:26 PM Error: Prerequisites were aborted.
    Jan 7, 2008 4:14:27 PM Error: Error while creating deployment actions.
    system:
    sap.com/SAP-JEECOR 7.00 SP10 (1000.7.00.10.0.20061026144500)
    sap.com/SAP-JEE 7.00 SP10 (1000.7.00.10.0.20061026144500)
    I checked http://<srv>/sap/monitoring/ComponentInfo
    the missing 'caf/core/ear' is not listed, however several other CAFs are:
    sap.com caf/core null (964250) SAP AG MAIN_APL70VAL_C 20061212133926 sap.com/CAF
    sap.com caf/core/dict null (964586) SAP AG MAIN_APL70VAL_C 20061212131613 sap.com/CAF
    sap.com caf/core/gp/facade/backgroundco/ear null (964227) SAP AG MAIN_APL70VAL_C 20061212134201 sap.com/CAF
    sap.com caf/core/metadata null (963689) SAP AG MAIN_APL70VAL_C 20061212133653 sap.com/CAF
    etc....
    Is it possible to deploy this missing caf-ear component supplementary?
    I have the strange feelings caf/core/ear is something 7.1 CE only related....
    thanks for any hint!
    kai

    Kai, I didn't mean to offend you. But good forum practice is to avoid duplicate posts.
    Regards,
    \-- Vladimir

  • SDM deployment error during XI 3.0 installation

    (nobody in the PI forum replied, so I'm reposting here)
    I need to install a sandbox using this old version. Installation base is 6.40 WebAS plus Java addon SR1. System installs fine, however during final SDM deployment I get a problem during the J2EE engine restart:
    errors:
    service sld ================= ERROR =================
    Cannot start service com.sap.aii.af.cpa.svc; it has hard reference to service sld which is not started.
    and around 20 more services which have a dependency on sld
    sld does not start because:
    /Applications/SLD#sap.com/com.sap.lcr#com.sap.lcr.sagent.BuilderDirector#J2EE_
    GUEST#328####e4cd3451819411dec19c001d72bd0666#SAPEngine_Application_Threadimpl:3_0##0#0#Error#1#com.sap.lcr.sagent.BuilderDirector#Plain###Can't access http store#
    OR:
    SAPEngine_System_Threadimpl:5_32##0#0#Error#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service sld error. Nested exception is: com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='sld_3012', A
    rguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key sld_3012
    at com.sap.sldserv.SldServerFrame.start(SldServerFrame.java:109)
    at com.sap.sldserv.SldServerFrame.start(SldServerFrame.java:78) ...........
    further suspicious warnings:
    Aug 5, 2009 12:51:17 AM Info: No action: Selected development component 'com.sap.aii.af.ms.svc'/'sap.com'/'SAP AG'/'3.0.0920041027171222.0000' will not be deployed because containing software component 'SAP-XIAFC'/'sap.com'/'SAP AG'/'1000.3.0.9.1.20041028052722' will not be deployed.
    and this for around 20 more components from comp.sap.aii*
    What went wrong, and, what can I do to fix this? Redeploy sld ? I could not find how.
    Java version is latest 1.4.2 x86_64 from IBM (1.4.2_13) for my architecture (x86_64 Linux RHEL5), DB is maxdb 7.6
    Any help is appreciated, Thanks.
    Sanjay

    Can you please check thet if you have given a central SLD then that SLD is up and running as you are getting the message.
    Cannot start service com.sap.aii.af.cpa.svc; it has hard reference to service sld which is not started.
    Please check this note it will solve your issue.
    Note 994433 - XI AF on J2EE Engine terminates with OutOfMemoryError
    you can manually start th services.
    Thanks Rishi Abrol

  • Error in SDM-deploy Step

    <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>

    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

  • SAP SDM Deployment failed

    Hello everybody i have a problem with my SAP ERP Installation the Error is :
    An error occurred while processing service SAP ERP 6.0 Support Release 3 > SAP Systems > Oracle > Central System > Central System( Last error reported by the step :uncaught exception: nw.sdm.deploymentErrorWithLog: SDM deployment failed for at least one of the components to be deployed. SOLUTION: Check C:\Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst.log for more information. (in script unknown, line 0:
    And here are my logfile , i hope you can help me for a solution. I have restart the SAP System and start it again and click retry but nothing happen, the same error comes again.
    Jan 19, 2010 7:34:14 AM  Info: Initial deployment: Selected development component 'tc/kmc/bc.uwl.ui/wd_pp'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'1' will be deployed.
    Jan 19, 2010 7:34:14 AM  Info: No action: Selected development component 'com.sap.portal.nav.ws.NavigationWSEar'/'sap.com'/'SAP AG'/'7.0014.20071210113331.0000'/'2' will not be deployed because containing software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210193159''/'2' will not be deployed.
    Jan 19, 2010 7:34:14 AM  Info: No action: Selected development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'3' will not update currently deployed development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'2'.
    Jan 19, 2010 7:34:14 AM  Info: No action: Selected development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'3' will not update currently deployed development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'1'.
    Jan 19, 2010 7:34:14 AM  Info: No action: Selected development component 'com.sap.prt.ws.container'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'2' will not be deployed because containing software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210152356''/'2' will not be deployed.
    Jan 19, 2010 7:34:14 AM  Info: Ending deployment prerequisites. All items are correct.
    Jan 19, 2010 7:35:49 AM  Info: Saved current Engine state.
    Jan 19, 2010 7:35:49 AM  Info: Starting: Initial deployment: Selected development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3' will be deployed.
    Jan 19, 2010 7:35:49 AM  Info: SDA to be deployed: C:\usr\sap\DRC\DVEBMGS00\SDM\root\origin\sap.com\caf\eu\gp\ws\msosrv\MAIN_APL70VAL_C\3\963790\sap.com_cafeugpwsmsosrv.sda
    Jan 19, 2010 7:35:49 AM  Info: Software type of SDA: J2EE
    Jan 19, 2010 7:35:49 AM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Jan 19, 2010 7:35:56 AM  Info: Begin of log messages of the target system:
    10/01/19 07:35:50 -  ***********************************************************
    10/01/19 07:35:51 -  Start updating EAR file...
    10/01/19 07:35:51 -  start-up mode is lazy
    10/01/19 07:35:51 -  EAR file updated successfully for 47ms.
    10/01/19 07:35:51 -  Start deploying ...
    10/01/19 07:35:51 -  EAR file uploaded to server for 32ms.
    10/01/19 07:35:56 -  ERROR: NOT deployed. The Deploy Service returned the following error:
                         For detailed information see the log file of the Deploy Service.
                         Exception is:
                         com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
                              at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700)
                              at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688)
                              at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
                              at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427)
                              at java.lang.Thread.run(Thread.java:534)
    10/01/19 07:35:56 -  ***********************************************************
    Jan 19, 2010 7:35:56 AM  Info: End of log messages of the target system.
    Jan 19, 2010 7:35:56 AM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Jan 19, 2010 7:35:56 AM  Error: Aborted: development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3', grouped by software component 'SAP-EU'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071210153525''/'3':
    Caught exception during application deployment from SAP J2EE Engine's deploy API:
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: NOT deployed. The Deploy Service returned the following error: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
    Exception is:
    com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
         at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700)
         at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688)
         at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
         at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427)
         at java.lang.Thread.run(Thread.java:534)
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
    Jan 19, 2010 7:35:56 AM  Info: Starting to save the repository
    Jan 19, 2010 7:35:57 AM  Info: Finished saving the repository

    Hi,
    Check below thread:
    /message/441671#441671 [original link is broken]
    Thanks
    Sunny

  • SDM Deploy Tool

    Hi,
    I need to know what are the requirements that the war file and ear file
    shoud be complience with the SDM deployment tool beacuse we can not do the deploy and we think that our war and ear are not complience with SDM.
    Regards,
    Sérgio Salomã

    Hi,
    Yes, it should be in format that SDM can support.
    Thanks
    Sunny

  • Difference Between SDM Deployment and JSPM

    Hello All,
    Can anybody tell me the difference between SDM Deployment and JSPM.
    please guide me in brief or guide any URL
    Thanks & Regards
    Shishir

    Shishir,
    Do refer the following links
    Java Support Package Manager (JSPM) - http://help.sap.com/saphelp_nw04s/helpdata/EN/87/4797422930c56ae10000000a155106/frameset.htm
    Software Deployment Manager (SDM) - http://help.sap.com/saphelp_nw04/helpdata/en/22/a7663bb3808c1fe10000000a114084/frameset.htm
    The first page of the links itself describes the purpose of the tools. Also, do use the search features of the forum and search on help.sap.com. Most of the queries are already asked or present in the help documentation.
    Thanks,
    GLM

  • SDM Deployment Failed--SDM could not start the J2EE cluster on the DB Host

    HI,
    I am trying to deploy ESS packges in EP through SDM.But while deploying I am getting this error in SDM at the start itself:-
    Error: An error occured while starting a cluster instance.
    Oct 14, 2008 5:14:41 PM  Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
    Please check if there is an appropriate running cluster instances
    SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
    There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
    I am pasting the full LOG File details:-
    Oct 14, 2008 6:32:00 PM  Info: Starting cluster instance processes.
    Oct 14, 2008 6:32:00 PM  Error: An error occured while starting a cluster instance.
    Oct 14, 2008 6:32:00 PM  Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage . The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
    Name:JM_T1223989073901_0_CPCAPP109
    Host:SBPEPCI1
    State:5
    HostAddress:172.17.131.38
    Name:JC_CPCAPP109_EPP_01
    Host:CPCAPP109
    State:5
    HostAddress:172.17.131.31
    Please check if there is an appropriate running cluster instances.
    Oct 14, 2008 6:32:00 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Oct 14, 2008 6:32:00 PM  Error: Aborted: development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0', grouped by software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
    SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
    There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage .
    The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
    Name:JM_T1223989073901_0_CPCAPP109
    Host:SBPEPCI1
    State:5
    HostAddress:172.17.131.38
    Name:JC_CPCAPP109_EPP_01
    Host:CPCAPP109
    State:5
    HostAddress:172.17.131.31
    Please check if there is an appropriate running cluster instances.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
    Oct 14, 2008 6:32:04 PM  Info: Starting to save the repository
    Oct 14, 2008 6:32:05 PM  Info: Finished saving the repository
    Oct 14, 2008 6:32:07 PM  Info: Starting: Initial deployment: Selected software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0' will be deployed.
    Oct 14, 2008 6:32:07 PM  Error: Aborted: software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
    Failed deployment of SDAs:
    development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0' : aborted
    Please, look at error logs above for more information!
    I have checked the CONFIGTOOl and the properties seem to be OK.
    I tried SHUTTING DOWN all APPLICATION servers & Restarting the DEPLOYMENT,but it still Failed
    Pls suggest.
    Regards,
    Abhijeet
    I

    Hi George,
    Thnx for your reply.
    I have stopped all Application servers and kept only the CI-DB instances running.Retried deploying the ESS packages but still getting the same error.
    Have checked the Visual admin,it is not in SAFE mode,it working normally.
    Have alos checked the CLUSTER Manager Property Values in both Visual Admin & Config Tool,they are alright.
    About the Cluster Resources,can you pls specify what exactly do you mean by "Cluster Resources are running or not".
    I think if the application servers are stopped,then the Cluster resources shudnt come into play right?? Correct me if I am wrong.
    Kindly suggest what other steps I shud take.
    Regards,
    Abhijeet

  • SDM deployment aborted error

    Hi,
    I am getting the following error while trying to deploy SAPESS13_0-20000512 on SDM. :
    Starting Deployment of ess/lwegp
    Aborted: development component 'ess/lwegp'/'sap.com'/'MAIN_ERP05VAL_C'/'2513885'/'2', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101950''/'2':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/ess_lwegp.ear. Reason: None of the available containers recognized the components of application sap.com/ess~lwegp; it is not possible to make deploy.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of ess/lwegp finished with Error (Duration 18066 ms)
    Can anyone please tell me why I am getting this error ?
    Regards,
    Aditi

    Hi Pradeep,
    Which component are you talking about ? I am trying to deploy XSS components .
    I have already deployed SAPPCUI_GP sucessfully without error. Only while deploying SAPESS13, I am getting the above mentioned error.

  • SDM deploy af atleast one item aborted

    Hi,
    We are not able to deploy ear file on server and getting exception "Deploy of atleast one item aborted". Till now we have tried below solutions for fixing the same:
    Restart SDM both from MMC and Console.
    Changed SDM password.
    Enable/Disable SDM from JCMON.
    Restart J2EE server.
    Changed NWDS workspace and deploy fresh ISA application.
    Tried to deploy from SDM GUI.
    After all these attempts we are still not able to deploy. Attached is SDM Log file for this problem.
    Looking forward for valuable thoughts on this......
    Dec 31, 2014 2:10:46 AM  Info: Start file transfer to E:\usr\sap\CRQ\JC00\SDM\program\temp\temp3728619115795722000Saltestapp_ear.ear Dec 31, 2014 2:10:47 AM  Info: File transfer of E:\usr\sap\CRQ\JC00\SDM\program\temp\temp3728619115795722000Saltestapp_ear.ear finished for 296 ms. Total file size is 30508322 bytes. Dec 31, 2014 2:10:47 AM  Info: The SDM client uses an old SDM client API. Dec 31, 2014 2:10:47 AM  Info: -------------------------- Starting deployment ------------------------ Dec 31, 2014 2:10:47 AM  Info: Error handling strategy: OnErrorStop Dec 31, 2014 2:10:47 AM  Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop Dec 31, 2014 2:10:47 AM  Info: Update strategy: UpdateAllVersions Dec 31, 2014 2:10:47 AM  Info: Starting deployment prerequisites: Dec 31, 2014 2:10:47 AM  Info: Loading selected archives... Dec 31, 2014 2:10:47 AM  Info: Loading archive 'E:\usr\sap\CRQ\JC00\SDM\program\temp\temp3728619115795722000Saltestapp_ear.ear' Dec 31, 2014 2:10:47 AM  Info: Selected archives successfully loaded. Dec 31, 2014 2:10:47 AM  Info: Actions per selected component: Dec 31, 2014 2:10:47 AM  Info: Initial deployment: Selected development component 'Saltestapp_ear'/'sap.com'/'localhost'/'2014.12.31.02.10.28'/'0' will be deployed. Dec 31, 2014 2:10:47 AM  Info: Ending deployment prerequisites. All items are correct. Dec 31, 2014 2:10:47 AM  Info: Saved current Engine state. Dec 31, 2014 2:10:47 AM  Info: Starting: Initial deployment: Selected development component 'Saltestapp_ear'/'sap.com'/'localhost'/'2014.12.31.02.10.28'/'0' will be deployed. Dec 31, 2014 2:10:47 AM  Info: SDA to be deployed: E:\usr\sap\CRQ\JC00\SDM\root\origin\sap.com\Saltestapp_ear\localhost\0\2014.12.31.02.10.28\temp3728619115795722000Saltestapp_ear.ear Dec 31, 2014 2:10:47 AM  Info: Software type of SDA: J2EE Dec 31, 2014 2:10:47 AM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) ***** Dec 31, 2014 2:10:54 AM  Info: Begin of log messages of the target system: 14/12/31 02:10:47 -  *********************************************************** 14/12/31 02:10:48 -  Start updating EAR file... 14/12/31 02:10:48 -  start-up mode is lazy 14/12/31 02:10:51 -  EAR file updated successfully for 2806ms. 14/12/31 02:10:51 -  Start deploying ... 14/12/31 02:10:54 -  EAR file uploaded to server for 2892ms. 14/12/31 02:10:54 -  ERROR: Not deployed. Deploy Service returned ERROR:                      com.sap.engine.services.rmi_p4.MarshalException: Exception when trying to read the original exception.; nested exception is:                      java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.microsoft.sqlserver.jdbc.StreamError                      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:732)                      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:714)                      at com.sap.engine.services.rmi_p4.Call.getResultStream(Call.java:200)                      at com.sap.engine.services.deploy.DeployService_Stub.deploy(DeployService_Stub.java:507)                      at com.sap.engine.deploy.manager.DeployManagerImpl.deployUpdateAction(DeployManagerImpl.java:709)                      at com.sap.engine.deploy.manager.DeployManagerImpl.deploy(DeployManagerImpl.java:513)                      at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:188)                      at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)                      at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)                      at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)                      at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)                      at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)                      at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)                      at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)                      at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)                      at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)                      at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)                      at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:128)                      at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:97)                      at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:68)                      at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)                      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.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)                      at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)                      at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)                      at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)                      at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)                      at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)                      at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)                      at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)                      at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)                      at java.lang.Thread.run(Thread.java:683)                      Caused by: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.microsoft.sqlserver.jdbc.StreamError                      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1292)                      at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1887)                      at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1811)                      at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1695)                      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1288)                      at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1887)                      at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1811)                      at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1695)                      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1288)                      at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1887)                      at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1811)                      at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1695)                      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1288)                      at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1887)                      at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1811)                      at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1695)                      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1288)                      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:336)                      at com.sap.engine.services.rmi_p4.Call.getResultStream(Call.java:195)                      ... 32 more                      Caused by: java.io.NotSerializableException: com.microsoft.sqlserver.jdbc.StreamError                      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1070)                      at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1364)                      at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1336)                      at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1280)                      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1068)                      at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1364)                      at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:376)                      at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:998)                      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 java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:837)                      at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1326)                      at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1280)                      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1068)                      at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1364)                      at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1336)                      at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1280)                      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1068)                      at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1364)                      at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1336)                      at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1280)                      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1068)                      at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:285)                      at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:147)                      at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:332)                      at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)                      at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)                      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)                      For detailed information see the log file of the Deploy Service. 14/12/31 02:10:54 -  *********************************************************** Dec 31, 2014 2:10:54 AM  Info: End of log messages of the target system. Dec 31, 2014 2:10:54 AM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) ***** Dec 31, 2014 2:10:54 AM  Error: Aborted: development component 'Saltestapp_ear'/'sap.com'/'localhost'/'2014.12.31.02.10.28'/'0': Caught exception during application deployment from SAP J2EE Engine's deploy service: com.sap.engine.services.rmi_p4.MarshalException: Exception when trying to read the original exception.; nested exception is: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.microsoft.sqlserver.jdbc.StreamError (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC) Dec 31, 2014 2:10:54 AM  Info: Starting to save the repository Dec 31, 2014 2:10:54 AM  Info: Finished saving the repository for 74 ms. Dec 31, 2014 2:10:54 AM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process. Dec 31, 2014 2:10:54 AM  Error: ---------------- At least one of the Deployments failed ---------------
    Kind Regards,
    Vishal Sobti

    Hi Vihsal,
    Can you please try to kill this from Operating System level. One more question, are you deploying this first time? Reason of asking this question is your below error code.
    "ERROR: Not deployed. Deploy Service returned ERROR:   com.sap.engine.services.rmi_p4.MarshalException: Exception when trying to read the original exception.; nested exception is:   java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.microsoft.sqlserver.jdbc.StreamError at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException"
    Could you please also confirm about the database please.
    Please try the below step as well if not done yet
    Go to SDM Directory and enter the below
    sdm jstartup "mode=integrated"
    Thanks,
    Hamendra

  • SDM Deployment Problem with aii_af_jmsproviderlib

    Hi
    When I try to deploy aii_af_jmsproviderlib I get the following error:
    "SDM has not calculated any deployment actions.Possible reasons:
    All selected archives have already been deployed before in the same or in a higher version".
    Also, it does not let me select the option: "Update deployed SDA/SCA version" which I need to select based on the documentation. Any suggestions how to fix this?
    Thanks
    Tim

    Hi!
    Could you
    1) give the detail of you modification?
    2) in my META-INF, I only find manifest but no SAP-manifest, why?
    Thanks a lot!

  • SDM Deployment issue

    Hi Guys,
    I am trying to deploy the .jar file for an EJB as a part of adapter module ejb deployment and i am getting the following error
    have an ejb file in .jar and when i try to deploy it using sdm i am getting the following error. any body has the idea
    ) Error loading archive
    C:\Documents and Settings\x10adm\Desktop\EJBXiPayAuthReq.jar
    (server side name is: D:/usr/sap/X10/DVEBMGS01/SDM/program/temp/EJBXiPayAuthReq.jar)
    com.sap.sdm.util.sduread.IllFormattedSduFileException: There is no deployment descriptor found in the SDA manifest
    any help would be really appreciated
    Thanks,
    Srini

    Hello Srini,
    According to J2EE Specifications jar files cannot be deployed to a J2EE Engine.
    I suggest you use the NWDS instead of plain Eclipse.
    In NWDS you have a J2EE perspective, which sould be used for Development for J2EE Componnets like EJBs.
    You need to create EJB Module Project and an Enterprise Application Project.
    The final build product of a Enterprise Application Project will be an .ear file, which will contain the jar file. The ear file will also have the required Deployment Descriptors which can be deployed using SDM or NWDS itself.
    Please refer to this document for Module Development and Deployment. Technically a adapter module is also a EJB.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3bdc14e1-0901-0010-b5a9-a01e29d75a6a
    Please award points if you find this post useful.
    Best Regards,
    Kanwal

  • Sdm deployment error

    Hi all,
    When I tried deploying a simple webdynpro application in the server I get the error like this
    Jul 25, 2007 1:09:01 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [003]Deployment aborted
    Deployment exception : Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !
    1. I tried to connect to sdm via remote_gui and entered password and it connected correctly there without any error.
    2. In NWDS I selected the sap j2ee engine as
    sap j2ee engine is installed on local host
    system name : F06
    J2EE Instance : 30
    SCS Instance : 31
    3.  I went through all the post about this issue and none helped me out.
    Thanks in advance,
    Pls help
    Best Regards,
    Suresh.

    In Window=>Preferences>SAP j2ee Engine.
    I selected
    SAP J2ee Engine installed in local host. Clicked the Browse button and then selected F06.  This populated
    System Name: F06
    J2ee instance:30
    SCS Instance:31
    So what could be the problem.

  • SDM deployment failed (DeployManagerException)

    Dear programmers,
    Since yesterday I'm trying to deploy an EAR file with NetWeaver Developer Studio. But, each time I get this error:
    Apr 25, 2007 10:59:54... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Apr 25, 2007 10:59:56... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Apr 25, 2007 10:59:56... Error: Aborted: development component 'NewsEAR'/'sap.com'/'localhost'/'2007.04.24.11.16.39':
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [cp22383-a] with user name: [admin]
                        Check your login information.
                        Exception is:
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
    Apr 25, 2007 11:00:33... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Apr 25, 2007 11:00:33... Error: -
    At least one of the Deployments failed -
    We did reset the SDM password in de Configtool and in the RemoteGui.bat. All processes seem to work, because they are green.
    We appreciate your help.
    Regards,
    Adri

    We found the solution while looking at my last question, which was almost the same. Thnx anyway
    If you go to User Administration and change the password there, when next time you log in, in the portal you will get an notification that the password is expired. Change it to your liking and your problem is solved
    Adri Kodde

  • SDM Deploy Error

    Hello! I'm deploying a J2EE project and the J2EE Server gives me the following error :
    18-may-2005 14:02:06 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [005]Deployment aborted
    Settings
    SDM host : linux2
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/ADMINI1/CONFIG~1/Temp/temp31738Isicres_J2EE.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/ADMINI1/CONFIG~1/Temp/temp31738Isicres_J2EE.ear
    Aborted: development component 'Isicres_J2EE'/'sap.com'/'localhost'/'2005.05.18.13.59.43':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Cannot deploy application sap.com/Isicres_J2EE.. Reason: null; nested exception is:      java.lang.NullPointerException (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    I haven't idea to solve this problem!! any help, please?
    Thank you

    Hi Carlos,
    You can find the root exception in the defaultTrace.trc file under /usr/sap/<SID>/<INSTANCE>/j2ee/cluster/server<N>/log.
    Hope it helps,
    Vladimir

Maybe you are looking for