JCo Nullpointer ISA4.0 SP5

Hi,
i try to establish a Custom JCo-Connection in Internet Sales 4.0 SP5 PI (WebShop).
I always get a NullPointerException when calling the method: 
<b>getDefaultJCoConnection()</b>
(from BackendBusinessObjectBaseSAP)
I guess, it tries to get a reference to the properties from config-data.xml in an non-existing Map.
I'am using Standard JCo-Calls as workaround at the moment and they work perfectly. So i assume they problem is with the configuration.
Any ideas?
(XCM)-Configuration ??
tia,
Rainer

hi,
The getJcoConnection() methid works only in the Impl Classes. I hope you have written the code in that.
If we try to get the DEfault JCo Connection then it won't work as it requires to follow the Struts Architecture.
Let me know if you need further help
I have done that in ISA3.1 - but i feel that it should be the same
Thanks
Sam

Similar Messages

  • SLD - Create JCO - nullpointer

    Hello,
    When i try to create a jco destination in my SLD (2004s SP13), i get a nullpointer exception (see below). The sld is configured correctly, and technical systems too, because when i use the SLD from my CE 7.1 i can create a JCO for the technical systems...
    It's just something in the webdynpro for creating JCO's in my SLD that triggers the nullpointer exception. Is it possible to redeploy the SLD applications for creating JCO destinations?
    Kind regards,
    J.
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:285)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:250)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:157)
         at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         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:313)
         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:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

    Hi,
    If your SLD is configured correctly (try the test SLD connection in webdynpro content administration), you can try the following things:
    1. in the SLD -> technical Systems -> Web AS Java , choose the JCO Destinations tab, there u can remove some jco destinations if you want.
    2. In the  visual administrator, where u did the configuration, send the data again to your SLD (this will remove outdated applications in the SLD)
    This solved the issue for me.
    Kind regards,
    Joren

  • Nullpointer in 'weblogic.transaction.internal.CoordinatorImpl

              I am using Weblogic 6.1 SP4 on JDK 1.3.1 on AIX.
              My server has a transacted EJB which accesses Oracle and DB2 databases. I have
              been running my application for several months.
              Suddenly, yesterday it starting spitting out these exceptions a few times a minute.
              I cannot find the configuration change I made that would have caused this to
              suddenly start appearing. My code has not changed in 2 weeks.
              Has anyone seen this error before? Does anyone know what causes this, so that
              I can narrow my search?
              Thanks for your help,
              Tania
              ####<Mar 4, 2003 12:35:48 PM CST> <Warning> <Dispatcher> <ksp12025> <cuAS01> <ExecuteThread:
              '5' for queue: 'default'> <system> <> <000000> <RuntimeException thrown by rmi
              server: 'weblogic.rmi.internal.BasicServerRef@105 - jvmid: '-4285102758410085945S:10.1.21.21:[18120,18120,18121,18121,18120,18121,-1]:qdomain4:cuAS01',
              oid: '261', implementation: 'weblogic.transaction.internal.CoordinatorImpl@311671da''>
              java.lang.NullPointerException
              at weblogic.transaction.internal.ServerResourceInfo.isAccessibleAtAndAssignableTo(ServerResourceInfo.java(Compiled
              Code))
              at weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(ServerTransactionImpl.java(Compiled
              Code))
              at weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(ServerTransactionImpl.java(Compiled
              Code))
              at weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransactionImpl.java(Compiled
              Code))
              at weblogic.transaction.internal.SubCoordinatorImpl.startCommit(SubCoordinatorImpl.java(Compiled
              Code))
              at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown
              Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java(Compiled
              Code))
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java(Compiled
              Code))
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java(Compiled
              Code))
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java(Compiled Code))
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              

              Thanks,
              The problem did clear up when the Unix server had to get bounced. I believe it
              was bounced for an unrelated issue.
              The one thing I noticed was that there were a couple of copies of my EJBs in the
              wlnotdelete directory that the server had been previously compliaining about.
              They went away after the Unix server was restarted and the NullPointer problem
              went away.
              We plan to upgrade to 7.1 soon, but will try to move to SP5 if we need to sooner.
              Thanks for your help.
              Tania Rhinehart
              Rajesh Mirchandani <[email protected]> wrote:
              >This is fixed in SP5. Open a case with [email protected] and reference
              >CR092301.
              >
              >Slava Imeshev wrote:
              >
              >> Hi Tania,
              >>
              >> I think you need to contact BEA support at [email protected]
              >>
              >> Regards,
              >>
              >> Slava Imeshev
              >>
              >> "Tania Rhinehart" <[email protected]> wrote in message
              >> news:[email protected]...
              >> >
              >> > I am using Weblogic 6.1 SP4 on JDK 1.3.1 on AIX.
              >> > My server has a transacted EJB which accesses Oracle and DB2 databases.
              > I
              >> have
              >> > been running my application for several months.
              >> > Suddenly, yesterday it starting spitting out these exceptions a few
              >times
              >> a minute.
              >> > I cannot find the configuration change I made that would have caused
              >this
              >> to
              >> > suddenly start appearing. My code has not changed in 2 weeks.
              >> >
              >> > Has anyone seen this error before? Does anyone know what causes
              >this, so
              >> that
              >> > I can narrow my search?
              >> >
              >> > Thanks for your help,
              >> > Tania
              >> >
              >> > ####<Mar 4, 2003 12:35:48 PM CST> <Warning> <Dispatcher> <ksp12025>
              >> <cuAS01> <ExecuteThread:
              >> > '5' for queue: 'default'> <system> <> <000000> <RuntimeException
              >thrown by
              >> rmi
              >> > server: 'weblogic.rmi.internal.BasicServerRef@105 - jvmid:
              >> '-4285102758410085945S:10.1.21.21:[18120,18120,18121,18121,18120,18121,-1]:q
              >> domain4:cuAS01',
              >> > oid: '261', implementation:
              >> 'weblogic.transaction.internal.CoordinatorImpl@311671da''>
              >> >
              >> > java.lang.NullPointerException
              >> > at
              >> weblogic.transaction.internal.ServerResourceInfo.isAccessibleAtAndAssignable
              >> To(ServerResourceInfo.java(Compiled
              >> > Code))
              >> > at
              >> weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(Se
              >> rverTransactionImpl.java(Compiled
              >> > Code))
              >> > at
              >> weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(Se
              >> rverTransactionImpl.java(Compiled
              >> > Code))
              >> > at
              >> weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransa
              >> ctionImpl.java(Compiled
              >> > Code))
              >> > at
              >> weblogic.transaction.internal.SubCoordinatorImpl.startCommit(SubCoordinatorI
              >> mpl.java(Compiled
              >> > Code))
              >> > at
              >> weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown
              >> > Source)
              >> > at
              >> weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java(Compiled
              >> > Code))
              >> > at
              >> weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java(Compi
              >> led
              >> > Code))
              >> > at
              >> weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java(C
              >> ompiled
              >> > Code))
              >> > at
              >> weblogic.kernel.ExecuteThread.execute(ExecuteThread.java(Compiled Code))
              >> > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >> >
              >
              >--
              >Rajesh Mirchandani
              >Developer Relations Engineer
              >BEA Support
              >
              >
              

  • Stop and re-start JCo Idoc Server

    Hi
    I created a JCO IDoc server (using the JCoIDocServer class) , so far it works fine for me to send and receive IDocs to R/3. The only issue is when I try to start and stop the JCO Idoc server at runtime. When I call the Stop method(). It seems like the service is stopped but if i call a Start method after that( even on a completely new class instance) I'm getting a nullpointer exception. I have seen documents on JCOServer says that use suspend method for stop the server, but this is not available for the JCoIDocServer class. How can I stop a server which is running, programaticalluy and restart it again ? (I dont mind if I have to reinstantiate the whole server class) . I use JCO and  IDoc libaray version 3.0 . Please help
    Thanks

    Hi,
    Try using the abort() after your stop in a "if" condition. You need to provide a message as a parameter for the abort() method, so that the remote SAP System (in case the IDoc Server is still connected to it) knows the reason why the IDoc server shutdown without any warning.
    So your code should look something like this (warning pseudo-code ) -
    server.stop();
    if(server.alive())
           server.abort("Forcing shutdown because its wakey wakey eggs and beccy time!");
    Try logging the status of the server after the stop() and abort() methods to know what the server is doing. I hate people using the suspend() method to "stop" the server, because it does not stop the server. It only suspends operations, so your connection and session to the remote SAP System remains open.
    After the time out (can be hours) on the remote System, the connection is closed, but until then, the remote SAP System keeps expecting your server to talk back to it. Open sessions are of course more dangerous than runaway trains, so avoid the suspend() method if you can.
    T00th
    Edited by: Sameer Jagirdar on Jan 21, 2010 1:14 PM --> fixed the code display thingy.
    Edited by: Sameer Jagirdar on Jan 21, 2010 1:15 PM

  • Machines with same Hostnames overwrite WebDynpro JCo Destinations (SLD)

    Hello,
    we are working with NWDI and virtualized Developer Workplace Machines (on VMWare Images). By this, all Developer Workplace machines have the same hostname. This works fine until teams start developing with Webdynpro JCo Destinations (i.e. for Adaptive RFC).
    This is what I think what I figured out what is going on:
    - Webdynpro JCo Destinations are managed on the configured SLD (in our case the NWDI SLD)
    - SLD identifies the JCo Destination by hostname and destination name
    - JCo Destinations are communicated from host to SLD, even though the SLD Data Supplier is configured only for reading SLD content
    In our environment with all developer workplaces having the same hostname, we have the effect, that all devlopers workplaces MUST work with the same JCo Destination. Each time a developer updates the destination for his workplace, this update is written to SLD and therefore the destination of all other workplaces is changed as well.
    So my question is: Is there any option to stop developer workplaces writing their JCo Destinations to the central SLD without loosing the functionality to read other CIM Data from their (Name Reservation, Tehcnical System Landscape) ?
    We are operating Developer Workplaces on following Releases: 6.40 SP15, 6.40 SP17, 7.00 SP12 and 7.10 SP5.
    Any help appreciated,
    Stefan

    Hi Stefan
          As of now we are using Content Administrator to manage and maintaing the JCO destinations to the systems which are configured in SLD.
          If you eliminate this jco destinations or if you want to decide not to use these JCOs ,You have option with JCO API.
    Manually you need to code in your programs to connect any R/3 System.As there is no option to maintain JCO destinations other than Content Admin with SLD configured with land scape.
    Regards
    Kalyan

  • RFC call from MII using JCO

    Hi All,
    I am calling custom function module from MII using JCO and I am facing one problem. Problem is that if any new field is added in function module in ECC side that is not appearing in RFC structure until we restart the MII server. Can anybody provide any solution. I am using MII 12.1 SP5.
    Thanks in Advance
    Chandan

    I faced this same issue. Only one solution is to reset the JCo Proxy by running following URL in the same MII server
    http://<MII Server>/XMII/JCOProxy?mode=reset
    This will reset the JCo cache and the new added fields in RFC at SAP end will be reflected in the Request/Response xml structure of the RFC in BLS
    Regards
    Som

  • Upgrading ECC5.0 to ECC6.0 and Internet Sales ISA4.0 CRM4.0

    We are performing a technical upgrade of ECC5.0 to ECC6.0 and we are seeking confirmation and instructions for connecting our existing ISA4.0 system to ECC6.0.  I have searched OSS and SDN and queried our SAP account manager for some confirmation and documentation on ISA4 and ECC6.0 compatability
    Any advice, confirmation and documentation on connecting Internet Sales version 4.0 component to ECC 6.0 is greatly appreciated.
    Here are the details of our ISA4 system
    Kind regards
    ISA System
    sap.com      SAP-JEE      6.40 SP9 (1000.6.40.9.0.20041119045409)      
    sap.com      com.sap.mw.jco       (6.4009.00.0000.20041026130530.0000)
    sap.com      com.sap.security.dbschema       (6.4009.00.0000.20041115123517.0000)
    sap.com      crm.b2b       (400.200904212104)
    sap.com      crm.b2b_lanl       (400.200904221705)
    sap.com      crm.b2c       (400.1020060105115443.0000)
    sap.com      crm.mcm       (400.1020060105115443.0000)
    sap.com      crm.shopadmin       (400.1020060105115443.0000)
    sap.com      crm.trexr3       (400.1020060105115443.0000)
    sap.com      IAIKSecurityFS       (1.3.12)
    sap.com      isacoreddic       (400.1020060105115443.0000)
    JDK 1.4.2_11-b06
    TREX6.1
    Windows 2003 (x86) 5.2
    Warm regards
    Lee Lewis

    When an incorrect password is entered, the expected message:
    "Name or password is incorrect (Please repeat logon) "
    is displayed.  When the correct password is entered, this message is displayed:
    "Error in user administration"
    No error messages are logged during the login attempt, only the following:
    Message , Datasource
    Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][actionxecution]='end' [actionclass]='com.sapmarkets.isa.isacore.action.b2b.LoginAction' [path]='/b2b/reallogin' [forward]='/b2b/login/login.jsp' [exectime]='94' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
    Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofunctionexecution]='end' [funcname]='BAPI_USER_GET_DETAIL' [ashost]='sapsbx' [sysid]='SBX' [exectime]='31' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
    Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofuncionexecution]='begin' [funcname]='BAPI_USER_GET_DETAIL' [ashost]='sapsbx' [sysid]='SBX' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
    Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofunctionexecution]='end' [funcname]='SUSR_LOGIN_CHECK_RFC' [ashost]='sapsbx' [sysid]='SBX' [exectime]='15' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
    Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofuncionexecution]='begin' [funcname]='SUSR_LOGIN_CHECK_RFC' [ashost]='sapsbx' [sysid]='SBX' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
    Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofunctionexecution]='end' [funcname]='RFC_SYSTEM_INFO' [ashost]='sapsbx' [sysid]='SBX' [exectime]='0' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
    Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofuncionexecution]='begin' [funcname]='RFC_SYSTEM_INFO' [ashost]='sapsbx' [sysid]='SBX' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
    Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][actionxecution]='begin' [actionclass]='com.sapmarkets.isa.isacore.action.b2b.LoginAction' [path]='/b2b/reallogin' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
    Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][actionxecution]='end' [actionclass]='com.sapmarkets.isa.isacore.action.DetermineBrowserVersionAction' [path]='/b2b/login' [forward]='/b2b/reallogin.do' [exectime]='15' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
    Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][actionxecution]='begin' [actionclass]='com.sapmarkets.isa.isacore.action.DetermineBrowserVersionAction' [path]='/b2b/login' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]

  • Java Web App for EP5 SP5

    Hi
    Recently I developed a Java web app for a Portal client.  The client is on EP5 SP5 with ITS and LDAP servers (a 3 server architecture).  I then used the deployment tool to create the necessary ear file and then successfully deployed it to the SAP J2EE Engine.  I then navigated to the following url:
    http://<portal_server>:8100/<web_app>/welcome.jsp
    However I am having trouble with the following:
    1) the jsp pages are not being rendered properly.  in fact welcome.jsp does not have any jsp tags at all but I am still getting a compiling exception.  as soon as I change the extension to .html the page is displayed fine.  issue: why am i not able to view the jsp pages.  error: com.inqmy.services.servlets_jsp.jsp.CompilingException ID 17013
    2) the web app I have developed utilises the sapjco functionality to connect to the relevant R3 system.  in my web app directory structure I have included the necessary sapjco.jar in the WEB-INF/lib directory but get the attached jco error. (I shouldnt need to set the classpath since the sapjaco.jar file must get picked up from WEB-INF/lib directory).  Error: At times I get a NoClassDefFoundError stopping at the line which requires the sapjco.jar file (where it uses JCo.Pool class) and at other times I get the "could not load middleware layer".
    I have tried numerous things to fix it but in vain.  Any thoughts around how I could go about resolving the issues will be greatly appreciated. 
    Willing to provide screenshots if required.
    Cheers
    Ankit

    Hi Alon
    Thanks a lot for the info!!
    I have read the doco you asked me to have a look at and it sounds reasonable.  But the question that I have is that is it possible to successfully include the relevant jar's in the application's WEB-INF\lib folder?? I ask this since I would expect the SAP j2ee class loader to look at the required jar's in the WEB-INF\lib folder?!? (Also the section on "Adding a Reference from a Deployed Application to a Service or Library" talks about an app that may want to use resources from OUTSIDE the application EAR.)
    So if I use any jar's such as sapjco, xerces, activation and mail I will need to add them to the library.txt if they are not already there (which they should be since the portal uses them) and then add the reference in reference.txt.
    Your thoughts will be appreciated.
    Cheers
    Ankit

  • SAP EP5 SP5 Java web app problem

    Hi
    Recently I developed a Java web app for a Portal client. The client is on EP5 SP5 with ITS and LDAP servers (a 3 server architecture). I then used the deployment tool to create the necessary ear file and then successfully deployed it to the SAP J2EE Engine. I then navigated to the following url:
    http://<portal_server>:8100/<web_app>/welcome.jsp
    However I am having trouble with the following:
    1) the jsp pages are not being rendered properly. in fact welcome.jsp does not have any jsp tags at all but I am still getting a compiling exception. as soon as I change the extension to .html the page is displayed fine. issue: why am i not able to view the jsp pages. error: com.inqmy.services.servlets_jsp.jsp.CompilingException ID 17013
    2) the web app I have developed utilises the sapjco functionality to connect to the relevant R3 system. in my web app directory structure I have included the necessary sapjco.jar in the WEB-INF/lib directory but get the attached jco error. (I shouldnt need to set the classpath since the sapjaco.jar file must get picked up from WEB-INF/lib directory). Error: At times I get a NoClassDefFoundError stopping at the line which requires the sapjco.jar file (where it uses JCo.Pool class) and at other times I get the "could not load middleware layer".
    I have tried numerous things to fix it but in vain. Any thoughts around how I could go about resolving the issues will be greatly appreciated.
    Willing to provide screenshots if required.
    Cheers
    Ankit

    Hi Ravi
    I used the SAP J2EE Engine Deploy Tool to create the war and ear archives as well as deploy the ear archive.  As I used this tool I included the required jar files inclusing the sapjco.jar inside WEB-INF\lib of the web archive (WAR).  I tested this in a tomcat environment before deploying it to the portal environment.
    1) The screendump is as below:
    Internal Server Error 500!
    com.inqmy.services.servlets_jsp.server.jsp.CompilingException: ID17013: Error in compiling : java.io.IOException: CreateProcess: javac -encoding UTF8 -nowarn C:\SAP_J2EEngine6.20\alone\services\servlet_jsp\work\jspTemp\changePassword\work\jsp_welcome1092865716140.java -classpath ".;.\system-lib\boot.jar;.\system-lib\jaas.jar;;.;.\additional-lib\jnet.jar;.\additional-lib\jdbc20.jar;.\services\iiop\iiop.jar;.\services\servlet_jsp\servlet_jsp.jar;.\services\p4\p4.jar;.\additional-lib\mail.jar;.\services\dbpool\dbpool.jar;.\additional-lib\connector.jar;.\additional-lib\activation.jar;.\services\deploy\deploy.jar;.\additional-lib\jta.jar;.\services\ts\ts.jar;.\additional-lib\jsse.jar;.\additional-lib\servlet.jar;.\additional-lib\ejb11.jar;.\additional-lib\jms.jar;.\services\ejb\ejb.jar;;C:\SAP_J2EEngine6.20\alone\services\servlet_jsp\work\jspTemp\changePassword\root\WEB-INF\lib\activation.jar;C:\SAP_J2EEngine6.20\alone\services\servlet_jsp\work\jspTemp\changePassword\root\WEB-INF\lib\inqmyxml.jar;C:\SAP_J2EEngine6.20\alone\services\servlet_jsp\work\jspTemp\changePassword\root\WEB-INF\lib\jcoapi.jar;C:\SAP_J2EEngine6.20\alone\D
         at com.inqmy.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:296)
         at com.inqmy.services.servlets_jsp.server.jsp.JSPServlet.getClassName(JSPServlet.java:333)
         at com.inqmy.services.servlets_jsp.server.jsp.JSPServlet.service(JSPServlet.java:207)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:136)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:856)
         at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:598)
         at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:260)
         at com.inqmy.services.httpserver.server.Response.handle(Response.java:164)
         at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:909)
         at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
         at com.inqmy.core.cluster.impl3.ParserRunner.run(ParserRunner.java:30)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:132)
    As advised by you I included the inqmyxml.jar file in the WEB-INF\lib folder for this application.  But it doesnt seem to have made a difference.
    2) for the second issue where sapjco.jar isnt found the error is as seen below.  At line 42 in R3.java I make a  JCO call -
    pool = JCO.getClientPoolManager().getPool(POOL_NAME);
    Error Dump below:
    java.lang.NoClassDefFoundError
         at R3.(R3.java:42)
         at ChangePassword.doPost(ChangePassword.java:76)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:136)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:856)
         at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:598)
         at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:260)
         at com.inqmy.services.httpserver.server.Response.handle(Response.java:164)
         at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:909)
         at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
         at com.inqmy.core.cluster.impl3.ParserRunner.run(ParserRunner.java:30)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:132)
    I would have expected EP5 to be able to find the appropriate jar files.  Especially since it has its own library of jar files to work with.  I was reading some J2EE Engine doco and came across two files library.txt and reference.txt.  Do I need to maintain these files as I deploy my application?
    Your thoughts will be appreciated.
    Cheers

  • Error while selecting Load Balancing in JCO creation

    While creating JCO i am facing this error.It is working fine with Single server connection,but when i chose Load balancing i error comes out.Please tell me the solution.
    I have read couples of forum mentioned you need to start both Portal and ECC.
    For you information my Portal and Java are both on diffrrent Box.
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM  TYPE=B MSHOST=olameccpdvr GROUP=PUBLIC R3NAME=DVR MSSERV=sapmsDVR PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       service 'sapmsDVR' unknown TIME        Thu Feb 24 12:19:54 201 RELEASE     701 COMPONENT   NI (network interface) VERSION     38 RC          -3 MODULE      nixxhsl.cpp LINE        776 DETAIL      NiHsLGetServNo: service name cached as unknown COUNTER     5

    Is your backend system configured correctly in your SLD ?
    Go to transaction SMMS on your backend system that your are connecting to. Click on Goto=>Parameters=>Display. Look for "server port" value.
    This should give you the TCP/IP port for your message server. It could be 3600 or 3601 (36NN - where NN is the instance number).
    In your services file, if you made the entry at the end of the file, press Enter (Return) after your entry.
    Try restarting your server after making the above changes.
    - Shanti

  • Error in creation of JCO with Load balancing server

    Hi,
    We are using a ABAP user base for our WEBAS server 6.40 (with ABAP+JAVA). i have created a Public group in concerned ECC 5.0 system. I have already configured SLD, and then i maintain data supplier bridge in SLD and run RZ70 in ECC 5.0 system to load system information.. i can see details in SLD ..
    now i am trying to create JCO connections .. here i am unable to create JCO with load balancing option..  i get
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM  TYPE=B MSHOST=<servername> GROUP=PUBLIC R3NAME=SID MSSERV=sapms<SID> PCS=1 ERROR       service 'sapms<SID>' unknown TIME        Fri Jun 16 12:41:20 2006 RELEASE     640 COMPONENT   NI (network interface) VERSION     37 RC          -3 MODULE      ninti.c LINE        505 DETAIL      NiPGetServByName2: service 'sapms<SID>' not found SYSTEM CALL getservbyname_r COUNTER     1
    i am able to create single server JCO, but it fails in load balancing.. is there anything i have  missed out in settings...
    Thanks and regards,
    Sudhir

    Thanks, Bogdan Rokosa
    I have the same problem,and solved it following the steps provided by Bogdan Rokosa  :
    you must insert an entry for your R3 system
    (like: sapms<SID> 3600/tcp)
    in services file
    (C:\WINDOWS\system32\drivers\etc\services) on Java WAS.
    I test the Jco successful without restart J2EE Engine.

  • PI 7.11 sp5 post install steps - SLD update hangs in IE browser

    Hello gurus,
    This is my first shot at installing PI ever.  We decided to go with PI 7.1 EHP1 and SP5.  I think the latest may be SP6.
    At any rate, we're doing this on AIX 6.1 and Oracle 10.2.0.4.
    I followed the install Guide exactly.  Did the sapinst, oracle and patch. Next, I manually updated the KERNEL, IGS , JVM, Then I updated SPAM, SAP_BASIS, then all the other abap components.  Then did JSPM and all those components.  Everything matches SP5 for PI 7.11
    https://websmp204.sap-ag.de/maintenanceNWPI71
    SAP_ABA     711     0005     SAPKA71105
    SAP_BASIS     711     0005     SAPKB71105
    PI_BASIS     711     0005     SAPK-71105INPIBASIS
    ST-PI     2008_1_710     0003     SAPKITLRE3
    SAP_BW     711     0005     SAPKW71105
    ST-A/PI     01M_BCO710     0001     SAPKITAB8F
    Now I'm doing the post install steps that are in the instguide.  THere are tons of steps, but let me go over the big ones and where I'm having a problem:
    READ ALL THESE NOTES:
    Note 1309239 - Configuration Wizard: PI NetWeaver initial setup
    Note 1286149 - Configuration Wizard: PI Self Test for NetWeaver
    Note 1107808 - Collective Note: Configuration Wizard 7.1
    Note 1286428 - Configuration Wizard: PI Wizard Templates overview
    Note 1115280 - PI CTC: Running SAP NW for PI in a different client
    At this point, based on being at PI 7.11 and SP5, I did the client copy.  from 000 SAP_UCUS to my new 400 client.  Then I did 001 SAP_USER to my new 400 client.
    Then I followed the steps to link the java UME from 001 to 400.  No problem after restarted SAP, it goes to 400.
    Now, the next step as I see it is to run the initial config wizard out of NWA.  I did that, no errors.
    My problem is when I get to updating the SLD.  I started at cimsap 1.5.42 and CRDelta 5.0....
    I updated cimsap to the cimsap51509_1-20005942.zip which took me to 1.6.9
    Next, I tried to import CRDelta51509_1-20005942.ZIP.  I "browse" to find it during the import, but when I click the "IMPORT" button, my browser hangs...
    I don't even get to the next page where it would be one more "warning/info" before I could really start the import.
    I didn't find anything in the work directory or the cluster/server0/log directory.
    I search all through SDN/OSS but could not find anyone who had this problem.
    Where did I mess up?  Are there other config wizards I should have run before I tried to update the SLD? 
    --NICK

    Hey Caio,
    Thanks for the response but it doesn't actually answer my question.  But to that point, for a "basic" PI post install, which of the NWA config tasks would you run other than the "initial config" ?  And would you run them BEFORE you updated the SLD content (cimsap/CRDelta) ?
    NW: PI - AS ABAP (Basic Configuration for Idoc, Proxy): Maintain
    PI Adapter Engine in JPR Mode
    PI Demo Client
    PI Full Qualified Host Name
    PI Self Test for NetWeaver
    PI SLD Self Registration
    Specifically, I did the SAPINST - ABAP/JAVA patches - Client copy - and THEN the initial config wizard (Setup a new local SLD, ).  Also, during the initial config, I clicked the box marked "This SLD will be used as a name server for development" and my PI server hostname was already in the box  marked "object server name".  This config took about 30 minutes.  I didn't see any errors or warnings.  although I didn't view the log.  I did go into Java JEE services and Filter for Services with name "XPI".  All were green.
    THEN I tried to update the SLD content.
    any thoughts appreciated.
    NICK

  • Deployable cannot be retrieved from FILE_PROVIDER , stopping. Cause:com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Name or password is incorrect

    Hi All,
    After two years of CTS+ working without issue, in the last fortnight JCO_ERROR_LOGON_FAILURE has occurred. I have reviewed all the configuration  in document http://scn.sap.com/doc/DOC-30177, and it all looks fine. The user configured also checks out fine as well. The user id that is causing all the trouble is CTS_<SID>. We chose this option so we could determine which user in case of future issues. We have two development paths, Project and BAU. So at anyone time transports that have started in the BAU development system will need to be imported into the Project development system (using transport express) and vice versa.  Attached is the security authentication log from the system showing authentication failure. I have also checked the transport routes defined for the business systems in the SLD and these look fine as well. Roles assigned to the user are SAP_CTS_PLUS,
    SAP_J2EE_ADMIN, SAP_XI_CMS_SERV_USER, SAP_XI_CONFIGURATOR, SAP_XI_DEVELOPER, Z_CTS_PLUS_ADDITIONAL. I have also checked the permissions on the file at the operating system level.
    Any suggestions/advice gratefully received as this really has me scratching my head.
    Log:
    !REPOSITORY_ERROR_CHECK_STACKTRACE!
    [EXCEPTION]
    com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Name or password is incorrect (repeat logon) on DXI mshost strsap31
    at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:662)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1364)
    at com.sap.conn.jco.rt.ClientConnection.connect(ClientConnection.java:731)
    at com.sap.conn.jco.rt.PoolingFactory.init(PoolingFactory.java:103)
    at com.sap.conn.jco.rt.ConnectionManager.createFactory(ConnectionManager.java:293)
    at com.sap.conn.jco.rt.DefaultConnectionManager.createFactory(DefaultConnectionManager.java:46)
    at com.sap.conn.jco.rt.ConnectionManager.getFactory(ConnectionManager.java:262)
    at com.sap.conn.jco.rt.RfcDestination.initialize(RfcDestination.java:509)
    at com.sap.conn.jco.rt.RfcDestination.getSystemID(RfcDestination.java:533)
    at com.sap.conn.jco.rt.RepositoryManager.getRepository(RepositoryManager.java:30)
    at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:603)
    at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:27)
    at com.sap.cts.jco.tms.TmsJCoAdapter.initializeJCo(TmsJCoAdapter.java:76)
    at com.sap.cts.jco.tms.TmsJCoAdapter.<init>(TmsJCoAdapter.java:57)
    at com.sap.cts.jco.EpsFileReader.<init>(EpsFileReader.java:76)
    at com.sap.cts.jco.EpsFileReaderController.doImport(EpsFileReaderController.java:90)
    at com.sap.cts.core.ImportManager.execImport(ImportManager.java:102)
    at com.sap.cts.ejb.DeployBean.execImport(DeployBean.java:170)
    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:597)
    at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:47)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
    at com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:204)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:710)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:662)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:322)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:199)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:65)
    at com.sap.engine.services.webservices.servlet.SoapServlet.doPost(SoapServlet.java:61)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: RfcException: [null]
      message: Name or password is incorrect (repeat logon) on DXI mshost strsap31
      Return code: RFC_SYS_EXCEPTION(3)
      error group: 103
      key: RFC_ERROR_LOGON_FAILURE
    at com.sap.conn.rfc.api.RfcApi.RfcOpen(RfcApi.java:219)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1331)
    ... 87 more
    Caused by: RfcException: [DXI|strsap31]
      message: Name or password is incorrect (repeat logon)
      Return code: RFC_SYS_EXCEPTION(3)
      error group: 104
      key: RFC_ERROR_SYSTEM_FAILURE
    Exception raised by DXI|strsap31
    at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcReceive(RfcIoOpenCntl.java:2034)
    at com.sap.conn.rfc.api.RfcApi.RfcOpen(RfcApi.java:187)
    ... 88 more
    Caused by: com.sap.conn.rfc.exceptions.RfcGetException: Name or password is incorrect (repeat logon)
    at com.sap.conn.rfc.engine.RfcImp.ab_rfcerror(RfcImp.java:1157)
    at com.sap.conn.rfc.engine.RfcGet.rfcget_run(RfcGet.java:131)
    at com.sap.conn.rfc.engine.RfcGet.ab_rfcget(RfcGet.java:23)
    at com.sap.conn.rfc.engine.RfcRcv.ab_rfcreceive(RfcRcv.java:33)
    at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcReceive(RfcIoOpenCntl.java:1981)
    ... 89 more

    User id missing in client 000

  • ERROR IN WAS 6.4 SNEAK PREVIEW INSTALL DURING SP3 - SP5 DEPLOY ONLINE STAG

    Hi All,
    I have installed WAS 6.4 SP3 sneak preview over SQL server 2000. I get the following error message while patching from WAS SP3 to SP5 ( this patch is included as part of the sneak preview zip package) during DEPLOY ONLINE stage.
    ERROR
    MUT-02041   SDM call of deploySdaList ends with returncode 4. See output of logfile D:\Program Files\sapinst_instdir\PATCH\MSS\callSdmViaSapinst.log.
    Also find below the log file :
    Aug 23, 2004 4:09:51 PM  Info: Start logging to console
    Aug 23, 2004 4:09:51 PM  Info:
    Aug 23, 2004 4:09:51 PM  Info: ============================================
    Aug 23, 2004 4:09:51 PM  Info: =   Starting to execute command 'deploy'   =
    Aug 23, 2004 4:09:51 PM  Info: ============================================
    Aug 23, 2004 4:09:51 PM  Info: Starting SDM - Software Deployment Manager...
    Aug 23, 2004 4:09:53 PM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.3005.00.0000.20040414093518.0000
    Aug 23, 2004 4:09:55 PM  Info: SDM operation mode successfully set to: Standalone
    Aug 23, 2004 4:09:57 PM  Info: Initializing Network Manager (50017)
    Aug 23, 2004 4:09:59 PM  Info: Checking if another SDM is running on port 50018
    Aug 23, 2004 4:09:59 PM  Info: -
    Starting deployment -
    Aug 23, 2004 4:09:59 PM  Info: Loading selected archives...
    Aug 23, 2004 4:09:59 PM  Info: Loading archive 'C:\WebAS640_Java_SP5\WebAS640SP3toSP5_Patch\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS05_0.SCA'
    Aug 23, 2004 4:12:27 PM  Info: Selected archives successfully loaded.
    Aug 23, 2004 4:12:33 PM  Info: Actions per selected component:
    Aug 23, 2004 4:12:33 PM  Info: Update: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
    Aug 23, 2004 4:12:33 PM  Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040330113610.0000' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031112163623.0000'.
    Aug 23, 2004 4:12:33 PM  Info: No action: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' will not update currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000'.
    Aug 23, 2004 4:12:33 PM  Info: No action: Selected development component 'tc/SL/UTIL_JDD'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000' will not update currently deployed development component 'tc/SL/UTIL_JDD'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000'.
    Aug 23, 2004 4:12:33 PM  Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040309120341.0000' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031119160521.0000'.
    Aug 23, 2004 4:12:33 PM  Info: Initial deployment: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' will be deployed.
    Aug 23, 2004 4:12:33 PM  Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031223155421.0000'.
    Aug 23, 2004 4:12:33 PM  Info: Update: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
    Aug 23, 2004 4:12:33 PM  Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170150.0000' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007124738.0000'.
    Aug 23, 2004 4:12:33 PM  Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031210162516.0000'.
    Aug 23, 2004 4:12:33 PM  Info: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215150458.0000'.
    Aug 23, 2004 4:12:33 PM  Info: Update: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' updates currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031223155421.0000'.
    Aug 23, 2004 4:12:33 PM  Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031223155421.0000'.
    Aug 23, 2004 4:12:33 PM  Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031103173534.0000'.
    Aug 23, 2004 4:12:33 PM  Info: Update: Selected development component 'tc/SL/UTIL'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000' updates currently deployed development component 'tc/SL/UTIL'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031015103253.0000'.
    Aug 23, 2004 4:12:33 PM  Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165832.0000' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133611.0000'.
    Aug 23, 2004 4:12:33 PM  Info: No action: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' will not update currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000'.
    Aug 23, 2004 4:12:35 PM  Info: No action: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000' will not update currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000'.
    Aug 23, 2004 4:12:36 PM  Info: Initial deployment: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' will be deployed.
    Aug 23, 2004 4:12:36 PM  Info: No action: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' will not update currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000'.
    Aug 23, 2004 4:12:36 PM  Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031001180520.0000'.
    Aug 23, 2004 4:12:36 PM  Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031020134252.0000'.
    Aug 23, 2004 4:12:36 PM  Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040415171020.0000' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031125134518.0000'.
    Aug 23, 2004 4:12:37 PM  Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007125447.0000'.
    Aug 23, 2004 4:12:37 PM  Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031210162516.0000'.
    Aug 23, 2004 4:12:37 PM  Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000'.
    Aug 23, 2004 4:12:37 PM  Info: Initial deployment: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will be deployed.
    Aug 23, 2004 4:12:37 PM  Info: Update: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
    Aug 23, 2004 4:12:37 PM  Info: No action: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
    Aug 23, 2004 4:12:37 PM  Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007124656.0000'.
    Aug 23, 2004 4:12:37 PM  Info: Update: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
    Aug 23, 2004 4:12:37 PM  Info: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.30.5.0.20040420063500' updates currently deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'3.20040113043717'.
    Aug 23, 2004 4:12:37 PM  Info: Update: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' updates currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040108174709.0000'.
    Aug 23, 2004 4:12:38 PM  Info: Update: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' updates currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040108174709.0000'.
    Aug 23, 2004 4:12:38 PM  Info: No action: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
    Aug 23, 2004 4:12:38 PM  Info: Update: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000' updates currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031001180520.0000'.
    Aug 23, 2004 4:12:38 PM  Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031119155233.0000'.
    Aug 23, 2004 4:12:38 PM  Info: Initial deployment: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' will be deployed.
    Aug 23, 2004 4:12:38 PM  Info: Update: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164151.0000' updates currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007124708.0000'.
    Aug 23, 2004 4:12:38 PM  Info: Update: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164054.0000' updates currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040112231712'.
    Aug 23, 2004 4:12:38 PM  Info: Update: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164228.0000' updates currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031001181052.0000'.
    Aug 23, 2004 4:12:39 PM  Info: Initial deployment: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165855.0000' will be deployed.
    Aug 23, 2004 4:12:39 PM  Info: Update: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
    Aug 23, 2004 4:12:39 PM  Info: Update: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165842.0000' updates currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133723.0000'.
    Aug 23, 2004 4:12:39 PM  Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040415171020.0000' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031125134518.0000'.
    Aug 23, 2004 4:12:39 PM  Info: Update: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163618.0000' updates currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031001180219.0000'.
    Aug 23, 2004 4:12:39 PM  Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031218123529.0000'.
    Aug 23, 2004 4:12:39 PM  Info: Update: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000' updates currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007125447.0000'.
    Aug 23, 2004 4:12:39 PM  Info: Update: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170316.0000' updates currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007124545.0000'.
    Aug 23, 2004 4:12:40 PM  Info: Update: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' updates currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215133140.0000'.
    Aug 23, 2004 4:12:40 PM  Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031020134252.0000'.
    Aug 23, 2004 4:12:40 PM  Info: Update: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155021.0000' updates currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031117101211.0000'.
    Aug 23, 2004 4:12:40 PM  Info: Update: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' updates currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040108174709.0000'.
    Aug 23, 2004 4:12:40 PM  Info: Update: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' updates currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031103173534.0000'.
    Aug 23, 2004 4:12:40 PM  Info: Update: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' updates currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040108174709.0000'.
    Aug 23, 2004 4:12:53 PM  Error: An error occured while storing the cluster instances!
    Aug 23, 2004 4:12:53 PM  Error: JStartup Framework is not able to deliver an information about the cluster control instances!
    Please check the status of the J2EE Engine
    Aug 23, 2004 4:12:53 PM  Error: Received exception when saving current Engine state: JStartup Framework is not able to deliver an information about the cluster control instances!
    Please check the status of the J2EE Engine
    Aug 23, 2004 4:12:53 PM  Info: Error handling strategy: OnErrorStop
    Aug 23, 2004 4:12:53 PM  Info: Update strategy: UpdateLowerVersions
    Aug 23, 2004 4:12:53 PM  Info: Starting: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215150458.0000'.
    Aug 23, 2004 4:12:53 PM  Info: SDA to be deployed: D:\usr\sap\P64\JC00\SDM\root\origin\sap.com\SQLTrace\SAP AG\6.3005.00.0000.20040401154008.0000\SQLTrace.ear
    Aug 23, 2004 4:12:53 PM  Info: Software type of SDA: J2EE
    Aug 23, 2004 4:12:59 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Aug 23, 2004 4:13:00 PM  Info: Starting cluster instance processes.
    <b><b>Aug 23, 2004 4:13:00 PM  Error: An error occured while starting a cluster instance!
    Aug 23, 2004 4:13:00 PM  Error: JStartup Framework is not able to deliver an information about the cluster control instances!</b></b>
    Please check the status of the J2EE Engine
    Aug 23, 2004 4:13:00 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Aug 23, 2004 4:13:00 PM  Error: Aborted: development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000':
    SDM could not start the J2EE cluster on the host aol! The online deployment is terminated.
    JStartup Framework is not able to deliver an information about the cluster control instances!
    Please check the status of the J2EE Engine
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
    Aug 23, 2004 4:13:01 PM  Error: An error occured while restoring the cluster instances states
    Aug 23, 2004 4:13:01 PM  Error: JStartup Framework is not able to deliver an information about the cluster control instances!
    Please check the status of the J2EE Engine
    Aug 23, 2004 4:13:01 PM  Error: Received exception when restoring Engine state: JStartup Framework is not able to deliver an information about the cluster control instances!
    Please check the status of the J2EE Engine
    Aug 23, 2004 4:13:01 PM  Info: -
    Deployment was successful -
    Aug 23, 2004 4:13:02 PM  Info: Summarizing the deployment results:
    Aug 23, 2004 4:13:02 PM  Error: Admitted: C:\WebAS640_Java_SP5\WebAS640SP3toSP5_Patch\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS05_0.SCA
    Aug 23, 2004 4:13:02 PM  Error: Processing error. Return code: 4
    Appreciate your prompt help.
    Thanks.
    Nirmal

    Hi,
    I am getting the folloing error message now : below is the log file :
    Aug 24, 2004 2:36:53 PM  Info: Start logging to console
    Aug 24, 2004 2:36:53 PM  Info:
    Aug 24, 2004 2:36:53 PM  Info: ============================================
    Aug 24, 2004 2:36:53 PM  Info: =   Starting to execute command 'deploy'   =
    Aug 24, 2004 2:36:53 PM  Info: ============================================
    Aug 24, 2004 2:36:53 PM  Info: Starting SDM - Software Deployment Manager...
    Aug 24, 2004 2:36:54 PM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.3005.00.0000.20040414093518.0000
    Aug 24, 2004 2:36:56 PM  Info: SDM operation mode successfully set to: Standalone
    Aug 24, 2004 2:36:57 PM  Info: Initializing Network Manager (50017)
    Aug 24, 2004 2:36:57 PM  Info: Checking if another SDM is running on port 50018
    Aug 24, 2004 2:36:57 PM  Info: -
    Starting deployment -
    Aug 24, 2004 2:36:58 PM  Info: Loading selected archives...
    Aug 24, 2004 2:36:58 PM  Info: Loading archive 'C:\WebAS640_Java_SP5\WebAS640SP3toSP5_Patch\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS05_0.SCA'
    Aug 24, 2004 2:37:17 PM  Info: Selected archives successfully loaded.
    Aug 24, 2004 2:37:22 PM  Info: Actions per selected component:
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040330113610.0000' will not update currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040330113610.0000'.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' will not update currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000'.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'tc/SL/UTIL_JDD'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000' will not update currently deployed development component 'tc/SL/UTIL_JDD'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000'.
    Aug 24, 2004 2:37:22 PM  Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040309120341.0000' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031119160521.0000'.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
    Aug 24, 2004 2:37:22 PM  Info: Initial deployment: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' will be deployed.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170150.0000' will not update currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170150.0000'.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000' will not update currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000'.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000' will not update currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000'.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' will not update currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000'.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'tc/SL/UTIL'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000' will not update currently deployed development component 'tc/SL/UTIL'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165554.0000'.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165832.0000' will not update currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165832.0000'.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' will not update currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000'.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000' will not update currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000'.
    Aug 24, 2004 2:37:22 PM  Info: Initial deployment: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' will be deployed.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' will not update currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000'.
    Aug 24, 2004 2:37:22 PM  Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031020134252.0000'.
    Aug 24, 2004 2:37:22 PM  Info: No action: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000' will not update currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000'.
    Aug 24, 2004 2:37:22 PM  Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040415171020.0000' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031125134518.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000' will not update currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000' will not update currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040413165121.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040401154008.0000'.
    Aug 24, 2004 2:37:23 PM  Info: Initial deployment: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will be deployed.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000' will not update currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322174245.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
    Aug 24, 2004 2:37:23 PM  Info: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.30.5.0.20040420063500' updates currently deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'3.20040113043717'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will not update currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000' will not update currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322164348.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will not update currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000' will not update currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164312.0000'.
    Aug 24, 2004 2:37:23 PM  Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155127.0000' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031119155233.0000'.
    Aug 24, 2004 2:37:23 PM  Info: Initial deployment: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' will be deployed.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164151.0000' will not update currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164151.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164054.0000' will not update currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164054.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164228.0000' will not update currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164228.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165855.0000' will not update currently deployed development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165855.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165842.0000' will not update currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165842.0000'.
    Aug 24, 2004 2:37:23 PM  Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040415171020.0000' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031125134518.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163618.0000' will not update currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163618.0000'.
    Aug 24, 2004 2:37:23 PM  Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326165540.0000' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031218123529.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000' will not update currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308164521.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000' will not update currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163841.0000'.
    Aug 24, 2004 2:37:23 PM  Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040326170320.0000' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031020134252.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170316.0000' will not update currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322170316.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155021.0000' will not update currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040322155021.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will not update currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will not update currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000'.
    Aug 24, 2004 2:37:23 PM  Info: No action: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000' will not update currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040308163632.0000'.
    <b>Aug 24, 2004 2:37:23 PM  Error: Could not create JStartupClusterController: No route to host: connect Throwable: java.net.NoRouteToHostException Throwable message: No route to host: connect
    Aug 24, 2004 2:37:23 PM  Error: Received exception when saving current Engine state: Could not create JStartupClusterController: No route to host: connect
    Aug 24, 2004 2:37:24 PM  Info: Error handling strategy: OnErrorStop</b>Aug 24, 2004 2:37:24 PM  Info: Update strategy: UpdateLowerVersions
    Aug 24, 2004 2:37:24 PM  Info: Starting: Initial deployment: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000' will be deployed.
    Aug 24, 2004 2:37:24 PM  Info: SDA to be deployed: D:\usr\sap\P64\JC00\SDM\root\origin\sap.com\tc\monitoring\systeminfo\SAP AG\6.3005.00.0000.20040419174536.0000\SystemInfo.ear
    Aug 24, 2004 2:37:24 PM  Info: Software type of SDA: J2EE
    Aug 24, 2004 2:37:25 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Aug 24, 2004 2:37:28 PM  Error: Could not create JStartupClusterController: No route to host: connect Throwable: java.net.NoRouteToHostException Throwable message: No route to host: connect
    Aug 24, 2004 2:37:28 PM  Info: No information about the J2EE engine cluster is available.
    The online deployment process is continuing.
    Aug 24, 2004 2:37:30 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Aug 24, 2004 2:37:30 PM  Error: Aborted: development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.3005.00.0000.20040419174536.0000':
    Caught exception while checking the login credentials from SAP J2EE Engine's deploy API:
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [aol] with UserName: [Administrator]
                        Check your Login Info.
                        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)
    Aug 24, 2004 2:37:30 PM  Error: Could not create JStartupClusterController: No route to host: connect Throwable: java.net.NoRouteToHostException Throwable message: No route to host: connect
    Aug 24, 2004 2:37:30 PM  Error: Received exception when restoring Engine state: Could not create JStartupClusterController: No route to host: connect
    Aug 24, 2004 2:37:31 PM  Info: -
    Deployment was successful -
    Aug 24, 2004 2:37:31 PM  Info: Summarizing the deployment results:
    Aug 24, 2004 2:37:31 PM  Error: Admitted: C:\WebAS640_Java_SP5\WebAS640SP3toSP5_Patch\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS05_0.SCA
    Aug 24, 2004 2:37:31 PM  Error: Processing error. Return code: 4

  • RFC_ERROR_SYSTEM_FAILURE: Time limit exceeded. Connection Pool - JCO api

    Hi Everyone
    My Connection  Pool parameters JCO api.
    client=300
    user=SISGERAL_RFC
    passwd=******
    ashost=14.29.3.120
    sysnr=00
    size=10
    I have these parameters on my Connection Pool and sometimes appear these wrongs in my application:
    1.
    2006-01-07 13:20:37,414 ERROR com.tel.webapp.framework.SAPDataSource - ##### Time limit exceeded. LOCALIZED MESSAGE = Time limit exceeded. KEY = RFC_ERROR_SYSTEM_FAILURE GROUP = 104 TOSTRING = com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Time limit exceeded.
    2.
    2006-01-07 14:01:31,007 ERROR com.tel.webapp.framework.SapPoolConnectionManager - Timeout
    I’d like to know if is happening.
    Are there something wrong with my connection pool?
    What can be happening?
    Thanks

    Raghu,
    Thanks for your response.
    Yes, the pool connections are in place according to the sAP note mentioned above.
    Regards,
    Faisal

Maybe you are looking for

  • Creation of material from excel sheet

    Hi All, Can we create material by uploading from excel sheet. I have created all necessary product categories in system. I want to create 20 materials in one product category from excel sheet. Abdul Raheem

  • Issue with size of disk image on an external drive

    I am trying to make a 900GB encrypted disk image on a new (blank) Lacie 1TB external drive. When I try and do so, I am told that there is only space for a 500GB image. When I tried to do the same thing on a Seagate 1TB external drive, I had no proble

  • White screen on restart

    I have a 27" iMac 3.5 GHz Core i7 - 8 GB Ram 1600 MHz DDR3 with a 3 TB Fusion drive.  I downloaded Yosemite with some difficulty this evening.  I ran the install and when it wanted to restart a white screen came up for over 10 minutes.  Should it tak

  • A song I downloaded wont play even though I have authorized it

    I just bought a song off of the itunes library, but when I go to play it it says I need authorization. I authorize it, and it still will not work. What is going on?

  • Concurrent-access logging; best approach

    I have a script that runs on multiple machines at once, and I would like to provide some ongoing single source logging of these activities. As a general rule I think the chance of two machines touching the log at once are slim, but when the script co