SAP connector: java.lang.NullPointerException

Hi,
we are actually using the free of charge version of cps.
Right now we are just running one job there "SAP_CCMS_MONI_BATCH_DP" It worked fine for about 2 weeks. Today I saw that the job is not executed in the SAP System anymore.
The error message is:
An error has occurred in the SAP connector: java.lang.NullPointerException
Details:
java.lang.NullPointerException
at java.lang.Throwable.<init>(Throwable.java:58)
at java.lang.String.regionMatches(String.java:886)
at java.lang.String.startsWith(String.java:981)
at java.lang.String.startsWith(String.java:966)
at com.redwood.scheduler.connector.sap.rfc.command.JobParameterHelper.getParametersStartingWith(JobParameterHelper.java:276)
at com.redwood.scheduler.connector.sap.rfc.command.impl.AbapRunPrintCommand.doAddSteps(AbapRunPrintCommand.java:256)
at com.redwood.scheduler.connector.sap.rfc.command.AbstractXbpJobRunCommand.execute(AbstractXbpJobRunCommand.java:177)
at com.redwood.scheduler.connector.sap.rfc.command.AbstractXbpCommand.doExecute(AbstractXbpCommand.java:123)
at com.redwood.scheduler.connector.sap.rfc.command.AbstractCommand.execute(AbstractCommand.java:56)
at com.redwood.scheduler.connector.sap.rfc.service.SapJobWork.doWork(SapJobWork.java:107)
at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:59)
at java.lang.Thread.run(Thread.java:838)
I have already checked the connection from CPS to the SAP System - everything is ok... I have restarted the process server...
Regards
Johannes

HI Anton,
my college told me right now, that we have patched the SAp System with the latest Kernel:
Kernel Release: 701
Patch Level 75
ABAP LOAD 1565
CUA-Load 32
Mode opt
The Job failed exactly at that time, when the Kernel was patched...
Regards
Johannes

