HTTP Inbound error - 500 SOAP PARSING HEADER

I am working with receiving inbound acknowledgement a text file from the customer to FTP through XI, the URL I supplied to the customer is in the form.
http://<url address linked to XI server:port>/sap/xi/engine?namespace=<namespace>&
interface=<sender interface>&
service=<Sender Service>&
party=&agency=&scheme=&
QOS=EO&sap-user=&sap-password=&sap-client=005&sap-language=EN
Customer is receiving the error message and I don't see any trace of them contacting our XI. When I tried testing usign SAP pI 7 client test tool with out providing /SAP/XI/engine? it doesn't throw any error and no xml payload file generated in FTP though no error seen.
Any one have any idea what this probelm could be?
Thanks,
Menaga

Hi,
you can do this
1. start ICF trace  form transaction SICF in order to log the message which is being send by your partner
this way if anything is reaching XI you will see it in the log
http://help.sap.com/saphelp_nw04/Helpdata/EN/80/b2dd3a6dac703be10000000a11405a/content.htm
Regards,
Michal Krawczyk

Similar Messages

  • Mail for Exchange : HTTP Server Error 500

    Just installed MFE on my Nokia E90 and having issues synching it up with my exchange account. I checked the log and this is what it says :
    19/12/2008 9:23:03 Setting OFFLINE Status to False
    19/12/2008 9:23:03 Setting ROAMING status to False
    19/12/2008 9:23:03 Setting DISK FULL status to False
    19/12/2008 9:23:08 Setting OFFLINE Status to False
    19/12/2008 9:23:08 Setting ROAMING status to False
    19/12/2008 9:23:08 Setting DISK FULL status to False
    19/12/2008 9:24:34 Profile Updated
    19/12/2008 9:24:34 unable to open snapshot database (-1)
    19/12/2008 9:24:34 OffPeakTime active
    19/12/2008 9:24:42 Cancel Job:0, Type:"Sync Job On Profile":
    19/12/2008 9:25:06 HTTP error code=500
    19/12/2008 9:25:06 HTTP Server Error 500: Internal Server Error
    19/12/2008 9:49:10 OffPeakTime active
    19/12/2008 9:55:09 HTTP error code=500
    19/12/2008 9:55:09 HTTP Server Error 500: Internal Server Error
    19/12/2008 10:02:01 HTTP error code=500
    19/12/2008 10:02:01 HTTP Server Error 500: Internal Server Error
    19/12/2008 10:04:21 Profile Updated
    19/12/2008 10:04:22 OffPeakTime active
    19/12/2008 10:04:30 HTTP error code=500
    19/12/2008 10:04:30 HTTP Server Error 500: Internal Server Error
    19/12/2008 10:05:17 HTTP error code=500
    19/12/2008 10:05:17 HTTP Server Error 500: Internal Server Error
    19/12/2008 10:09:39 HTTP error code=500
    19/12/2008 10:09:39 HTTP Server Error 500: Internal Server Error
    19/12/2008 10:11:06 OffPeakTime active
    19/12/2008 10:11:06 Setting OFFLINE Status to False
    19/12/2008 10:11:07 Setting ROAMING status to False
    19/12/2008 10:11:07 Setting DISK FULL status to False
    19/12/2008 10:11:23 HTTP error code=500
    19/12/2008 10:11:24 HTTP Server Error 500: Internal Server Error
    19/12/2008 10:35:27 Profile Updated
    19/12/2008 10:35:28 OffPeakTime active
    19/12/2008 10:35:29 Profile Updated
    19/12/2008 10:35:29 OffPeakTime active
    19/12/2008 10:35:30 Cancel Job:1, Type:"Sync Job On Profile":
    19/12/2008 10:35:43 HTTP error code=500
    19/12/2008 10:35:43 HTTP Server Error 500: Internal Server Error
    19/12/2008 10:40:12 OffPeakTime active
    19/12/2008 10:42:23 Profile Updated
    19/12/2008 10:42:23 OffPeakTime active
    19/12/2008 10:42:36 HTTP error code=500
    19/12/2008 10:42:36 HTTP Server Error 500: Internal Server Error
    19/12/2008 10:43:44 Profile Updated
    19/12/2008 10:43:45 OffPeakTime active
    19/12/2008 10:43:45 Profile Updated
    19/12/2008 10:43:46 OffPeakTime active
    19/12/2008 10:43:59 HTTP error code=401
    19/12/2008 10:43:59 HTTP Server Error 401: UnAuthorized
    19/12/2008 10:46:17 Profile Updated
    19/12/2008 10:46:17 OffPeakTime active
    19/12/2008 10:46:18 Profile Updated
    19/12/2008 10:46:19 OffPeakTime active
    19/12/2008 10:46:20 Cancel Job:5, Type:"Sync Job On Profile":
    19/12/2008 10:46:33 HTTP error code=401
    19/12/2008 10:46:33 HTTP Server Error 401: UnAuthorized
    19/12/2008 10:47:50 HTTP error code=401
    19/12/2008 10:47:50 HTTP Server Error 401: UnAuthorized
    19/12/2008 10:49:54 HTTP error code=401
    19/12/2008 10:49:54 HTTP Server Error 401: UnAuthorized
    19/12/2008 10:51:02 Profile Updated
    19/12/2008 10:51:02 OffPeakTime active
    19/12/2008 10:51:03 Profile Updated
    19/12/2008 10:51:04 OffPeakTime active
    19/12/2008 10:51:15 HTTP error code=500
    19/12/2008 10:51:15 HTTP Server Error 500: Internal Server Error
    19/12/2008 10:53:02 Profile Updated
    19/12/2008 10:53:03 OffPeakTime active
    19/12/2008 10:53:04 Profile Updated
    19/12/2008 10:53:04 OffPeakTime active
    19/12/2008 10:53:05 Cancel Job:10, Type:"GlobalAddressLookup":
    19/12/2008 10:53:31 Profile Updated
    19/12/2008 10:53:31 Cancel Job:11, Type:"UnKnown Job":
    19/12/2008 10:53:31 OffPeakTime active
    19/12/2008 10:53:32 HTTP error code=403
    19/12/2008 10:53:32 HTTP Server Error 403 : Forbidden
    19/12/2008 10:53:43 HTTP error code=403
    19/12/2008 10:53:43 HTTP Server Error 403 : Forbidden
    19/12/2008 10:53:51 HTTP error code=403
    19/12/2008 10:53:51 HTTP Server Error 403 : Forbidden
    19/12/2008 10:54:41 Profile Updated
    19/12/2008 10:54:41 OffPeakTime active
    19/12/2008 10:54:50 HTTP error code=500
    19/12/2008 10:54:50 HTTP Server Error 500: Internal Server Error
    19/12/2008 11:24:50 HTTP error code=500
    19/12/2008 11:24:50 HTTP Server Error 500: Internal Server Error
    19/12/2008 11:54:51 HTTP error code=500
    19/12/2008 11:54:51 HTTP Server Error 500: Internal Server Error
    20/12/2008 12:17:46 HTTP error code=500
    20/12/2008 12:17:46 HTTP Server Error 500: Internal Server Error
    20/12/2007 12:24:37 OffPeakTime active
    20/12/2007 12:24:49 HTTP error code=500
    20/12/2007 12:24:49 HTTP Server Error 500: Internal Server Error
    20/12/2008 12:25:23 AUDT Timer expired
    20/12/2008 12:25:23 OffPeakTime active
    20/12/2008 12:25:23 OffPeakTime active
    20/12/2008 12:25:25 OffPeakTime active
    20/12/2008 12:26:38 HTTP error code=500
    20/12/2008 12:26:38 HTTP Server Error 500: Internal Server Error
    20/12/2007 12:29:46 OffPeakTime active
    20/12/2008 12:32:11 AUDT Timer expired
    20/12/2008 12:32:11 OffPeakTime active
    20/12/2008 12:32:11 OffPeakTime active
    20/12/2008 12:32:21 HTTP error code=500
    20/12/2008 12:32:21 HTTP Server Error 500: Internal Server Error
    20/12/2008 12:40:09 OffPeakTime active
    Any idea ?

    I have the same problem, the microsoft link not solve my problem:
     23/10/2009 11:42:36 Profile Updated
    23/10/2009 11:42:36 PeakTime active
    23/10/2009 11:42:42 HTTP error code=501
    23/10/2009 11:42:42 HTTP Server Error 501: Not Implemented
    23/10/2009 12:16:55 Profile Updated
    23/10/2009 12:16:55 PeakTime active
    23/10/2009 12:16:56 PING Command Requested
    23/10/2009 12:16:59 HTTP error code=403
    23/10/2009 12:16:59 Exception during Ping.
    23/10/2009 12:16:59 HTTP Server Error 403 : Forbidden
    23/10/2009 12:17:00 Error occurred during Ping.
    23/10/2009 12:17:00 Error occurred during Ping. Setting Status to Waiting For Reconnect
    23/10/2009 12:17:15 HTTP error code=403
    23/10/2009 12:17:15 HTTP Server Error 403 : Forbidden
    23/10/2009 12:17:35 HTTP error code=403
    23/10/2009 12:17:35 HTTP Server Error 403 : Forbidden
    23/10/2009 12:17:55 HTTP error code=403
    23/10/2009 12:17:55 HTTP Server Error 403 : Forbidden
    23/10/2009 12:21:55 PING Command Requested
    23/10/2009 12:21:58 HTTP error code=403
    23/10/2009 12:21:58 Exception during Ping.
    23/10/2009 12:21:58 HTTP Server Error 403 : Forbidden
    23/10/2009 12:21:58 Error occurred during Ping.
    23/10/2009 12:21:58 Error occurred during Ping. Setting Status to Waiting For Reconnect
    Many thanks 

  • Portal EP 7.3 FQDN Throwing HTTP Internal Error 500 on every link

    Hi Expert,
    Currently we have a strange issue on the portal 7.3 that might you had this issue also. The problem is, everytime we use the FQDN, all the links in the j2ee / portal will throwing an error 500. Currently the portal was on initial sp level and connect to the Abap UME. If we use without fqdn, just normal hostname its fine.
    The error message from default trace is like below:
    #2.#2012 03 07 10:16:20:281#+00#Error#com.sap.engine.services.servlets_jsp.ISE500#
    com.sap.ASJ.web.000500#BC-NWA-INC-UIF#sap.com/tclmitsamuimainframewd#C0000A902D05014B00000004000058D6#405732050000000004#sap.com/tclmitsamuimainframewd#com.sap.engine.services.servlets_jsp.ISE500#J2EE_GST_EPD#0##5A2AB61B683C11E1A38B0000182EFAD2#5a2ab61b683c11e1a38b0000182efad2#5a2ab61b683c11e1a38b0000182efad2#0#Thread[HTTP Worker [@1801061142],5,Dedicated_Application_Thread]#Plain##
    500 Internal Server Error is returned for HTTP request [http://vhscepdapp01.sg.axongroup.co.uk:54000/webdynpro/resources/sap.com/tclmitsamuimainframe~wd/FloorPlanApp]:
      component [dispatcher],
      web module [webdynpro/resources/sap.com/tclmitsamuimainframe~wd],
      application [sap.com/tclmitsamuimainframe~wd],
      DC name [sap.com/tclmitsamuimainframe~wd],
      CSN component[BC-NWA-INC-UIF],
      problem categorization [com.sap.ASJ.web.000137],
      internal categorization [99433791].
    [EXCEPTION]
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to retrieve client for current request. Causing exception is  nested.
            at com.sap.tc.webdynpro.clientserver.task.Task.getClient(Task.java:457)
            at com.sap.tc.webdynpro.serverimpl.wdc.um.ClientUserFactory.forceLoggedInClientUser(ClientUserFactory.java:106)
            at com.sap.tc.webdynpro.serverimpl.wdc.um.ClientUserFactory.checkAuthentication(ClientUserFactory.java:284)
            at com.sap.tc.webdynpro.serverimpl.core.um.AbstractClientUserFactory$1.checkAuthentication(AbstractClientUserFactory.java:223)
            at com.sap.tc.webdynpro.services.sal.um.api.WDClientUser.checkAuthentication(WDClientUser.java:233)
            at com.sap.tc.webdynpro.clientserver.session.RequestManager.checkAuthentication(RequestManager.java:837)
            at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:294)
            at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
            at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
            at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:55)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
            at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
            at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:453)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
            at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
            at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
            at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
            at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
            at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
            at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
            at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
            at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:462)
            at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:270)
            at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
            at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
            at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
            at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: com.sap.tc.webdynpro.services.cal.core.exceptions.WDClientException: Found no client: clientNameReqParam=null, clientNameAppParam=null, useragent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)
            at com.sap.tc.webdynpro.clientserver.cal.ClientInspector.findClientContainer(ClientInspector.java:211)
            at com.sap.tc.webdynpro.clientserver.cal.ClientInspector.getClient(ClientInspector.java:103)
            at com.sap.tc.webdynpro.clientserver.task.Task.getClient(Task.java:455)
            ... 50 more
    Appreciate if someone could help to solve this.
    Cheers,
    Raff
    Edited by: Raffaello Sanzio Rodiman on Mar 7, 2012 11:28 AM

    Hi
    If you are using IE 9, Change the browser mode to 8.
    This can be done in IE9,  Tools -->  F12 Developer tools --> Browser Mode --> Internet Explorer 8.
    Regards
    Lakshmi

  • ISA550 permit HTTPS inbound, error that SSLVPN is already using port

    I'm trying to permit HTTPS from anywhere to an internal web server. The ISA is running SSLVPN on one IP address. I am trying to create an ACL and NAT that allows HTTPS on a totally different IP address than the SSLVPN runs on. If I go to Firewall>NAT>Port Forwarding and create a port forwarding rule as follows:
    Original Service: HTTPS
    Translated Service: HTTPS
    Translated IP: Internal server IP address
    WAN: WAN1
    WAN IP: External server IP address - not the same as the interface IP address
    I get the following error:
    The service HTTPS already is used by SSLVPN. Please use another service.
    I feel like I'm missing something simple/stupid as I can't imagine that you can't have both SSLVPN and an internal HTTPS server running on two totally different IP addresses at the same time. TIA.

    Hi,
    You can try with :
    Original Service: 8080
    Translated Service: HTTPS
    Translated IP: Internal server IP address
    regards
    Moorthy

  • Header missing in SOAP message header (SAP XI Extension)

    Hi Experts,
    We are implementing interface MasterDataUpdateConfirmation_Out between 2 SAP ERP systems. The middleware is SAP PI.
    SAP PI team requested a change in this interface Stack - Replace Stack ABAP by Stack Java. The changes were made.
    However, now we get an error in the interface in the SAP ERP sender system, but the message arrives to SAP PI where is processed without errors and also arrives to SAP ERP receive system and the message is also processes without errors.
    The error we have in XML message in SAP ERP sender system is:
    XML element {http://schemas.xmlsoap.org/soap/envelope/}Header missing in
    SOAP message header (SAP XI Extension)
    Exception of class CX_XMS_SYSERR_PARSER
    Can anyone please help us? We have no ideia what to do.
    Thanks in advance,
    RS

    Hi again,
    I don't know if it is important, but the communication is asynchronous and the sender system is SAP ECC 6.0.
    Thanks!

  • HTTP response code 500 : Error during parsing of SOAP header

    Hi Experts,
    I have a MAIL to IDOC scenario.  An external third party emails invoices to our inbox - which we pick up and process the attachment.  All is well when I test the scenario internally, but when the third party emails it fails with (see ERROR MESSAGE below).
    When I look at the SOAP header of the failed message I see the values from the dump in this field:
      <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderTHREAD-INDEX">AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=</sap:Record>
    Can anyone tell me what SHeaderTHREAD-INDEX does?  Or what my problem is  (Our email is Outlook)
    ERROR MESSAGE.........
    SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/WRONG_VALUE; Params: SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14), AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=協彎䅍䔾ਉ़䥎噏䥃䕟乏㸸㌱ㄵㄹ㰯䥎噏䥃䕟乏㸊उ㱁䵏啎呟䕘䍌彖䅔㸷⸵〼⽁䵏啎呟䕘䍌彖䅔㸊उ㱃啒剅乃失㹅啒㰯䍕剒䕎䍙ㄾਉ़䅍何乔彖䅔㸱⸴㜼⽁ꯃ䅢坡汫, ST: ST_XM; AdditionalText: An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC; ApplicationFaultMessage:  ; ErrorStack: XML tag SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14) (or one of the attributes) has the incorrect value AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQ An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC Data loss occurred when converting AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1p
    Transmitting the message to endpoint http://sdcxp1-ci.na.fmo.com:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header.

    We work with Microsoft Outlook, but I'm sure this could work with any email system.
    This error only came from external emails - what we did in the end is to get the third party to email a particular email (email1) in our company.  This is set up as a regular email account.  On this email put a forward rule to email2 for a particular sender/subject.  email2 is set up as POP3 so that XD1 can poll it - we also block any emails except from email1.
    Doing this accomplishes a couple of things:
    1)  We get around the error because XI polls email2 (which has adapter settings of IMAP4 so we can see MAIL adapter attributes ie. sender, subject etc...When we originally had as POP3 we were not able to see these - but setting as IMAP4 causes the error for external emailers)
    2) We have a SPAM filter - the XI email is clean from SPAM and the adapter will not have errors, as it only receives valid emails to process
    3) We have a central email (email1) which is used to archive all XI emails - we use this for all email scenarios (as we also save to folder and forward in the rule)
    Hope this helps your situation.

  • SOAP Sync: HTTP/1.1 500 Internal Server Error

    Hi,
                      My scenario is SOAP to SOAP Synchronous. I created WSDL from Id by using (http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>.  And Sender interface details.
    I am testing SOAP Synchronous scenario through SOAPUI tool. When sending the requrest from SOAP UI i am getting "HTTP/1.1 500 Internal Server Error" error.
    Log:
    <?xml version='1.0'?>
    <!-- see the documentation -->
    <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
      <SOAP:Body>
        <SOAP:Fault>
          <faultcode>SOAP:Server</faultcode>
          <faultstring>Server Error</faultstring>
          <detail>
            <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
              <context>XIAdapter</context>
              <code>ADAPTER.JAVA_EXCEPTION</code>
              <text><![CDATA[
    com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve binding for the given channelId: Binding:CID=null;
    When i test the URL in explorer its giving "OK". What will be the probelm? Pls let me know.
    Regards,
    Dev

    Hi,
       This might be the problem with url...
    It should be in the below format...
    http://host:port/XISOAPAdapter/MessageServlet?channel=party:sender component:sender Communicaton Channel
    Regards,
    Naveen

  • HTTP server code 500 reason Internal Server Error explanation Error during

    Hi,
    I am trying to connect to SAP TM (Tranportation Management) System using HTTP adapter using PI 7.0.The scenario is
    ECC ->PI->SAP TM. I have configured HTTP adapter as the receiver with addressing type as HTTP Destination. I have created a RFC destination of type H pointing to SAP TM on PI. I have encountered the following error after executing the scenario.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
      <SAP:P1>500</SAP:P1>
      <SAP:P2>Internal Server Error</SAP:P2>
      <SAP:P3>Error during parsing of SOAP header</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Thanks,
    Kiran

    Error during parsing of SOAP header
    Can you mention what are the settings done in Receiver HTTP channel.....the request that you send to target is not in proper format.
    One reason could be incorrect Content Type.....is it text/XML ?
    Regards,
    Abhishek.

  • HTTP server code 500 reason Internal Server Error

    HI,
    I am getting following error in Call Adapter
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Message canceled
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
      <SAP:P1>500</SAP:P1>
      <SAP:P2>Internal Server Error</SAP:P2>
      <SAP:P3>Internal Server Error</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Internal Server Error</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I have a Business system that is sending the material master data to a different Business System via XI. The message is received by XI correctly. XI correctly performs the transformation and identifies the message interface and selects correct receiver for the message. XI communicates with the receiving business system via the appropriate communication channel.
    The message "fails" in the receiving system with the following error:
    HTTP server code 500 reason Internal Server Exception explanation Error parsing of SOAP header.
    The channel is using HTTP Adapter type, and i cross checked the communication channel details like Addressing type, target host, service number, path, user name, user password.......each and every detail is correct.
    Please help me out to find the solution to the problem.
    Points will be gladly awarded.
    Edited by: Ashish Soni on Sep 24, 2008 9:02 PM

    try sending the same XML message picking from moni and check whether you are getting same error or not?
    if you get same error then check at web server for logs there you can find exact error.

  • CLIENT_SEND_FAILED HTTP ERROR 500 Internal Server Error

    Hello Experts,
        I have a scenario from Proxy->SOAP.  I am facing the below error.  I have many other Scenarios from Proxy -> SOAP all of them are working fine except this.
    I am using NW07_06_REL With SP 06
    <?xml version="1.0"; encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
      <SAP:P1>500</SAP:P1>
      <SAP:P2>Internal Server Error</SAP:P2>
      <SAP:P3>(See attachment HTMLError for details)</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error while sending by HTTP (error code: 500, error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    HTML Error
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not create Message from TransportMessage. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIMessage creation failed (inbound). Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage. Reason: com.sap.aii.af.sdk.xi.mo.MalformedMessageException: Unexpected length of element <sap:Main><sap:Interface @sap:namespace> = xxxxx; nested exception caused by: com.sap.aii.af.sdk.xi.util.XMLScanException: Unexpected length of element <sap:Main><sap:Interface @sap:namespace> = XXXXXX
    The message clogs in the qRFC Queue. Not able to re-process it.
    I have already checked Most of the threads on the SDN, They didn't help me.
    Any help greatly appreciated
    Edited by: Kannan Narayanan on Dec 28, 2010 3:29 AM

    --> Error while sending by HTTP (error code: 500, error text: Internal Server Error)
    Answer: 500 internal Server Error is due to server down or network related problems.
    Import the wsdl in xmlspy or SOAPUI and see the behavior first. If the error is same, you can conclude it due to other end .(i meant server that host webservice causing it). we have very similar issues in our end. This is server down error mostly.
    Hope I answered your question.

  • HTTP/1.1 500 Internal Server Error.......content-type: text/html;charset=ut

    Hi
    I have created one web service... while i am testing in WSNAVIGATOR i am getting the following error.........
    <b>Request</b>
    POST /sap/bc/srt/rfc/sap/ZZ_BAPI_CUSTOMER_DISPLAY?sap-client=100 HTTP/1.1
    Host: SAPDEV:8000
    Content-Type: text/xml; charset="UTF-8"
    Connection: close
    Authorization: <value is hidden>
    Content-Length: 578
    SOAPAction: ""
    <?xml version="1.0" encoding="UTF-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Header><sapsess:Session xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/"><enableSession>true</enableSession></sapsess:Session></SOAP-ENV:Header><SOAP-ENV:Body><ns1:CustomerDisplay xmlns:ns1='urn:sap-com:document:sap:soap:functions:mc-style'><CustomerNo>0000040009</CustomerNo></ns1:CustomerDisplay></SOAP-ENV:Body></SOAP-ENV:Envelope>
    <b>Response</b>
    HTTP/1.1 500 Internal Server Error
    content-type: text/html;charset=utf-8
    content-length: 3175
    how to solve this problem.... please help me
    Regards
    Ravi Shankar B
    Message was edited by:
            RaviShankar B

    generally HTTP500 error would generate ABAP dumpt - check txn ST22.
    other thing i have noticed is SAPDEV:8000
    you have set up FQDN (fully qualified domain name) for web applications to work properly.
    for more on FQDN check this.
    https://wiki.sdn.sap.com/wiki/display/BSP/FullyQualifiedDomainName%28FQDN%29
    Regards
    Raja

  • HTTP Status Code 200 Received But Error During Response Parsing

    Hi Experts,
    We are testing a simple Proxy(ECC) to File scenario in QA. This interface was working fine in Dev but we are getting the following error here in QA:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!--  Call Adapter  -->
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">OK_BUT_NO_XI_MESSAGE</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    We searched other threads but could not get any solution. Please provide suggestions.
    Thank You.
    Regards,
    Anandan

    the problem was due to high volume message (247 MB ) ...Java stack was not able to process this huge message ,that is the reason ,it started automatically  and as a result  , "HTTP Status Code 200 Received But Error During Response Parsing" due to unavailability of AFW during Call adapter step in the pipeline processing...
    We have done the following activities in order to solve this problem....
    increase the value of  icm/HTTP/max_request_size_KB to 512MB
                                        icm/wp_roll_timeout   to maximum
                                        HTTP TIMEOUT to 1800 sec
                                       icm/wp_roll_timeout   to maximum
                                         mpi/total_size_MB  to maximum
                                       mpi/buffer_size  to maximum
    and then increased the maxthreadcount ,maxcontentlength using config tool...
    and also increased the java heap size to maximum....
    After doing everything ,the file has been successfully processed....
    the problem has been resolved...

  • SOAP version for B2B HTTP inbound message in SOA Suite 11.1.1.7

    Is there a way to find out the SOAP version supported by B2B HTTP inbound message in SOA Suite 11.1.1.7? Has there been a upgrade of SOAP version to SOAP 1.2?
    The reason behind this assumption is because we are facing following error when an external service posts an XML message enclosed in SOAP envelope (SOAP 1.1) to B2B Sync Receiver Servlet:
    Mime Header Content-Type: text/xml requires SOAP envelope namespace
    Since SOAP headers are already added in the message we are not expecing to face such issue. As per my understanding this issue maybe seen when there is a SOAP version mismatch.
    Moreover, this issue is not seen when this external service posts the same SOAP message to B2B Sync Receiver of SOA suite 11.1.1.6.
    Any help would be highly appreciated.
    Thanks,

    I resolved the issue by myself, The connection factory which I was referring was duplicated. Hence messages were not dequeueing.
    I would be able to found the issues by creating a similar test case scenario.
    Cheers,
    B

  • Proxy error - HTTP status code 500

    Hi,
    Scenario: Asynchronous Proxy (R/3 4.7) to 3rd Party (JDBC)
    We applied patches to JAVA on the XI side to fix a bug, the process worked before the patches. I am now getting an error on R/3 i.e. the data is not reaching XI.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Call Integration Server
      -->
    - <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
      <SAP:Context />
      <SAP:Code p1="500" p2="Error during conversion of XI message" p3="" p4="">HTTP.HTTP_STATUS_CODE_NEQ_OK</SAP:Code>
      <SAP:Text language="EN">HTTP status code 500 : Error during conversion of XI message</SAP:Text>
      </SAP:ErrorHeader>
    Any ideas. Thanks,
    Leanne

    Hi,
    SAP requested we implement patches, this sorted out the proxy issue. The message now arrives in XI.
    I have now encountered another problem, this process was working prior to the patches being implemented. I noticed that the communication channels now look different, any ideas?
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: JDBC Adapter configuration not initialized: null</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Thanks,
    Leanne

  • Posting XML via HTTP post returns "Envelope missing in SOAP message header"

    Hi,
    I am trying to post a simple XML message directly to the integration server using an html document, where the form that contains the XML message is a simple
    <b><FORM action="http://servername:8000/sap/xi/engine?type=entry" method="post"></b>
    So, I add my xml message like this:
    <?xml version="1.0" encoding="UTF-8">
    <ns:PlantMaintenanceMessageType xmlns:ns="http://sap.com/demo/plantmaintenance">
          <EquipmentID>SLIEQUIP5</EquipmentID>
          <FunctionalLocation>KB</FunctionalLocation>
          <Date/>
          <Time/>
    </ns:PlantMaintenanceMessageType>
    but I get a message back from the Integration Server as:
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProtocol</SAP:Category>
      <SAP:Code area="PARSER">ITEM_MISSING</SAP:Code>
      <SAP:P1>Envelope</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <b><SAP:Stack>XML tag Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack></b>
      </SAP:Error>
    Seems like I am missing the Envelope so my Integration Server can understand my post. What does the Envelope look like or should conatain so that the Integration Server accepts my XML file ?
    Thanks !

    This is the trace
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <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 =</Trace>
      <Trace level="1" type="T">Sender agency external =</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender 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="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
      <Trace level="2" type="T">Host = sapqxh:8020</Trace>
      <Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
      <Trace level="2" type="T">Remote address = 10.228.137.106</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="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
      <Trace level="3" type="T">Getting type of XMB...</Trace>
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="2" type="T">XMB kind = CENTRAL</Trace>
      <Trace level="3" type="T">Start pipeline found</Trace>
      <Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</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="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="3" type="T">system-ID = QXH</Trace>
      <Trace level="3" type="T">client = 220</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = PISUPER</Trace>
      <Trace level="1" type="Timestamp">2008-07-18T14:19:04Z 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 = 4880474945AE67E2E10000000AE4896A</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="3" type="T">QOS = EO</Trace>
      <Trace level="3" type="T">Message-GUID = 4880474945AE67E2E10000000AE4896A</Trace>
      <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="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">Generate prefixed queue name</Trace>
      <Trace level="1" type="T">Queue name : XBTL0000</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTL0000</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="3" type="T">Setup qRFC Scheduler</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="3" type="T">Call qRFC .... MsgGuid = 4880474945AE67E2E10000000AE4896A</Trace>
      <Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
      <Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
      <Trace level="3" type="T">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="3" type="T">Version number = 000</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 001</Trace>
      <Trace level="3" type="T">Message version 000</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface MIOA_US139_EmployeeData*</Trace>
      <Trace level="1" type="T">select interface namespace urn:abbott-com:US139</Trace>
      <Trace level="1" type="T">found interface MIOA_US139_EmployeeData</Trace>
      <Trace level="1" type="T">found action ARCH</Trace>
      <Trace level="1" type="T">set interface action to ARCH</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
      <Trace level="3" type="T">Trace object available again now. OK.</Trace>
      <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
      <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
      <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
      <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
      </Trace>
      <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="3" type="T">message version successfully read from persist version= 000</Trace>
      <Trace level="2" type="T">Increment log sequence to 001</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = QXH</Trace>
      <Trace level="3" type="T">client = 220</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = PISUPER</Trace>
      <Trace level="1" type="Timestamp">2008-07-18T14:19:08Z 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="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline attributes</Trace>
      <Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">ENABLE = 1</Trace>
      <Trace level="3" type="T">TRACELEVEL = 0</Trace>
      <Trace level="3" type="T">EXEMODE = A</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline elements</Trace>
      <Trace level="3" type="T">ELEMPOS = 0001</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0002</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0003</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0004</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0007</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0008</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0009</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
      <Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET 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">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</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">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</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_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 level="2" type="T">Start without given receiver</Trace>
      <Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
      <Trace level="2" type="T">...valid Receiver w/o Condition: - BS_AIMS</Trace>
      <Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
      <Trace level="2" type="T">Number of Receivers:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-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">Message version 001</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
      <Trace level="1" type="Timestamp">2008-07-18T14:19:11Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</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">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</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_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 level="2" type="T">Check conditions for (Inb: Party Srvc If) BS_AIMS MIIA_US139_EmployeeData</Trace>
      <Trace level="2" type="T">...valid InbIf without Condition: MIIA_US139_EmployeeData</Trace>
      <Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-07-18T14:19:11Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 002</Trace>
      <Trace level="3" type="T">Message version 002</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
      <Trace level="1" type="Timestamp">2008-07-18T14:19:14Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</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_RECEIVER_SPLIT</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">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</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_RECEIVER_SPLIT-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="2" type="T">got property produced by receiver determination</Trace>
      <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 = XBTM0000</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="3" type="T">Persisting message Status = 012</Trace>
      <Trace level="3" type="T">Message version 003</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
      <Trace level="3" type="T">Trace object available again now. OK.</Trace>
      <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
      <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
      <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
      <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
      </Trace>
      <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="3" type="T">message version successfully read from persist version= 004</Trace>
      <Trace level="2" type="T">Increment log sequence to 005</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = QXH</Trace>
      <Trace level="3" type="T">client = 220</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = PISUPER</Trace>
      <Trace level="1" type="Timestamp">2008-07-18T14:19:20Z 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="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline attributes</Trace>
      <Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">ENABLE = 1</Trace>
      <Trace level="3" type="T">TRACELEVEL = 0</Trace>
      <Trace level="3" type="T">EXEMODE = A</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline elements</Trace>
      <Trace level="3" type="T">ELEMPOS = 0001</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0002</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0003</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0004</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0007</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0008</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0009</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2008-07-18T14:19:20Z CET Begin of pipeline processing PLSRVID = 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="Timestamp">2008-07-18T14:19:20Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</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">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</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_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
      <Trace level="2" type="T">......attachment XI_Context not found</Trace>
      <Trace level="3" type="T">Mapping already defined in interface determination</Trace>
      <Trace level="3" type="T">Object ID of Interface Mapping 3CCA7AE76D3F33F19F8D7A8DAD494E65</Trace>
      <Trace level="3" type="T">Version ID of Interface Mapping C387A5F00F8B11DCAB84C751AAE12E82</Trace>
      <Trace level="1" type="T">Interface Mapping urn:abbott-com:US139 IM_US139_EmployeeData</Trace>
      <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_US139_EmployeeData_</Trace>
      <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
      <Trace level="2" type="T">Mode 0</Trace>
      <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_US139_EmployeeData_.</Trace>
      <Trace level="3" type="T">Load c387a5f0-0f8b-11dc-ab84-c751aae12e82, urn:abbott-com:US139, -1, com/sap/xi/tf/_MM_US139_EmployeeData_.class.</Trace>
      <Trace level="3" type="T">Search com/sap/xi/tf/_MM_US139_EmployeeData_.class (urn:abbott-com:US139, -1) in swcv c387a5f0-0f8b-11dc-ab84-c751aae12e82.</Trace>
      <Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_US139_EmployeeData_</Trace>
      <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_US139_EmployeeData_</Trace>
      <Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_US139_EmployeeData_ completed. (executeStep() of com.sap.xi.tf._MM_US139_EmployeeData_</Trace>
      <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-07-18T14:22:07Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 005</Trace>
      <Trace level="3" type="T">Message version 005</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
      <Trace level="1" type="Timestamp">2008-07-18T14:22:12Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</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_OUTBINDING</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">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</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_OUTBINDING-ENTER_PLSRV">
      <Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
      <Trace level="2" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
      <Trace level="2" type="T">-QEHCLNT230</Trace>
      <Trace level="2" type="T">-BS_AIMS</Trace>
      <Trace level="2" type="T">urn:abbott-com:US139.MIIA_US139_EmployeeData</Trace>
      <Trace level="2" type="T">Channel found: - BS_AIMS - CC_BS_AIMS_File_Out_09</Trace>
      <Trace level="2" type="T">no header mapping defined</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-07-18T14:22:12Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 006</Trace>
      <Trace level="3" type="T">Message version 006</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
    - <!--  ************************************
      -->
      <Trace level="1" type="Timestamp">2008-07-18T14:22:18Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">ADRESSMOD = SD</Trace>
      <Trace level="3" type="T">P_CLASS =</Trace>
      <Trace level="3" type="T">P_IFNAME =</Trace>
      <Trace level="3" type="T">P_METHOD =</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Unknown channel type: File</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
      <Trace level="3" type="T">ADRESSMOD = SD</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</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">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</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_IE_ADAPTER-ENTER_PLSRV">
      <Trace level="3" type="T">Channel for adapter engine: File</Trace>
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
      <Trace level="2" type="T">old values in cache (no lock found) - start reading from SLD</Trace>
      <Trace level="1" type="T">error reading SAP_XIAdapterFramework from SLD</Trace>
      <Trace level="2" type="T">Adapter Framework(s) found</Trace>
      <Trace level="2" type="T">Service Port(s) found - take first one</Trace>
      <Trace level="2" type="T">URL found</Trace>
      <Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
      <Trace level="3" type="T">URL = http://sapqxh:52000/MessagingSystem/receive/AFW/XI</Trace>
      <Trace level="3" type="T">User = PIISUSER</Trace>
      <Trace level="3" type="T">Cached =</Trace>
      <Trace level="3" type="T">Creating HTTP-client</Trace>
      <Trace level="3" type="T">HTTP-client: creation finished</Trace>
      <Trace level="3" type="T">Security: Basic authentication</Trace>
      <Trace level="3" type="T">Serializing message object...</Trace>
      <Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
      <Trace level="3" type="T">HTTP-client: request sent</Trace>
      <Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
      <Trace level="3" type="T">HTTP-client: response received</Trace>
      <Trace level="3" type="T">HTTP-client: checking status code...</Trace>
      <Trace level="3" type="T">HTTP-client: status code = 200</Trace>
      <Trace level="3" type="T">Deserializing message object...</Trace>
      <Trace level="1" type="T">Empty response received!</Trace>
      <Trace level="3" type="System_Error">HTTP-client: error response=</Trace>
      <Trace level="3" type="T">HTTP-client: closing...</Trace>
      </Trace>
      </Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 007</Trace>
      <Trace level="3" type="T">Message version 007</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 014</Trace>
      <Trace level="3" type="T">Message version 008</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </SAP:Trace>

Maybe you are looking for

  • How can I use the same domain.sites2 on two macs?

    I know iWeb is no longer supported but I still find it ok to manage my web site. I would like to work on the site from two macs. I thought I could just use the same Domain.sites2 on both macs but: if I move Domain.sites2 to dropbox folder, when I lau

  • Html snippet works w/in iweb but NOT when site is live & online @$#!

    help!? I have had a flash based slide show working on my iweb site for some time I used iweb enhancer to make it work w/ iweb 06 - now in 08 the "enhancer" doesnt work. The html snippet should & seems to...I am able to get the pages to behave very we

  • String index out of bounds?

    hi, i am writing a java program which reads in a file and then error checks it, once its done this it will output it to another file. It was working fine until i tried writing another method, now it keeps telling there is a string index out of bounds

  • Where to get ABAP Development Workbench ?

    Hello sap gurus, I alredy have SAP NetWeaver Enterprise Portal on MaxDB - Developer Edition Sneak Preview installed on my server. However I want to use the ABAP Development Workbench.  I do now want to buy a book with cds or go to the sap shop site t

  • Move MP3 files from ipod to hard drive

    Hey, My hard drive dies and I have lost everything on it. Good news is that a lot of my music is stored on my ipod. How do I get the music files, which were mostly NOT purchased from itunes but my own MP3s, off of my ipod on on to my new hard drive?