Similar Messages

  • Com.sap.kw java.lang.NullPointerException: FATAL ERROR:

    We are getting a bunch of errors around cop.sap.kw in our J2EE defaultTrace log file.
    Here is an example:
    Apr 1, 2008 7:36:33 PM       com.sap.kw.framework.FrontController [SAPEngine_Application_Thread[impl:3]_56] Path: Caught java.lang.NullPointerException: FATAL ERROR: Could not load E:\usr\sap\QAA\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\tc~kw_tc\servlet_jsp\SAPIKS2\root\WEB-INF\ApplConfig.xml
         at com.sap.kw.framework.XMLConfiguration.<init>(XMLConfiguration.java:53)
         at com.sap.kw.actions.ApplConfig.init(ApplConfig.java:83)
         at com.sap.kw.framework.FrontController.init(FrontController.java:222)
         at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
         at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
         at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
         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)
    Has anyone ran into this before?

    Hi,
    that file you mentioned exists in file system?
    it seems somebody has changed incorrectly something in the file system.
    regards.
    roberti

  • Com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException in sap pi

    Hi all,
    I am working on SAP PI 7.3.1 SP09. Currently we have interfaces which uses 50200 port. I have created a http destination from nwa pointing to https://....url. So all of a sudden all the interfaces went to error state. After debugging i found that the port 50200 is replaced with 50201which is https port. After changing the port to initial value ie., 50200 all interfaces are working fine except the one which were pointing to https url and they are showing the following error description.
    <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SAP:Category>XIAdapterFramework</SAP:Category>  
    <SAP:Code area="MESSAGE">GENERAL</SAP:Code>  
    <SAP:P1 />  
    <SAP:P2 />  
    <SAP:P3 />  
    <SAP:P4 />  
    <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException</SAP:AdditionalText>  
    <SAP:Stack />  
    <SAP:Retry>M</SAP:Retry>  
    </SAP:Error>
    The entire trace is as follows:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Inbound Message
    --> 
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"> 
    <Trace level="1" type="T">Party normalization: sender</Trace>  
    <Trace level="3" type="T">Sender scheme external =</Trace>  
    <Trace level="3" type="T">Sender agency external =</Trace>  
    <Trace level="3" type="T">Sender party external =</Trace>  
    <Trace level="3" type="T">Sender party normalized =</Trace>  
    <Trace level="1" type="T">Determining the sender agreement</Trace>  
    <Trace level="3" type="T">##### DG: 3</Trace>  
    <Trace level="3" type="T">##### TO: 3</Trace>  
    <Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>  
    <Trace level="2" type="T">Request Line = POST /sap/xi/engine/?type=entry HTTP/1.0</Trace>  
    <Trace level="2" type="T">Host = 10.66.14.150:50200</Trace>  
    <Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>  
    <Trace level="1" type="T">Remote address = 10.66.10.160</Trace>  
    <Trace level="1" type="T">User = SFUSER</Trace>  
    <Trace level="1" type="T">Process ID: 760</Trace>  
    <Trace level="1" type="T">Work Process ID: 10</Trace>  
    <Trace level="1" type="T">Message ID = 53BEFE7146893BD5E10000000A420AA0</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"> 
    <Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>  
    <Trace level="3" type="T">##### DG: 3</Trace>  
    <Trace level="3" type="T">##### TO: 3</Trace>  
    <Trace level="1" type="T">Hop engine name = is.02.devpipd1</Trace>  
    <Trace level="1" type="T">Hop engine type = IS</Trace>  
    <Trace level="1" type="T">Hop adapter name = XI</Trace>  
    <Trace level="1" type="T">Hop adapter namespace = http://sap.com/xi/XI/System</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV"> 
    <Trace level="3" type="T">No triggers found. OK.</Trace>  
    </Trace>
    <Trace level="3" type="T">system-ID = PD1</Trace>  
    <Trace level="3" type="T">client = 001</Trace>  
    <Trace level="3" type="T">language = E</Trace>  
    <Trace level="3" type="T">user = SFUSER</Trace>  
    <Trace level="1" type="Timestamp">2014-07-10T08:56:37Z INDIA</Trace>  
    <Trace level="1" type="T">ACL Check is performed</Trace>  
    <Trace level="1" type="T">XML validation is executed</Trace>  
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />  
    - <!-- ************************************
    -->   
    <Trace level="1" type="T">PLNAME = CENTRAL</Trace>  
    <Trace level="1" type="T">QOS = BE</Trace>  
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />  
    - <!-- ************************************
    -->   
    <Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>  
    <Trace level="3" type="T">Pipeline-Elements for pipeline SAP_CENTRAL</Trace>  
    <Trace level="3" type="T">0001 PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    <Trace level="3" type="T">0002 PLSRV_RECEIVER_DETERMINATION</Trace>  
    <Trace level="3" type="T">0003 PLSRV_INTERFACE_DETERMINATION</Trace>  
    <Trace level="3" type="T">0004 PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>  
    <Trace level="3" type="T">0005 PLSRV_MAPPING_REQUEST</Trace>  
    <Trace level="3" type="T">0006 PLSRV_OUTBOUND_BINDING</Trace>  
    <Trace level="3" type="T">0007 PLSRV_VIRUS_SCAN_RQ_OUT</Trace>  
    <Trace level="3" type="T">0008 PLSRV_XML_VALIDATION_RQ_OUT</Trace>  
    <Trace level="3" type="T">0009 PLSRV_CALL_ADAPTER</Trace>  
    <Trace level="3" type="T">0010 PLSRV_VIRUS_SCAN_RS_INB</Trace>  
    <Trace level="3" type="T">0011 PLSRV_XML_VALIDATION_RS_INB</Trace>  
    <Trace level="3" type="T">0012 PLSRV_MAPPING_RESPONSE</Trace>  
    <Trace level="3" type="T">0013 PLSRV_VIRUS_SCAN_RS_OUT</Trace>  
    <Trace level="3" type="T">0014 PLSRV_XML_VALIDATION_RS_OUT</Trace>  
    <Trace level="3" type="T">system-ID = PD1</Trace>  
    <Trace level="3" type="T">client = 001</Trace>  
    <Trace level="3" type="T">language = E</Trace>  
    <Trace level="3" type="T">user = SFUSER</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST"> 
    <Trace level="2" type="T">Persisting original message</Trace>  
    <Trace level="3" type="T">Message-Version = 000</Trace>  
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>  
    </Trace>
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Begin of pipeline processing PLSRVID = CENTRAL</Trace>  
    - <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB"> 
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"> 
    <Trace level="3" type="T">Calling pipeline service: PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>  
    <Trace level="3" type="T">PLSRVTYPE =</Trace>  
    <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>  
    <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_VALIDATION</Trace>  
    <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>  
    <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>  
    <Trace level="3" type="T" />  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"> 
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV"> 
    <Trace level="3" type="T">Pipeline Service = PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    <Trace level="3" type="T">Skip Inbound Validation =</Trace>  
    <Trace level="3" type="T">Skip Outbound Validation =</Trace>  
    <Trace level="3" type="T">Area = XML_VALIDATION_INB</Trace>  
    <Trace level="1" type="T">Reading sender agreement</Trace>  
    <Trace level="1" type="T">Message does not contain a sender agreement</Trace>  
    <Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>  
    </Trace>
    </Trace>
    </Trace>
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA End of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST"> 
    <Trace level="3" type="T">Persisting message after plsrv call</Trace>  
    <Trace level="3" type="T">Message-Version = 001</Trace>  
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>  
    </Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION"> 
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"> 
    <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>  
    <Trace level="3" type="T

    HI,
    Thank you for your hint. Maybe I just forgot to mention one important fact. We have second SAP Netweaver PI 7.1 which is completely our system. The first one I mentioned in first message is the customer's one. The one we have extra is also connected to MAXIMO and GIS. Settings of this interface is completely same among one thing:
    Patch level of XIAF:
    1. customers SAP PI level is
    Adapter Common Library Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:29:47+0000)
    Adapter Application Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:30:00+0000)
    2. our SAP PI level is
    Adapter Common Library Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:21+0000)
    Adapter Application Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:31+0000)
    Both of them has Axis Version: Apache Axis version: 1.4 Built on Apr 22, 2006 (06:55:48 PDT)
    Also important to mention is fact that same problem happened in our SAP PI, but we implemented last patch of XIAF and it has suddenly started to work. I have suspicion it is somehow connected to this patch. Btw. this patch contains a lot of notes regarding  AXIS framework (i.e. 1435998, 1150375, 1048268), so obviously some bugs of the AXIS adapter has been resolved by this patch.
    What do you think ?
    Thanks

  • Runtime error.Java.lang.nullPointerException: null at com.sap.guid.GUID.par

    Hi experts.
    My scenario is File --> PI --> File.
    During the message mapping there are a few RFC lockups.
    I have configured an communication component for the RFC destination, and a Receiver communication channel to the RFC system.
    When I am trying to check the message mapping and the operation mapping from the integration builder every thing works just fine.
    In the interface determination i have configured the rfc parameter for the mapping.
    When I am trying to run the hole process i receive an error saying:"Runtime exception from: java.lang.nullPointerException:
    null at com.sap.guid.GUID.parsHEXguid(guid.java:1015)
    reguars Max

    Did you test your operation mapping??
    Did you provide your RFC communication channel name and import parameters value in paramter tab of Operation mappi
    Yes I did.
    I have tested the operation mapping and it runs just fine.
    Also all the parameters are specified.
    And the communication channel is configured.
    Just to make sure the communication channel is configured well.
    Should it be configured as RFC adepter and connected to the system on which the RFCs are located?
    If this is all of the configuration needed i have already done them.
    Any suggestions?
    Regards Max.

  • Java.lang.NullPointerException   at com.sap.caf.eu.gp.ui.inst.CInstantiation.getProcessTemplate(CInstantiation.java:732)

    Hi I am getting the following error on link related to Guided procedure step only for few people not for every one. Once  i delete the browser cookies are cache it is working fine. Please  let me know , if any one could had same issue or if any one know the reason, it is completely showing related to Standard GP service related exception. Also this errors are not coming all the time consistently, it is happening randomly. but when u get the error if you delete the cookies from browser and log off and login again from portal it is working fine.
    Path to object does not exist at com.sap.nw.eu.gp, the whole lookup name is sap.com/com.sap.nw.eu.gp/GPService.
    com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at com.sap.nw.eu.gp, the whole lookup name is sap.com/com.sap.nw.eu.gp/GPService.
    at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:278)
    at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:627)
    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
    at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
    at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at com.sap.caf.eu.gp.ui.inst.CInstantiation.wdDoInit(CInstantiation.java:161)
    at com.sap.caf.eu.gp.ui.inst.wdp.InternalCInstantiation.wdDoInit(InternalCInstantiation.java:148)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:864)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
    at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1362)
    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
    at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
    at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) 
    Exception occured during processing of Web Dynpro application sap.com/caf~eu~gp~ui~inst/AInstantiation. The causing exception is nested.
    [EXCEPTION]
    java.lang.NullPointerException
    at com.sap.caf.eu.gp.ui.inst.CInstantiation.getProcessTemplate(CInstantiation.java:732)
    at com.sap.caf.eu.gp.ui.inst.wdp.InternalCInstantiation.getProcessTemplate(InternalCInstantiation.java:203)
    at com.sap.caf.eu.gp.ui.inst.VInstantiation.dispatch(VInstantiation.java:182)
    at com.sap.caf.eu.gp.ui.inst.VInstantiation.onEventShowInstantiationView(VInstantiation.java:564)
    at com.sap.caf.eu.gp.ui.inst.wdp.InternalVInstantiation.wdInvokeEventHandler(InternalVInstantiation.java:291)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
    at com.sap.tc.webdynpro.progmodel.controller.Component.fireEvent(Component.java:285)
    at com.sap.caf.eu.gp.ui.inst.wdp.InternalCInstantiationInterface.wdFireEventShowInstantiationView(InternalCInstantiationInterface.java:174)
    at com.sap.caf.eu.gp.ui.inst.CInstantiationInterface.setTemplateId(CInstantiationInterface.java:116)
    at com.sap.caf.eu.gp.ui.inst.wdp.InternalCInstantiationInterface.setTemplateId(InternalCInstantiationInterface.java:129)
    at com.sap.caf.eu.gp.ui.inst.WInstantiationInterfaceView.onPlugDefault(WInstantiationInterfaceView.java:83)
    at com.sap.caf.eu.gp.ui.inst.wdp.InternalWInstantiationInterfaceView.wdInvokeEventHandler(InternalWInstantiationInterfaceView.java:105)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingInterfaceView.invokeEventHandler(DelegatingInterfaceView.java:85)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:162)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:375)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:864)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
    at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1362)
    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
    at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
    at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

    Govardan,
    Thanks for the reply. We don't have any custom code related to GP or CAF. We created the GP Process and in the process, we attached the PCD objects to the callable object to call.
    In the entire error trace it is referring only sap standard classes only. Also we haven't done any customization Except GP Process creation as i mentioned above.
    com.sap.caf.eu.gp.ui.inst.CInstantiation.getProcessTemplate(CInstantiation.java:732),
    if you look at my initial report , there are two exceptions i have mentioned. before coming the above error i have observed the following error in the log file, First it is logging the following error and then next showing the above error. Looks like GPService is not able to lookup .
    Path to object does not exist at com.sap.nw.eu.gp, the whole lookup name is  sap.com/com.sap.nw.eu.gp/GPService.
    com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at com.sap.nw.eu.gp, the whole lookup name is sap.com/com.sap.nw.eu.gp/GPService.
    at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:278)
    at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:627)
    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
    at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
    at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at com.sap.caf.eu.gp.ui.inst.CInstantiation.wdDoInit(CInstantiation.java:161)
    at com.sap.caf.eu.gp.ui.inst.wdp.InternalCInstantiation.wdDoInit(InternalCInstantiation.java:148)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:864)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
    at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1362)
    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
    at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
    at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) 
    Thanks

  • RFC Import from own SAP XI results in java.lang.NullPointerException

    Hi All,
    I'm trying to do an import of a local RFC (developed in SAP XI) but this results in a java.lang.NullPointerException
    RFC import from other SAP system is no problem.
    Anyone an idea?
    Cheers,
    Frank

    Hi,
    But we are using custom RFCs from SAP XI only. We are using XI3.0 SP11.
    Could you pls check the following sap notes..
    SAP Notes 677732, 672745, 212011, and 718320.
    Have a look at the following link...
    http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/frameset.htm
    Thanks,
    Sasi

  • SAP ESS Family Member/dependants   java.lang.NullPointerException error

    Hi
    We are have the following problem when trying to edit or add a new child dependent fro Family member dependents.  In the backend it works fine but on ess it dumps.  There is no st22.  we have looked all the notes and the previous sdn thread for this and applied the relevant patches as suggested in the notes.  Have any of you encounter this problem and how did you guys resolve it??
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.xss.per.vc.detailfooter.VcPersInfoDetailFooter.onBeforeOutput(VcPersInfoDetailFooter.java:229)
        at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooter.onBeforeOutput(InternalVcPersInfoDetailFooter.java:188)
        at com.sap.xss.per.vc.detailfooter.VcPersInfoDetailFooterInterface.onBeforeOutput(VcPersInfoDetailFooterInterface.java:144)
        at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooterInterface.onBeforeOutput(InternalVcPersInfoDetailFooterInterface.java:136)
        at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooterInterface$External.onBeforeOutput(InternalVcPersInfoDetailFooterInterface.java:212)
        ... 55 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; InfoPath.3; .NET CLR 1.1.4322)
    Version null
    DOM version null
    Client Type msie7
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0104.20090324111057.0000 (release=NW701_04_REL, buildtime=2009-06-12:08:35:57[UTC], changelist=58858, host=pwdfm106), build date: Mon Dec 07 22:38:32 GMT+02:00 2009
    J2EE Engine 7.01 PatchLevel 97888.
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_30-b04, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: amd64
    Session & Other
    Session Locale en_ZA
    Time of Failure Tue Jun 28 07:52:35 GMT+02:00 2011 (Java Time: 1309240355891)
    Web Dynpro Code Generation Infos
    sap.com/pb
    SapDictionaryGenerationCore 7.0108.20100922154735.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:22:16[UTC], changelist=96611, host=pwdfm319.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0108.20100922154735.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:22:20[UTC], changelist=96611, host=pwdfm319.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0108.20100922154919.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:16:25[UTC], changelist=96647, host=pwdfm319.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0108.20100922160824.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:26:26[UTC], changelist=96858, host=pwdfm319.wdf.sap.corp)
    SapMetamodelCommon 7.0108.20100922155425.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:17:08[UTC], changelist=96742, host=pwdfm319.wdf.sap.corp)
    SapMetamodelCore 7.0108.20100922155425.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:17:05[UTC], changelist=96742, host=pwdfm319.wdf.sap.corp)
    SapMetamodelDictionary 7.0108.20100922154738.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:20:28[UTC], changelist=96612, host=pwdfm319.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0108.20100922160830.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:24:08[UTC], changelist=96859, host=pwdfm319.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0108.20101115095814.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:31:20[UTC], changelist=99321, host=pwdfm319)
    SapWebDynproGenerationCore 7.0108.20100922160824.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:26:29[UTC], changelist=96858, host=pwdfm319.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0108.20101115095814.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:31:20[UTC], changelist=99321, host=pwdfm319)
    sap.com/tcwddispwda
    No information available null
    sap.com/pb_api
    SapDictionaryGenerationCore 7.0108.20100922154735.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:22:16[UTC], changelist=96611, host=pwdfm319.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0108.20100922154735.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:22:20[UTC], changelist=96611, host=pwdfm319.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0108.20100922154919.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:16:25[UTC], changelist=96647, host=pwdfm319.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0108.20100922160824.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:26:26[UTC], changelist=96858, host=pwdfm319.wdf.sap.corp)
    SapMetamodelCommon 7.0108.20100922155425.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:17:08[UTC], changelist=96742, host=pwdfm319.wdf.sap.corp)
    SapMetamodelCore 7.0108.20100922155425.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:17:05[UTC], changelist=96742, host=pwdfm319.wdf.sap.corp)
    SapMetamodelDictionary 7.0108.20100922154738.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:20:28[UTC], changelist=96612, host=pwdfm319.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0108.20100922160830.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:24:08[UTC], changelist=96859, host=pwdfm319.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0108.20101115095814.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:31:20[UTC], changelist=99321, host=pwdfm319)
    SapWebDynproGenerationCore 7.0108.20100922160824.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:26:29[UTC], changelist=96858, host=pwdfm319.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0108.20101115095814.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:31:20[UTC], changelist=99321, host=pwdfm319)
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    java.lang.NullPointerException
         at com.sap.xss.per.vc.detailfooter.VcPersInfoDetailFooter.onBeforeOutput(VcPersInfoDetailFooter.java:229)
         at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooter.onBeforeOutput(InternalVcPersInfoDetailFooter.java:188)
         at com.sap.xss.per.vc.detailfooter.VcPersInfoDetailFooterInterface.onBeforeOutput(VcPersInfoDetailFooterInterface.java:144)
         at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooterInterface.onBeforeOutput(InternalVcPersInfoDetailFooterInterface.java:136)
         at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooterInterface$External.onBeforeOutput(InternalVcPersInfoDetailFooterInterface.java:212)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:603)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:569)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseEvent(FPMComponent.java:938)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseEvent(FPMComponent.java:1101)
         at com.sap.xss.per.vc.overview.VcPersInfoOverview.create(VcPersInfoOverview.java:225)
         at com.sap.xss.per.vc.overview.wdp.InternalVcPersInfoOverview.create(InternalVcPersInfoOverview.java:161)
         at com.sap.xss.per.vc.overview.BizCardsView.onActionNew(BizCardsView.java:164)
         at com.sap.xss.per.vc.overview.wdp.InternalBizCardsView.wdInvokeEventHandler(InternalBizCardsView.java:172)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
         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.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
         at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1363)
         at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:327)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:873)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         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:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

    You need the latest SP for resolving this ie front end version. Please check what version you are on and accordingly you need
    to patch your system
    1. http://service.sap.com/
    2. SAP Support Portal    - > Software Download
    3. Download   > Support packages and patches   > Entry by application
       group
    4. SAP Application components
    5. SAP ERP
    6. SAP ERP ENHANCE PACKAGE
    7. EHP4 FOR SAP ERP 6.0 / NW7.01
    8. Entry by component
    9. SAP XSS (Self Services)
    10.SAP ESS 603 (# OS independent)
    download the below version-
    SAPESS06_8-20002355.SCA SP06 for SAP ESS 603
    Now extract the below file from the downloaded SAP_ESS .sca
    -ess~xx
    Now Logon to SDM,go to deployment tab and open the deployment
    configuration tab -
    choose the radio button
    -Update deployed SDA/SCA that have any version
    -deploy -ess~xx sda  files.
    It  will resolve the issue.
    Edited by: Siddharth Rajora on Jun 28, 2011 5:17 PM

  • Data Federator Connection to R3 - java.lang.NullPointerException

    Hi.
    We are trying to add a SAP R3 DataSource in Data Federator XI 3.0 SP2.
    Test Connection gives us the following message: "The connection was established but there is no table for the given connection parameters", what it seems to be ok according to the SAP doc.
    However, when we try to get a list of the Functions or Infosets in the SAP system, an error comes because of a "java.lang.NullPointerException". Checking the application log we get the following:
    2010/03/30 12:21:27.059|<=|||0|26537104| |||||||||||||||"[LeSelect.Api.LSStatementImpl] - [Execution Thread 4]Executing query: CALL executeConnectorCommand '/TEST//TEST/user_bla/sources/draft/R3SYS', 'GET_FUNCTION_LIST * * 200'"
    2010/03/30 12:21:27.074|>=|E||0|26537104| |||||||||||||||"[LeSelect.Core.n] - [Execution Thread 4]Bad Wrapper Error:
    java.lang.NullPointerException
         at LeSelect.Wrappers.SAPR3.H.F(y:343)
         at LeSelect.Wrappers.SAPR3.H.executeCommand(y:285)
         at LeSelect.Core.B.D.R(y:151)
         at LeSelect.Core.QueryEngine.H.p.G(y:131)
         at LeSelect.Core.QueryEngine.H.p.A(y:105)
         at LeSelect.Core.QueryEngine.B.J.A(y:72)
         at LeSelect.Core.QueryEngine.Executor.y.A(y:227)
         at LeSelect.Core.QueryEngine.m.A(y:284)
         at LeSelect.Api.LSStatementImpl.lsExecuteQuery(y:314)
         at LeSelect.B.E.D.V(y:935)
         at LeSelect.B.E.K.B(y:105)
         at LeSelect.B.E.G$_A.run(y:691)"
    We registered the callback program and did all of the steps indicated for the installation, also checked the possible sources of the error according to OSS Note 1278491.
    Any idea how to solve this? Thanks.

    Hello, we have the similar problem: while connecting from Data Federator to SAP ERP we get the following error - "Wrapper /ZTEST/sources/ZTEST reported an exception which is not a WrapperException: java.lang.NullPointerException: null"
    It's necessary to install "SAP BusinessObjects Data Federator Infoset, SAP Query and ABAP Functions Connector Prototype"
    SAP BusinessObjects Web Intelligence Reporting for SAP ERP
    for connection to SAP ERP.
    Are there any ideas? Thanks

  • Error in deployment:java.lang.NullPointerException:sdu name can not be null

    HI Everyone!
        I try to deploy my web dynpro project to SAP J2EE engine. Configuration about SAP J2EE Engine is OK, but there is an error during the deployment. Here is the deployment trace:
    2007-6-28 14:56:27 /userOut/daView_category (com.sap.ide.eclipse.deployer.DVBaseLog) [Thread[Deploy Thread,6,main]] INFO: deployment trace
    14:56:24.207 [info  #300]  [#4]: Trying to connect to 'secude-vmcn0001:50004' as 'administrator'
    14:56:24.207 [debug #100]  [#4]: Session::getContext.[ B E G I N ].timerId=16
    14:56:25.161 [debug #100]  [#4]: Session::getContext.[ E N D ].timerId=[id:#16, elapsed: 954 ms.]
    14:56:25.161 [info  #300]  [#4]: Connected to 'secude-vmcn0001:50004' as 'administrator'
    14:56:25.161 [debug #100]  [#4]: DeployProcessor::ctor:New deploy processor created.deployerId=4
    14:56:25.161 [info  #300]  [#4]: +++++ Starting  D E P L O Y action +++++
    14:56:25.161 [info  #300]  [#4]: Selected archives for deployment
    14:56:25.161 [info  #300]  [#4]: D:\NetWeaverWorkspace\Workspace\Dashboard\Dashboard.ear
    14:56:25.536 [debug #100]  [#4]: DeployProcessor::deploy:going to generate Session id, deployerId=4
    14:56:25.755 [debug #100]  [#4]: DeployProcessor::deploy:got Session id='14',time:[id:#17, elapsed: 594 ms.], deployerId=4
    14:56:25.974 [info  #300]  [#4]: Upload archives to the server.Remote upload path is 'C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\tcbldeploy_controller\archives\14'
    14:56:25.974 [debug #300]  [#4]: DeployProcessor::uploadItemsToServer:Going to upload 'D:\NetWeaverWorkspace\Workspace\Dashboard\Dashboard.ear' on the server.deployerId=4
    14:56:26.427 [info  #300]  [#4]: File 'D:\NetWeaverWorkspace\Workspace\Dashboard\Dashboard.ear' uploaded successfully as 'C:/SAP/JP1/JC00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/14/Dashboard.ear'. Time:[id:#18, elapsed: 453 ms.]
    14:56:26.427 [info  #300]  [#4]: Archives uploaded.time:[#18: 0.453 sec]
    14:56:26.427 [debug #100]  [#4]: DeployProcessor::deployItems:enter.timerId=19, deployerId=4
    14:56:26.427 [debug #100]  [#4]: DeployProcessor::internalCreateAndInitDeployer:get deployer from server, deployerId=4
    14:56:26.427 [debug #100]  [#4]: DeployProcessor::internalCreateAndInitDeployer:deployer get successfully:[id:#20, elapsed: 0 ms.], deployerId=4
    14:56:26.630 [info  #300]  [#4]: component version handling rule is UpdateAllVersions
    14:56:26.849 [info  #300]  [#4]: Error strategies:
    14:56:26.849 [debug #100]  [#4]: DeployProcessor::internalCreateAndInitDeployer:deployer initialized sucessfully:[id:#20, elapsed: 422 ms.], deployerId=4
    14:56:26.849 [debug #100]  [#4]: DeployProcessor::internalCreateAndInitDeployer:total time:[#20: 0.422 sec], deployerId=4
    14:56:26.849 [info  #300]  [#4]: Starting deployment
    14:56:27.177 [debug #100]  [#4]: DeployProcessor::internalMapSdus:sduMapperVisitor.setCompositeDeploymentItem(null),remoteSdu=name: 'null', vendor: 'null', location: 'LOKAL', version: '0.2007.06.28.14.28.59', software type: 'J2EE', dependencies: '[]'
    14:56:27.177 [debug #300]  [#4]: DeployProcessor::deployItems:finally.Total Time:[#19: 0.75 sec], deployerId=4
    14:56:27.177 [info  #300]  [#4]: +++++ End  D E P L O Y action +++++
    And here is the exception detail:
    2007-6-28 14:56:27 /userOut/daView_category (com.sap.ide.eclipse.deployer.DVBaseLog) [Thread[Deploy Thread,6,main]] ERROR: java.lang.NullPointerException: sdu name can not be null.
         at com.sap.engine.services.dc.api.model.impl.SduImpl.<init>(SduImpl.java:39)
         at com.sap.engine.services.dc.api.model.impl.SdaImpl.<init>(SdaImpl.java:51)
         at com.sap.engine.services.dc.api.model.impl.ModelFactoryImpl.createSda(ModelFactoryImpl.java:43)
         at com.sap.engine.services.dc.api.model.SduMapperVisitor.createSda(SduMapperVisitor.java:52)
         at com.sap.engine.services.dc.api.model.SduMapperVisitor.visit(SduMapperVisitor.java:64)
         at com.sap.engine.services.dc.repo.impl.SdaImpl.accept(SdaImpl.java:136)
         at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.internalMapSdus(DeployProcessorImpl.java:704)
         at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:487)
         at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:155)
         at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:185)
         at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:115)
    It seems that there is something wrong about 'SDU', but i don't know what is it, and i can not find the answer both in sdn.sap.com and here.
    Anyone can help me on this?
    Thanks in Advance,
    MK

    Hi Sumit,
        Thank you for your concern.
    Below is a trace file on my server:
    C:\SAP\JP1\JC00\j2ee\cluster\server0\log\defaultTrace.0.trc
    #1.5 #000C296B3F6A000D0000000200000A3000EF90978C2E8C29#1183013784131#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###The session id 14 is associated with correlator id 67431500000169001. Use this correlator id to filter the trace and log messages.#
    #1.5 #000C296B3F6A000D0000000300000A3000EF90978C2E8C29#1183013784131#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###++++++++++++++ Starting deployment ++++++++++++++#
    #1.5 #000C296B3F6A000D0000000400000A3000EF90978C2E8C29#1183013784131#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Archives specified for deployment are: #
    #1.5 #000C296B3F6A000D0000000500000A3000EF90978C2E8C29#1183013784131#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###C:/SAP/JP1/JC00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/14/Dashboard.ear#
    #1.5 #000C296B3F6A000D0000000600000A3000EF90978C2E8C29#1183013784131#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Start loading archives ...#
    #1.5 #000C296B3F6A000D0000000700000A3000EF90978C2E8C29#1183013784147#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Archives are loaded.#
    #1.5 #000C296B3F6A000D0000000800000A3000EF90978C2E8C29#1183013784147#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Error Handling Action: 'UndeploymentAction', Error Handling Strategy: 'OnErrorStop'.
    Error Handling Action: 'DeploymentAction', Error Handling Strategy: 'OnErrorStop'.
    Error Handling Action: 'PrerequisitesCheckAction', Error Handling Strategy: 'OnErrorStop'.
    Version Handling Rule: 'UpdateAllVersions'.
    Deployment Strategy: 'normal deploy strategy'.
    Life Cycle Deployment Strategy: 'bulk deploy strategy'.
    There are no batch filters specified.#
    #1.5 #000C296B3F6A000D0000000900000A3000EF90978C2E8C29#1183013784194#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###The batch for session id 14 will be executed with normal parallelism strategy.#
    #1.5 #000C296B3F6A000D0000000A00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name sap.com/tcwddispwda doesn't exist, because is stopped or not deployed.#
    #1.5 #000C296B3F6A000D0000000B00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:tcddicddicruntime doesn't exist, because is stopped or not deployed.#
    #1.5 #000C296B3F6A000D0000000C00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:com.sap.aii.util.rb doesn't exist, because is stopped or not deployed.#
    #1.5 #000C296B3F6A000D0000000D00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:com.sap.aii.util.xml doesn't exist, because is stopped or not deployed.#
    #1.5 #000C296B3F6A000D0000000E00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:com.sap.aii.proxy.framework doesn't exist, because is stopped or not deployed.#
    #1.5 #000C296B3F6A000D0000000F00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:tc~cmi doesn't exist, because is stopped or not deployed.#
    #1.5 #000C296B3F6A000D0000001000000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:com.sap.aii.util.misc doesn't exist, because is stopped or not deployed.#
    #1.5 #000C296B3F6A000D0000001100000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:tcddicddicservices doesn't exist, because is stopped or not deployed.#
    #1.5 #000C296B3F6A000D0000001200000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:tcgraphicsigs doesn't exist, because is stopped or not deployed.#
    #1.5 #000C296B3F6A000D0000001300000A3000EF90978C2E8C29#1183013784366#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###JLinEE validation of application local/Dashboard returned result
    WARNINGS:
    References Test: Count of deploy time references (described in META-INF/SAP_MANIFEST.MF) and runtime references (described in META-INF/application-j2ee-engine.xml) does not match., file: Dashboard.ear, column 0, line 0, severity: warning
    References Test: There are no matching deploy time references (described in META-INF/SAP_MANIFEST.MF) for the following runtime references [sap.com/tcwddispwda, sap.com/com.sap.mw.jco, sap.com/tcddicddicruntime, sap.com/com.sap.aii.util.rb, sap.com/com.sap.aii.util.xml, sap.com/webservices_lib, sap.com/com.sap.aii.proxy.framework, sap.com/sapxmltoolkit, sap.com/tccmi, sap.com/com.sap.security.api.sda, sap.com/com.sap.util.monitor.jarm, sap.com/com.sap.aii.util.misc, sap.com/tcddicddicservices, sap.com/com.sap.lcr.api.cimclient, sap.com/tcgraphics~igs, sap.com/sld] (described in the META-INF/application-j2ee-engine.xml)., file: Dashboard.ear, column 0, line 0, severity: warning
    #1.5 #000C296B3F6A000D0000001400000A3000EF90978C2E8C29#1183013784366#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#com.sap.engine.services.deploy#Plain#Exception while validating application local/Dashboard.
    No one of the [] containers, which processed it, returned deployed component names.
    The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, appclient, dbschemacontainer, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
    Possible reasons :
         1.An AS Java service, which is providing a container, is stopped or not deployed.
         2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.###
    #1.5 #000C296B3F6A000D0000001700000A3000EF90978C2E8C29#1183013784366#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#com.sap.engine.services.deploy#Plain#Exception in operation deploy with application local/Dashboard.###
    #1.5 #000C296B3F6A000D0000001B00000A3000EF90978C2E8C29#1183013784397#/System/Server##java.lang.Package#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#java.lang.Package#Java#error.action.filter#com/sap/engine/services/mngt_model/localization.properties#Exception thrown by Action Filter: com.sap.engine.services.mngt_model.spi.ActionFilteringException: com.sap.engine.services.deploy.server.utils.DSRemoteException: Application local/Dashboard is not deployed..Action will not be delivered to domain: connector. Action is: APPLICATION_DEPLOYED#3#com.sap.engine.services.mngt_model.plugins.ApplicationActionFilter@d46ed0#connector#APPLICATION_DEPLOYED#
    #1.5 #000C296B3F6A000D0000001D00000A3000EF90978C2E8C29#1183013784397#/System/Server##java.lang.Package#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#java.lang.Package#Java#error.action.filter#com/sap/engine/services/mngt_model/localization.properties#Exception thrown by Action Filter: com.sap.engine.services.mngt_model.spi.ActionFilteringException: com.sap.engine.services.deploy.server.utils.DSRemoteException: Application local/Dashboard is not deployed..Action will not be delivered to domain: servlet_jsp. Action is: APPLICATION_DEPLOYED#3#com.sap.engine.services.mngt_model.plugins.ApplicationActionFilter@d46ed0#servlet_jsp#APPLICATION_DEPLOYED#
    #1.5 #000C296B3F6A000D0000001F00000A3000EF90978C2E8C29#1183013784397#/System/Server##java.lang.Package#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#java.lang.Package#Java#error.action.filter#com/sap/engine/services/mngt_model/localization.properties#Exception thrown by Action Filter: com.sap.engine.services.mngt_model.spi.ActionFilteringException: com.sap.engine.services.deploy.server.utils.DSRemoteException: Application local/Dashboard is not deployed..Action will not be delivered to domain: appclient. Action is: APPLICATION_DEPLOYED#3#com.sap.engine.services.mngt_model.plugins.ApplicationActionFilter@d46ed0#appclient#APPLICATION_DEPLOYED#
    #1.5 #000C296B3F6A000D0000002100000A3000EF90978C2E8C29#1183013784397#/System/Server##java.lang.Package#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#java.lang.Package#Java#error.action.filter#com/sap/engine/services/mngt_model/localization.properties#Exception thrown by Action Filter: com.sap.engine.services.mngt_model.spi.ActionFilteringException: com.sap.engine.services.deploy.server.utils.DSRemoteException: Application local/Dashboard is not deployed..Action will not be delivered to domain: dbpool. Action is: APPLICATION_DEPLOYED#3#com.sap.engine.services.mngt_model.plugins.ApplicationActionFilter@d46ed0#dbpool#APPLICATION_DEPLOYED#
    #1.5 #000C296B3F6A000D0000002300000A3000EF90978C2E8C29#1183013784397#/System/Server##java.lang.Package#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#java.lang.Package#Java#error.action.filter#com/sap/engine/services/mngt_model/localization.properties#Exception thrown by Action Filter: com.sap.engine.services.mngt_model.spi.ActionFilteringException: com.sap.engine.services.deploy.server.utils.DSRemoteException: Application local/Dashboard is not deployed..Action will not be delivered to domain: jmsconnector. Action is: APPLICATION_DEPLOYED#3#com.sap.engine.services.mngt_model.plugins.ApplicationActionFilter@d46ed0#jmsconnector#APPLICATION_DEPLOYED#
    #1.5 #000C296B3F6A000D0000002500000A3000EF90978C2E8C29#1183013784397#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#com.sap.engine.services.deploy#Plain#Exception while validating application local/Dashboard.
    No one of the [] containers, which processed it, returned deployed component names.
    The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, appclient, dbschemacontainer, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
    Possible reasons :
         1.An AS Java service, which is providing a container, is stopped or not deployed.
         2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.###
    #1.5 #000C296B3F6A000D0000002800000A3000EF90978C2E8C29#1183013784397#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#com.sap.engine.services.tcxblxdeploy_controller#Plain#An error occurred while deploying the deployment item 'local_Dashboard'.###
    #1.5 #000C296B3F6A000D0000002B00000A3000EF90978C2E8C29#1183013784428#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Unlocking the Deploy.#
    #1.5 #000C296B3F6A000D0000002C00000A3000EF90978C2E8C29#1183013784428#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#com.sap.engine.services.tcxblxdeploy_controller#Plain#An error occurred while deploying the deployment item 'local_Dashboard'.; nested exception is:
         java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: local_Dashboard
    sdu file path: C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\tcbldeploy_controller\archives\14\Dashboard.ear
    version status: NEW
    deployment status: Admitted
    description:
              1. Error:
    Error occurred while deploying ear file C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\tcbldeploy_controller\archives\14\Dashboard.ear.
    Reason: Exception while validating application local/Dashboard.
    No one of the [] containers, which processed it, returned deployed component names.
    The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, appclient, dbschemacontainer, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
    Possible reasons :
         1.An AS Java service, which is providing a container, is stopped or not deployed.
         2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
    . Cannot deploy it.; nested exception is:
         java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\tcbldeploy_controller\archives\14\Dashboard.ear.
    Reason: Exception while validating application local/Dashboard.
    No one of the [] containers, which processed it, returned deployed component names.
    The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, appclient, dbschemacontainer, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
    Possible reasons :
         1.An AS Java service, which is providing a container, is stopped or not deployed.
         2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.###
    #1.5 #000C296B3F6A000D0000002F00000A3000EF90978C2E8C29#1183013784428#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Deployment has finished#
    Thanks,
    MK

  • HTTP Status 500 Error java.lang.NullPointerException on BO 4.0 SP2

    Hello,
    we installed BO 4.0 SP2 with Tomcat 6 on Windows Server 2008 R2 64 Bit.
    After installation it is not possible to open the CMC, BI-Launchpad or LCM in a browser. It presents the following error page:
    HTTP Status 500 -
    type Exception report
    message
    description The server encountered an internal error () that prevented it from fulfilling this request.
    exception
    java.lang.NullPointerException
         com.businessobjects.servletbridge.customconfig.Config.<init>(Config.java:37)
         com.businessobjects.servletbridge.customconfig.ConfigReader.getConfig(ConfigReader.java:274)
         com.businessobjects.pinger.TimeoutManagerFilter.getSessionState(TimeoutManagerFilter.java:192)
         com.businessobjects.pinger.TimeoutManagerFilter.doFilter(TimeoutManagerFilter.java:75)
    note The full stack trace of the root cause is available in the Apache Tomcat/6.0.24 logs.
    Apache Tomcat/6.0.24
    This is the error message from Tomcat log:
    28.09.2011 08:56:46 org.apache.catalina.core.StandardWrapperValve invoke
    SCHWERWIEGEND: Servlet.service() for servlet equinoxbridgeservlet threw exception
    java.lang.NullPointerException
         at com.businessobjects.servletbridge.customconfig.Config.<init>(Config.java:37)
         at com.businessobjects.servletbridge.customconfig.ConfigReader.getConfig(ConfigReader.java:274)
         at com.businessobjects.pinger.TimeoutManagerFilter.getSessionState(TimeoutManagerFilter.java:192)
         at com.businessobjects.pinger.TimeoutManagerFilter.doFilter(TimeoutManagerFilter.java:75)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
         at java.lang.Thread.run(Thread.java:619)
    The installation of 'SBOP BI Platform Servers 4.0 SP02 Patch 5' didn't affect this problem, it still has the same error.
    BusinessObjects XI 3.1 is running without problems on that server.
    Any help would be very appreciated!
    Thanks in advance.

    Hello together,
    I could fix this issue without any reinstalling of tomcat. I had the same problem after installtion of Patch 9 of SP2 for BOE 4.0.
    Directly after the installation  I changed the session-timeout parameter in some web.xml's because it was requested by our customer. Because I wanted to have a good documentation of those changes in the web.xml's I created a bigger comment in these files.
    First I got 404 errors after that - to solve this I followed Knowledgebase article [1639813|https://websmp230.sap-ag.de/sap/support/notes/1639813] but first it didn't help.
    So the before mentioned bigger comments seemed to be a problem (or maybe the special characters in there) because after shortening these comments and restarting SIA and Tomcat the 404 error disappeared and suddenly the above described 500 error occured.
    After that I changed the Tomcat's localhost directory to localhost.old during downtime of Tomcat (as recommended by Lukas Kostrab). localhost was newly created but it didn't help either.
    So last but not least I redeployed tomcat following article [1639813|https://websmp230.sap-ag.de/sap/support/notes/1639813] (wdeploy.bat tomcat6 u2013DAPP=BOE deploy) and started Tomcat and SIA again. I decided to wait a little bit longer with trying to start CMC - maybe 15min - and suddenly it worked.
    So in conclusion I would say:
    - check any changes you made in any config-files (like e.g. web.xml) and shorten them or remove special characters
    - stop SIA and Tomcat
    - rename localhost directory (or copy and remove) so it will be recreated at startup of Tomcat
    - if that doesn't help check tomcat config according to article [1639813|https://websmp230.sap-ag.de/sap/support/notes/1639813] and redeploy tomcat as mentioned in that arcitle and be a little bit patient
    Hope this might help some of you.
    Best wishes
    Marie

  • Sender  Mail Adapter - java.lang.NullPointerException in CC monitoring

    hi,
    I configured my Sender Mail Adapter correctly.
    I have the correct POP URL, authentication. I'm not using PayloadSwapBean right now.
    I can't get rid of the exception inside my Channel monitoring.
    exception caught during processing mail message; java.lang.NullPointerException
    does anyone know why?
    I've been told the POP account has emails already.
    I will try to create an outlook account for this POP e-mail account in the mean time to see the e-mails.
    Thank you

    thanks aaron.
    I don't see the folder ./SYS/../j2ee/...
    will it be under another folder?  I don't see a trace log folder either.
    I think the problem might be in the Module tab.
    I tried.
    AF_Modules/PayloadSwapBean
    localejbs/AF_Modules/PayloadSwapBean
    /localejbs/AF_Modules/PayloadSwapBean
    sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean
    localejbs/sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean
    /localejbs/sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean
    they all produce the same error. I wonder if these Beans actually exist.
    I think we might have to reinstall this Mail Adapter altogether.
    Or maybe it's really the connection to the Mail Server. But would it display this kind of message.
    This is what I'm looking at.
    Also, i had to use this URL
    pop://server:995/
    (995 is using SSL and it is the default port).  When I use this, I see the Java Null Pointer Exception a lot less frequently. Weird.

  • Interface Mapping run time error...java.lang.nullpointerException  thrown

    Hi,
    I am trying to create a simple f2f scenairo and when I tested the configuration xi throws this message as :
    Interface Mapping run time error...java.lang.nullpointerException  thrown during application mapping.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
      <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
      <SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
      <SAP:TimeSent>2007-01-09T03:43:49Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Service>CAMEL_BS_01</SAP:Service>
      <SAP:Interface namespace="http://kia.com/fiel2file">Source01_MI</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>Camel_BService_01</SAP:Service>
      <SAP:Interface namespace="http://kia.com/fiel2file">Target01_MI</SAP:Interface>
    - <SAP:Mapping notRequired="M">
      <SAP:ObjectId>j5qiPBwVPU2yonkPwhdt/g==</SAP:ObjectId>
      <SAP:SWCV>tR26oJ7nEdu5oM/vCXwv+g==</SAP:SWCV>
      <SAP:SP>-1</SAP:SP>
      </SAP:Mapping>
      </SAP:Receiver>
      <SAP:Interface namespace="http://kia.com/fiel2file">Source01_MI</SAP:Interface>
      </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_Equipment_MM_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_Equipment_MM_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    - <SAP:Hop timeStamp="2007-01-09T03:43:49Z" wasRead="false">
      <SAP:Engine type="AE">af.pi7.gbdci550</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
      <SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
      <SAP:Info />
      </SAP:Hop>
    - <SAP:Hop timeStamp="2007-01-09T03:43:50Z" wasRead="false">
      <SAP:Engine type="IS">is.03.gbdci550</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
      </SAP:HopList>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Date>20070108</SAP:Date>
      <SAP:Time>224350</SAP:Time>
      <SAP:Host>gbdci550</SAP:Host>
      <SAP:SystemId>PI7</SAP:SystemId>
      <SAP:SystemNr>03</SAP:SystemNr>
      <SAP:OS>AIX</SAP:OS>
      <SAP:DB>DB6</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>014</SAP:ProcStatus>
      <SAP:AdapterStatus>000</SAP:AdapterStatus>
      <SAP:User>PIAFUSER</SAP:User>
      <SAP:TraceLevel>1</SAP:TraceLevel>
      <SAP:LogSeqNbr>002</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
      <SAP:PipelineElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
      <SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
      <SAP:PipelineService>PLSRV_MAPPING_REQUEST</SAP:PipelineService>
      <SAP:QIdInternal>XBTOW0__0001</SAP:QIdInternal>
      <SAP:CommitActor>X</SAP:CommitActor>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID">097C2FFA403445A30F7600CE</SAP:EOReferenceRuntime>
      <SAP:EOReferenceInbound type="TID" />
      <SAP:EOReferenceOutbound type="TID" />
      <SAP:MessageSizePayload>168</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>2608</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>168</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
      <SAP:InterfaceAction>DEL</SAP:InterfaceAction>
      <SAP:RandomNumber>67</SAP:RandomNumber>
      <SAP:AckStatus>000</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      <SAP:Sender_Agreement_GUID>49574D50A74F3F5D902E20831759594C</SAP:Sender_Agreement_GUID>
      <SAP:Serialize_Children>X</SAP:Serialize_Children>
      </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.025474</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.064329</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.067038</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.085552</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.085573</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.472198</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.473649</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.483159</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.483341</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.48668</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.486921</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.49182</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.491835</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.720028</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.721545</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>
    - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:TraceLevel>Information</SAP:TraceLevel>
      <SAP:Logging>Off</SAP:Logging>
      </SAP:Diagnostic>
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">Party normalization: sender</Trace>
      <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
      <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender party normalized =</Trace>
      <Trace level="1" type="T">Party normalization: receiver</Trace>
      <Trace level="1" type="T">Receiver scheme external =</Trace>
      <Trace level="1" type="T">Receiver agency external =</Trace>
      <Trace level="1" type="T">Receiver party external =</Trace>
      <Trace level="1" type="T">Receiver party normalized =</Trace>
      <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = PI7</Trace>
      <Trace level="1" type="T">client = 200</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 9E0AD3009F9311DB8770000D60514DD2</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Queue name : XBTI0008</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0008</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = PI7</Trace>
      <Trace level="1" type="T">client = 200</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTOW0__0001</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Persisting single message for post-split handling</Trace>
      <Trace level="1" type="T" />
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = PI7</Trace>
      <Trace level="1" type="T">client = 200</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
      <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Interface Mapping http://kia.com/fiel2file Equipment_IM_Outbound</Trace>
      <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_Equipment_MM_</Trace>
      <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</Trace>
      <Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_Equipment_MM_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</Trace>
      <Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_Equipment_MM_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</Trace>
      <Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
      </SOAP:Header>
    - <SOAP:Body>
    - <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
    - <SAP:Payload xlink:href="cid:[email protected]">
      <SAP:Name>MainDocument</SAP:Name>
      <SAP:Description />
      <SAP:Type>Application</SAP:Type>
      </SAP:Payload>
      </SAP:Manifest>
      </SOAP:Body>
      </SOAP:Envelope>
    Please I request to give me some hint how to troubleshoot this issue.
    Thanks a lot,
    Srujan

    Hi, i have the same type of error when testing configuration, but it seems that the mapping even doesn't start :
    i'm creating an EBP to XCBL scenario, so it's a RFC->XI->XCBL 3.5
    Here is the Java exception
    Mappage d'interface
    Can someone be helpful for that ?
    Regards
    Laurent
    Message was edited by:
            Laurent Gitton

  • A critical error has occured: java.lang.NullPointerException in bank detail

    Hi all,
            When i maintain data for infotype 0009 in R3, bank details link works fine. But when there is no data maintained in R3 for infotype 9..... instead of option for creating new bank details...im getting the following error...
    java.lang.NullPointerException
         at com.sap.xss.hr.per.nz.bank.fc.FcPerBankNz.readRecord(FcPerBankNz.java:276)
         at com.sap.xss.hr.per.nz.bank.fc.wdp.InternalFcPerBankNz.readRecord(InternalFcPerBankNz.java:631)
         at com.sap.xss.hr.per.nz.bank.fc.FcPerBankNzInterface.readRecord(FcPerBankNzInterface.java:146)
         at com.sap.xss.hr.per.nz.bank.fc.wdp.InternalFcPerBankNzInterface.readRecord(InternalFcPerBankNzInterface.java:219)
         at com.sap.xss.hr.per.nz.bank.fc.wdp.InternalFcPerBankNzInterface$External.readRecord(InternalFcPerBankNzInterface.java:295)
         at com.sap.xss.hr.per.nz.bank.overview.VcPerBankNzOverview.onBeforeOutput(VcPerBankNzOverview.java:257)
         at com.sap.xss.hr.per.nz.bank.overview.wdp.InternalVcPerBankNzOverview.onBeforeOutput(InternalVcPerBankNzOverview.java:265)
         at com.sap.xss.hr.per.nz.bank.overview.VcPerBankNzOverviewInterface.onBeforeOutput(VcPerBankNzOverviewInterface.java:134)
         at com.sap.xss.hr.per.nz.bank.overview.wdp.InternalVcPerBankNzOverviewInterface.onBeforeOutput(InternalVcPerBankNzOverviewInterface.java:132)
         at com.sap.xss.hr.per.nz.bank.overview.wdp.InternalVcPerBankNzOverviewInterface$External.onBeforeOutput(InternalVcPerBankNzOverviewInterface.java:208)
    I have maintained all configs in SPRO and active subtypes have been maintained....
    Please help me solve this... ITs CRITICAL for me to solve this problem....
    thanks,

    Hi,
    I think system working fine ....logically there should be entry for the infotype "0009"
    But if you want to change that then you need change the "Time constraint"  for this ...
    You can set that in table "T591A"
    go to se16 give 'T591A" then selection screen give "0009" and check the DATA.
    I think for infotype "0009 subtype "0" ( main bank ) the time contain will be "1" ......
    And its means there should be data in the PA30 for infotype "0009" .

  • Portal Runtime Error - java.lang.NullPointerException in Role Permissions

    Hello All:
    I am getting a runtime error while trying to bring up permissions for copies of SAP delivered roles.
    Any help much appreciated.
    =================
    [EXCEPTION]
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.aclEditor
    Component class : com.sap.portal.admin.acleditor.ACLEditor
    User : TESTUSER
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
         at java.security.AccessController.doPrivileged(AccessController.java:242)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:215)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.NullPointerException
         at com.sap.portal.admin.editor.pane.OutPane.calculatePEObjectId(OutPane.java:210)
         at com.sap.portal.admin.editor.pane.OutPane.createEditorLayout(OutPane.java:256)
         at com.sap.portal.admin.editor.pane.OutPane.setupComponent(OutPane.java:150)
         at com.sap.portal.admin.editor.pane.EditorPaneWrapper.mySetupComponent(EditorPaneWrapper.java:143)
         at com.sapportals.admin.wizardframework.components.FlowContainer.setupComponent(FlowContainer.java:129)
         at com.sapportals.admin.wizardframework.core.TrivialPaneFactory.getComponent(TrivialPaneFactory.java:35)
         at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:229)
         at com.sap.portal.admin.editor.Editor.doWizard(Editor.java:605)
         at com.sap.portal.admin.editor.Editor.run(Editor.java:150)
         at com.sap.portal.admin.editor.AbstractEditorComponent.doContent(AbstractEditorComponent.java:59)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         ... 29 more
    #1.5 #001125C00D9B007C000005E00017E09600044CCF2EFD55C4#1210352637138#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#TESTUSER#121429##mdt2ds111_SC1_1097250#TESTUSER#30ca97d01de611ddac19001125c00d9b#SAPEngine_Application_Thread[impl:3]_10##0#0#Error##Java###05:03_09/05/08_0167_1097250
    [EXCEPTION]
    #1#java.lang.NullPointerException
         at com.sap.portal.admin.editor.pane.OutPane.calculatePEObjectId(OutPane.java:210)
         at com.sap.portal.admin.editor.pane.OutPane.createEditorLayout(OutPane.java:256)
         at com.sap.portal.admin.editor.pane.OutPane.setupComponent(OutPane.java:150)
         at com.sap.portal.admin.editor.pane.EditorPaneWrapper.mySetupComponent(EditorPaneWrapper.java:143)
         at com.sapportals.admin.wizardframework.components.FlowContainer.setupComponent(FlowContainer.java:129)
         at com.sapportals.admin.wizardframework.core.TrivialPaneFactory.getComponent(TrivialPaneFactory.java:35)
         at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:229)
         at com.sap.portal.admin.editor.Editor.doWizard(Editor.java:605)
         at com.sap.portal.admin.editor.Editor.run(Editor.java:150)
         at com.sap.portal.admin.editor.AbstractEditorComponent.doContent(AbstractEditorComponent.java:59)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
         at java.security.AccessController.doPrivileged(AccessController.java:242)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:215)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    =====================

    Praveen:
    I have already tried this and it did not fix the problem.
    Here is something more bizarre, I get the error when the copied roles are in 3rd folder level after Portal Content.
    For instance:
    1) Portal Content > Test Folder 1 (ZContentAdmin)  ....... NO ERROR
    2) Portal Content > Test Folder 1 > Test Folder 2 (ZContentAdmin) .......... NO ERROR
    3) Portal Content > Test Folder 1 > Test Folder 2 > Test Folder 3 (ZContentAdmin) ..... ERROR
    Just to reiterate, custom roles work fine, it is just when I do a Copy/Delta copy of SAP delivered content roles.....
    Looking for a solution.
    Khurram
    Edited by: Khurram Mahmudi on May 9, 2008 9:32 PM

  • Error in file-webservice- file (Error: java.lang.NullPointerException)

    Hi everybody,
    I have configured a file-webservice-file without BPM scenario...as explained by Bhavesh in the following thread:
    File - RFC - File without a BPM - Possible from SP 19.
    I have  used a soap adapter (for webservice) instead of rfc .My input file sends the date as request message and gets the sales order details from the webservice and then creates a file at my sender side.
    1 communication channel for sender file
    1 for receiver soap
    1 for receiver file
    Error: java.lang.NullPointerException
    What could be the reason for this error
    thanks a lot
    Ramya

    Hi Tanaya,
    I monitored the channels in the Runtime work bench and the error is in the sender ftp channel.The other 2 channel status is "not used" in RWB.
    1 sender ftp channel
    1 receiver soap channel
    1 receiver ftp channel.
    2009-12-16 15:02:00 Information Send binary file  "b.xml" from ftp server "10.58.201.122:/", size 194 bytes with QoS EO
    2009-12-16 15:02:00 Information MP: entering1
    2009-12-16 15:02:00 Information MP: processing local module localejbs/AF_Modules/RequestResponseBean
    2009-12-16 15:02:00 Information RRB: entering RequestResponseBean
    2009-12-16 15:02:00 Information RRB: suspending the transaction
    2009-12-16 15:02:00 Information RRB: passing through ...
    2009-12-16 15:02:00 Information RRB: leaving RequestResponseBean
    2009-12-16 15:02:00 Information MP: processing local module localejbs/CallSapAdapter
    2009-12-16 15:02:00 Information The application tries to send an XI message synchronously using connection File_http://sap.com/xi/XI/System.
    2009-12-16 15:02:00 Information Trying to put the message into the call queue.
    2009-12-16 15:02:00 Information Message successfully put into the queue.
    2009-12-16 15:02:00 Information The message was successfully retrieved from the call queue.
    2009-12-16 15:02:00 Information The message status was set to DLNG.
    2009-12-16 15:02:02 Error The message was successfully transmitted to endpoint com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Internal Server Error using connection File_http://sap.com/xi/XI/System.
    2009-12-16 15:02:02 Error The message status was set to FAIL.
    Now, the error is internal server error.What can I do about this?
    thanks a lot
    Ramya

Maybe you are looking for

  • 9.3.0 Update Failed.

    Hi all, Trying to update Acrobat Pro to 9.3.0 has consistently failed. Any idea how this can be fixed? Attached log showing failure at a specific file. Executing ApplyOperation.py for payload: 2 Start Time-   02/09/10  14:21:09 /bin/mkdir -p -m 775 '

  • How to turn off the 32-bit bridge interface dialogue?

    Hi guys, is there a way to open 32bit plugins in logic 64bit mode without having to confirm that annoying plug-in interface dialogue each time? Thanks Eddie

  • Time Machine Backups Stall out

    Hello, I thought I had this resolved when I replaced the backup drive.  Time machine backups of my server stall out.  They start seemingly fine, but eventually they will reach a point where the progress bar just stops progressing.  I can find nothing

  • Search function, user/member login, shopping cart

    I'm hitting some major walls here. I'm a graphic designer and I am building a website for a company that needs a search function for their products, a user/member function so customers can have accounts, and also a shopping cart. I need a pro to poin

  • Cluster creation help!

    Hi there Does any one have a fool-proof document for creating and proving a 2 server ColdFusion 10 cluster? Most of the documents I have found are missing something.  More specifically, what is the difference between HTTP Port and Admin Component Por