SAP PROXY determine as error SENDER.

The system id: DEV ,CLIENT: 500 LOGICAL SYSTEM: DEV500.
I have chagned logical system to DEV500N,and rechange back to DEV500.
. I CALL ABAP  PROXY IN CLIENT DEV500. Now in sxi_monitor ,the message sender always DEV500N. I don't know why it is DEV500N.
by the way . how sap pi determine the abap proxy message sender.
use client logical name to find business name ?
thanks

Check in DEV500 in SXMB_ADM--->Integration Configuration if you have set the Role of Business System as "Appl Sys" and RFC Dest of XI sys.
Also make sure you have done the configuration (change the Business System from DEV500N to DEV500) accordingly in your scenario in Intergration directory.
Have done any changes in SLD w.r.t DEV500N?? If yes then also change them.

Similar Messages

  • How does ABAP client proxy determine the sender business system

    When we use ABAP client proxy to send a message in XI-SOAP format to the integration engine, how does the client proxy determine what is the sender business system, i.e. how does it know what value it should insert in the sender service field in the SOAP envelop.
    For example, at first, the business system X8A_105 corresponds to the technical system X8A_105, so when the client proxy sends out a message, the sender service is X8A_105. Then I delete the business system X8A_105 in the SLD, and create a new business system that is associated with the technical system X8A_105.when the client proxy sends out a message, the sender_service is still X8A_105, why?

    Hi Annie,
    Execute the following function module in your business system and see what name it returns..
    LCR_GET_OWN_BUSINESS_SYSTEM.
    You can always debug the code inside the above FM to find out how it gets the business system name...
    I think the issue should be related to cache. I would also suggest you to logoff from your business system and then login again.
    Regards,
    Sumit
    Message was edited by:
            Sumit Khetawat

  • Error in retrieving data in sap proxy

    Hi, while trying do retrieve z function module in blank sap proxy (.net 2003) I get following error:
    Registry entry Software\SAP\SAP .NET Connector not set
    Parameter name InstallDir
    I use SAP .NET Connector 2.0, and system is ecc 6.0 unicode. How to solve this?
    Thanks in advance,

    Hi,
    check the below the links
    http://help.sap.com/saphelp_nw2004s/helpdata/en/b4/79cb9463b89a41a73e1e2805eb4bf7/content.htm
    https://media.sdn.sap.com/html/submitted_docs/dotnet/Programming%20with%20PDK%20for%20.NET/Connecting%20to%20SAP%20NetWeaver%20Systems/Using%20SAP%20.NET%20Connector.htm
    please check the configuration is done properly or not.
    let us know if u have nay issues,
    Regards,
    Ravi

  • File to proxy ..HTTP_RESP_STATUS_CODE_NOT_OK error in sxmb_moni??

    Hi friends..
    in file to proxy.. i am getting error like this..
    <?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">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code><SAP:P1>500 </SAP:P1><SAP:P2>Internal Server Error</SAP:P2><SAP:P3></SAP:P3><SAP:P4></SAP:P4><SAP:AdditionalText><html><head><title>SAP Web Application Server Error</title>
    <style type="text/css">
    body { font-family: arial, sans-serif;}
    </style>
    </head>
    <BODY text="#172972" link="#808080" vlink="#808080"
    alink="#8e236b" bgcolor=white  leftmargin="0" topmargin="0"
    marginheight="0" marginwidth="0">
    <table height="61" width="100%" border="0" cellspacing="0"
    cellpadding="0"><tr><td background="http://dceazar01:8010/sap/public/icman/img/bluebar_tile.gif"
    height="30"><table> <tr> <td width=5></td> <td width=20% nowrap><font face=arial size="-1" color=white>SAP Web Application Server
    </font></td><td width=75% align="right" nowrap><font face=arial
    size="-1" color="white"><a href="http://help.sap.com/">Help
    </font></td><td width=5% nowrap></font></td> </tr></table>
    </td><td rowspan=2 width=122 height=61 valign=top><img src=
    "http://dceazar01:8010/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td>
    </tr><tr><td background="http://dceazar01:8010/sap/public/icman/img/graybar_tile.jpg" height="31">
     </td></tr>
    </table>
    <br><br>
    <table width=800>
    <tr><td width=50 nowrap>
    </td><td>
    <H2><b>500 Internal Server Error</b></H2><br><hr><br>Internal Server Error(-1)<br><br><hr>
    <table border="0">
    <tr><td>Error:</td><td>-1</td></tr>
    <tr><td>Version:</td><td>6040</td></tr>
    <tr><td>Component:</td><td>HTTP_PLG</td></tr>
    <tr><td>Date/Time:</td><td>Sun Jan  7 12:04:44 2007
    </td></tr>
    <tr><td>Module:</td><td>http_plg_mt.c</td></tr>
    <tr><td>Line:</td><td>3505</td></tr>
    <tr><td>Server:</td><td>dceazar01_SRD_10</td></tr>
    <tr><td>Detail:</td><td>No handler defined for this URL</td></tr>
    </table>
    <p></p>
    </td></tr></table>
    <table><tr><td width=50 nowrap></td>
    <td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">© 2001-2005, SAP AG</a></FONT></td></tr></table></SAP:AdditionalText><SAP:ApplicationFaultMessage namespace=""></SAP:ApplicationFaultMessage><SAP:Stack><b>HTTP response contains status code 500 with the description Internal Server Error
    Error when sending by HTTP (error code: 500, error text: Internal Server Error)</b></SAP:Stack><SAP:Retry>M</SAP:Retry></SAP:Error>
    please guide me..
    regards
    Ram

    hi friends..
    trace is like this...
    <?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 = 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><!-- ************************************ -->
    <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 = dcexi0602.aaaa.com:8000</Trace>
    <Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
    <Trace level="2" type="T">Remote address = 10.150.113.48</Trace>
    <Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace><!-- ************************************ -->
    <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>
    <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 = DGX</Trace>
    <Trace level="3" type="T">client = 100</Trace>
    <Trace level="3" type="T">language = E</Trace>
    <Trace level="3" type="T">user = XIAFUSERDGX</Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:42Z 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><!-- ************************************ -->
    <Trace level="1" type="T">Message-GUID = 6799BA809E4D11DBB72AF6C9E0007003</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><!-- ************************************ -->
    <Trace level="3" type="T">QOS = EO</Trace>
    <Trace level="3" type="T">Message-GUID = 6799BA809E4D11DBB72AF6C9E0007003</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 : XBTI0004</Trace>
    <Trace level="1" type="T">Generated prefixed queue name = XBTI0004</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 = 6799BA809E4D11DBB72AF6C9E0007003</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><!-- ************************************ -->
    <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="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><!-- ************************************ -->
    <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 = DGX</Trace>
    <Trace level="3" type="T">client = 100</Trace>
    <Trace level="3" type="T">language = E</Trace>
    <Trace level="3" type="T">user = XIAFUSERDGX</Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET  </Trace>
    <Trace level="1" type="T">----------------------------------------------------- </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></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">Corresponding internal pipeline SAP_CENTRAL</Trace>
    <Trace level="3" type="T"> </Trace>
    <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>
    <Trace level="3" type="T"> </Trace>
    <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>
    <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>
    <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>
    <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>
    <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>
    <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>
    <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>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z 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>
    <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>
    <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:  - SAP_ERP_azar_DEV </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">2007-01-07T12:48:43Z 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">2007-01-07T12:48:43Z 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>
    <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>
    <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)  SAP_ERP_azar_DEV InterfaceCollection </Trace>
    <Trace level="2" type="T">...valid InbIf without Condition: InterfaceCollection </Trace>
    <Trace level="2" type="T">Number of receiving Interfaces:1  </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z 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><!-- ************************************ -->
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z 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>
    <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>
    <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><!-- ************************************ -->
    <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 = XBTOE1__0000</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>
    <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><!-- ************************************ -->
    <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><!-- ************************************ -->
    <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 = DGX</Trace>
    <Trace level="3" type="T">client = 100</Trace>
    <Trace level="3" type="T">language = E</Trace>
    <Trace level="3" type="T">user = XIAFUSERDGX</Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET  </Trace>
    <Trace level="1" type="T">----------------------------------------------------- </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></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">Corresponding internal pipeline SAP_CENTRAL</Trace>
    <Trace level="3" type="T"> </Trace>
    <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>
    <Trace level="3" type="T"> </Trace>
    <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>
    <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>
    <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>
    <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>
    <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>
    <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>
    <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>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z 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">2007-01-07T12:48:43Z 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>
    <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>
    <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 is already determined in the interface determination </Trace>
    <Trace level="3" type="T">Object ID of Interface Mapping DA461E413F303668931A977B9D811191 </Trace>
    <Trace level="3" type="T">Version ID of Interface Mapping B2CF8EF067FF11DBA742D7830A967135 </Trace>
    <Trace level="1" type="T">Mapping-Object-Id:DA461E413F303668931A977B9D811191 </Trace>
    <Trace level="1" type="T">Mapping-SWCV:B2CF8EF067FF11DBA742D7830A967135 </Trace>
    <Trace level="1" type="T">Mapping-Step:1  </Trace>
    <Trace level="1" type="T">Mapping-Type:JAVA </Trace>
    <Trace level="1" type="T">Mapping-Program:com/sap/xi/tf/_MM_M_StockMov_To_SAP_ </Trace>
    <Trace level="3" type="T">Dynamic configuration is empty </Trace>
    <Trace level="3" type="T">Multi mapping required. </Trace>
    <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_M_StockMov_To_SAP_. </Trace>
    <Trace level="3" type="T">Load b2cf8ef0-67ff-11db-a742-d7830a967135, http://aaaa.com/xi/PROCESS/PPE/ERP_MES, -1, com/sap/xi/tf/_MM_M_StockMov_To_SAP_.class. </Trace>
    <Trace level="3" type="T">Search com/sap/xi/tf/_MM_M_StockMov_To_SAP_.class (http://aaaa.com/xi/PROCESS/PPE/ERP_MES, -1) in swcv b2cf8ef0-67ff-11db-a742-d7830a967135. </Trace>
    <Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_M_StockMov_To_SAP_ </Trace>
    <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_M_StockMov_To_SAP_ </Trace>
    <Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_M_StockMov_To_SAP_ completed. (executeStep() of com.sap.xi.tf._MM_M_StockMov_To_SAP_ </Trace>
    <Trace level="3" type="T">Message Type 1  Number of messages 1  </Trace>
    <Trace level="3" type="T">Dynamic configuration is empty </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z 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">2007-01-07T12:48:43Z 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>
    <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>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->
    <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">-Bs_MES_Stock_proxy </Trace>
    <Trace level="2" type="T">-SAP_ERP_azar_DEV </Trace>
    <Trace level="2" type="T">http://aaaa.com/xi/PROCESS/PPE/ERP_MES.MI_IN_S_StockMov </Trace>
    <Trace level="2" type="T">Channel found:  - SAP_ERP_azar_DEV - CC_IN_XI_Proxy </Trace>
    <Trace level="2" type="T">no header mapping defined </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z 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><!-- ************************************ -->
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"></Trace><!-- ************************************ -->
    <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>
    <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>
    <Trace level="3" type="T">Channel for Integration Engine: XI</Trace>
    <Trace level="3" type="T"> </Trace>
    <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  = IENGINE</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>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
    <Trace level="3" type="T">Channel for Integration Engine: XI</Trace>
    <Trace level="1" type="T">Sender: Header mapped to</Trace>
    <Trace level="1" type="T">Party = </Trace>
    <Trace level="1" type="T">Agency = </Trace>
    <Trace level="1" type="T">Scheme = </Trace>
    <Trace level="1" type="T">Service = Bs_MES_Stock_proxy</Trace>
    <Trace level="1" type="T">Receiver: Header mapped to</Trace>
    <Trace level="1" type="T">Party = </Trace>
    <Trace level="1" type="T">Agency = </Trace>
    <Trace level="1" type="T">Scheme = </Trace>
    <Trace level="1" type="T">Service = SAP_ERP_azar_DEV</Trace>
    <Trace level="1" type="T">Party denormalization: sender </Trace>
    <Trace level="1" type="T">Sender target scheme = </Trace>
    <Trace level="1" type="T">Sender target agency = </Trace>
    <Trace level="1" type="T">Sender party normalized = </Trace>
    <Trace level="1" type="T">Sender party external = </Trace>
    <Trace level="1" type="T">Party denormalization: receiver </Trace>
    <Trace level="1" type="T">Receiver target scheme = </Trace>
    <Trace level="1" type="T">Receiver target agency = </Trace>
    <Trace level="1" type="T">Receiver party normalized = </Trace>
    <Trace level="1" type="T">Receiver party external = </Trace>
    <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
    <Trace level="2" type="T">Addressing mode: url</Trace>
    <Trace level="3" type="T">Host = dceazar01</Trace>
    <Trace level="3" type="T">Port = 8010</Trace>
    <Trace level="3" type="T">Transport protocol = HTTP      1.0</Trace>
    <Trace level="3" type="T">Message protocol = </Trace>
    <Trace level="3" type="T">Path = sap/xi/engine?type=receiver</Trace>
    <Trace level="2" type="T">Auth mode: basicSAP</Trace>
    <Trace level="3" type="T">Conversion of language from char2 to char1 EN</Trace>
    <Trace level="3" type="T">User = asar</Trace>
    <Trace level="3" type="T">Client = 400</Trace>
    <Trace level="3" type="T">Language = E</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 SAP </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 = 500 </Trace>
    <Trace level="3" type="T">Deserializing message object... </Trace>
    <Trace level="3" type="System_Error">HTTP-client: error response= <html><head><title>SAP Web Application Server Error</title>
    <style type="text/css">
    body { font-family: arial, sans-serif;}
    </style>
    </head>
    <BODY text="#172972" link="#808080" vlink="#808080"
    alink="#8e236b" bgcolor=white  leftmargin="0" topmargin="0"
    marginheight="0" marginwidth="0">
    <table height="61" width="100%" border="0" cellspacing="0"
    cellpadding="0"><tr><td background="http://dceazar01:8010/sap/public/icman/img/bluebar_tile.gif"
    height="30"><table> <tr> <td width=5></td> <td width=20% nowrap><font face=arial size="-1" color=white>SAP Web Application Server
    </font></td><td width=75% align="right" nowrap><font face=arial
    size="-1" color="white"><a href="http://help.sap.com/">Help
    </font></td><td width=5% nowrap></font></td> </tr></table>
    </td><td rowspan=2 width=122 height=61 valign=top><img src=
    "http://dceazar01:8010/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td>
    </tr><tr><td background="http://dceazar01:8010/sap/public/icman/img/graybar_tile.jpg" height="31">
     </td></tr>
    </table>
    <br><br>
    <table width=800>
    <tr><td width=50 nowrap>
    </td><td>
    <H2><b>500 Internal Server Error</b></H2><br><hr><br>Internal Server Error(-1)<br><br><hr>
    <table border="0">
    <tr><td>Error:</td><td>-1</td></tr>
    <tr><td>Version:</td><td>6040</td></tr>
    <tr><td>Component:</td><td>HTTP_PLG</td></tr>
    <tr><td>Date/Time:</td><td>Sun Jan  7 13:48:43 2007
    </td></tr>
    <tr><td>Module:</td><td>http_plg_mt.c</td></tr>
    <tr><td>Line:</td><td>3505</td></tr>
    <tr><td>Server:</td><td>dceazar01_SRD_10</td></tr>
    <tr><td>Detail:</td><td>No handler defined for this URL</td></tr>
    </table>
    <p></p>
    </td></tr></table>
    <table><tr><td width=50 nowrap></td>
    <td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">© 2001-2005, SAP AG</a></FONT></td></tr></table></Trace>
    <Trace level="3" type="T">HTTP-client: closing...</Trace>
    </Trace>
    <Trace level="2" type="T">Switch back to normalized party (HTTP response)</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="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="2" type="T">Undo header mapping (HTTP response) </Trace>
    <Trace level="1" type="T">Sender: Header before undo of mapping</Trace>
    <Trace level="1" type="T">Party = </Trace>
    <Trace level="1" type="T">Agency = </Trace>
    <Trace level="1" type="T">Scheme = </Trace>
    <Trace level="1" type="T">Service = Bs_MES_Stock_proxy</Trace>
    <Trace level="1" type="T">Receiver: Header before undo of mapping</Trace>
    <Trace level="1" type="T">Party = </Trace>
    <Trace level="1" type="T">Agency = </Trace>
    <Trace level="1" type="T">Scheme = </Trace>
    <Trace level="1" type="T">Service = SAP_ERP_azar_DEV</Trace>
    <Trace level="2" type="T">Sender: Header after undo of mapping</Trace>
    <Trace level="2" type="T">Party = </Trace>
    <Trace level="2" type="T">Agency = </Trace>
    <Trace level="2" type="T">Scheme = </Trace>
    <Trace level="2" type="T">Service = Bs_MES_Stock_proxy</Trace>
    <Trace level="2" type="T">Receiver: Header before undo of mapping</Trace>
    <Trace level="2" type="T">Party = </Trace>
    <Trace level="2" type="T">Agency = </Trace>
    <Trace level="2" type="T">Scheme = </Trace>
    <Trace level="2" type="T">Service = SAP_ERP_azar_DEV</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><!-- ************************************ -->
    <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>
    please guide me ...
    regards
    Ram

  • Background job finished but Error sending data

    Dear all,
    report is running in my prod server . once this report completed sapuser get mail . when i check the job status it shows
    Job started
    Step 001 started (program GP4CF9U420G825I4P7DU8XY49WH, variant CUSTOMEROUTSTD, user ID S2K_BASIS)
    Spool request (number 0000012259) created without immediate output
    Error sending data (4)
    Job finished
    one more clarity i required
    this report should goes to 4 SAP users . how can i configure this report to 4 sapusers
    kindly suggest me

    > Step 001 started (program GP4CF9U420G825I4P7DU8XY49WH, variant CUSTOMEROUTSTD, user ID S2K_BASIS)
    > Spool request (number 0000012259) created without immediate output
    > Error sending data (4)
    I'd check SCOT/SOST for any errors. Also check the syslog (SM21).
    > this report should goes to 4 SAP users . how can i configure this report to 4 sapusers
    Create a distribution list (SAPoffice-Inbox - environment - distribution list) and enter that as addresse for the output.
    Markus

  • Error sending IDOC from JCO Client to PI AEX 7.3.1

    Hi All
    We have a requirement to send an IDOC from a non SAP System to our ECC via PI AEX :
    JCO.Client --> PI AEX --> SAP ECC
    At this time, we are testing this scenario with a JAVA Client with JCO Library (3.0.10).
    Destination to PI is OK
    Destination to our SAP ECC (for IDocRepository) is OK
    But by sending the IDOC to PI we are getting the following error, Exception is raised on the PI System and sent back to the JCO Client :
    com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: while trying to invoke the method java.lang.Object.hashCode() of an object loaded from local variable 'key' (raised by system <extern>|PiSystem)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:670)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.execute(MiddlewareJavaRfc.java:1881)
        at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:1120)
        at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:953)
        at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:1465)
        at com.sap.conn.jco.rt.AbapFunction.execute(AbapFunction.java:319)
        at com.sap.conn.idoc.jco.JCoIDoc.send(JCoIDoc.java:323)
        at com.sap.conn.idoc.jco.JCoIDoc.send(JCoIDoc.java:353)
        at sap_connector_examples.IDocClientExampleToJavaPO_pbs.main(IDocClientExampleToJavaPO_pbs.java:97)
    Caused by: RfcException: [<extern>|PiSystem]
        message: while trying to invoke the method java.lang.Object.hashCode() of an object loaded from local variable 'key'
        Return code: RFC_SYS_EXCEPTION(3)
        error group: 104
        key: RFC_ERROR_SYSTEM_FAILURE
    Exception raised by <extern>|PiSystem
    PI Destination:
    jco.destination.repository_destination=ABAP_AS_WITHOUT_POOL
    jco.client.gwhost=PiSystem
    jco.client.gwserv=sapgw01
    jco.client.tpname=XI_IDOC_DEFAULT_PID
    jco.client.type=E
    ECC Destination: (ABAP_AS_WITHOUT_POOL)
    jco.client.lang=en
    jco.client.client=100
    jco.client.passwd=****
    jco.client.user=User
    jco.client.sysnr=00
    jco.client.ashost=ECCSystem
    We have already set the PI VM System parameter  jco.allow_non_abap_partner to 1
    ECC User has S_RFC Rolle
    I will be thankful for any advise.
    Thank You
    Regards
    Stéphane

    Hi
    InboundRA (Resource Adapter) is green (Fully available).
    What do you mean by maintaining JCO RFC Destination in PI ?
    We have set the inboundRA Properties has follow :
    ProgramID : XI_IDOC_DEFAULT_PID
    DestinationName : XI_IDOC_DEFAULT_DESTINATION
    Local: true
    mutliRepository : ED1=XI_IDOC_DEFAULT_DESTINATION_ED1;ES4=XI_IDOC_DEFAULT_DESTINATION_ES4;MD1=XI_IDOC_DEFAULT_DESTINATION_MD1;ES1=XI_IDOC_DEFAULT_DESTINATION_ES1;PD1=XI_IDOC_DEFAULT_DESTINATION_PD1;
    GatewayServer and Service are pointing to our PI System
    BindingKey : PI_AAE_IDOC
    And for each Repository we created a destination in NWA pointing to the corresponding ECC System.
    (target host pointing to the ECC System and the Gateway host  pointing to the PI System)
    Our Installation isn't new but it is the first time we are configuring the System for this scenario:
    JCO.client --> PI AEX
    Regards
    Stéphane

  • SAP B1iP detected an error 404 Not found

    我根据Yatsea 写的Creating New Dashboard Packages for Sap Business One 8.8以及提供的sample一步一步的去做,到最后一步提示如下错误:
    SAP B1iP detected an error:
    Emitted HTTP-Code
    404-Not Found
    Internal Reason
    /com.sap.b1.dashboards/001sap0001.XXX_Top_10_BPs.Top_10_BPs/default.html [err004]
    Recommendation
    Check for the correctness of your activity or environment or ask your system-administrator for further help.
    tid
    10111016465218008162C0A8016D9A20
    Full Internal Error Message
    /com.sap.b1.dashboards/001sap0001.XXX_Top_10_BPs.Top_10_BPs/default.html [err004]
    这是什么原因啊?我折腾了一天了,还没弄好哦。。。。

    Hi Jay,
         我重新导入了,有看到event,是在Failure里面。
       Result Message是:no scenario step (vBIU) associated for this step for the incoming system (SysId)
         Msg是:
        <?xml version="1.0" encoding="utf-8" ?>
    - <Msg xmlns="urn:com.sap.b1i.vplatform:entity" MessageId="10111710462131508066C0A801672D97" BeginTimeStamp="20101117104621" recording="false" logmsg="0009" MessageLog="true">
    - <Header>
      <IPO Id="INB_HT_CALL_SYNC_XPT" tid="10111709282731508057C0A801674050" />
      <Sender Id="001sap0004" />
      </Header>
    - <Header>
      <IPO Id="INB_HT_CALL_SYNC_XPT" tid="10111709282731508057C0A801674050" />
      <Sender Id="001sap0004" />
      </Header>
    - <Body>
      <Payload Role="T" Type="Call" add="" />
    - <Payload Role="S">
      <io xmlns="urn:com.sap.b1i.bizprocessor:bizatoms" pltype="ure">==== data-length: 0 ====</io>
      </Payload>
      </Body>
    - <Body>
      <Payload Role="T" Type="Call" add="" />
    - <Payload Role="S">
      <io xmlns="urn:com.sap.b1i.bizprocessor:bizatoms" pltype="ure">==== data-length: 0 ====</io>
      </Payload>
      </Body>
      </Msg>
      为什么会失败呢?失败的原因是什么呢?怎么解决呢?
    我看了里面Warning的信息:
    An IPO-Execution profile cannot be given, as the necessary log-information is missing!
    Make sure to set in the config-file 'xcellerator.cfg' the log-level for the components
    'com.sap.b1i.bizprocessor' and 'com.sap.b1i.dblayer' to 'CONFIG' (restart B1iP afterwards).
    Then, enable detailed logging for the particular IPO-Step and re-execute the particular IPO-Step!
    所以我检查了我的xcelerator.cfg文件。
    Dolphin
    Edited by: Wu dolphin on Nov 17, 2010 3:52 AM
    Edited by: Wu dolphin on Nov 17, 2010 4:47 AM

  • Java proxy client with HTTP sender

    I have SP15. I have sender agreement with HTTP adapter for system A and Java Proxy Cleint that send message as system A.
    When I send message through Java proxy I see error:
    <i>SOAPFault received from Integration Server. ErrorCode/Category: XIServer/IN_BIND_WRONG_ADPT; Params: HTTP; AdditionalText:  ; ApplicationFaultMessage:  ; ErrorStack: Server agreement found belongs to adapter HTTP; current adapter is 'XI' </i>
    When I deleted sender agreement it worked.
    Could you explain this strange behavior? Is it a bug. Sender agrement for HTTP is necessary since SP16

    I have the same problem with SOAP and file adapter. I've posted this here already.
    XIServer/IN_BIND_WRONG_ADPT
    I have deleted the sender agreement for my soap adapter scenarios, because a sender agreement is not necessary (created by the wizard). After that the soap adapter scenarios work fine. But at scenarios with a sender file adapter you need a sender agreement.
    We had the following situation:
    XI Test, XI SP17, Basis SP16 --> IN_BIND_WRONG_ADPT problem
    XI QA, XI SP17, Basis SP14 --> okay
    XI Prod, XI SP15, Basis SP 16 --> okay
    We patched our XI QA to
    XI QA, XI SP17, Basis SP16
    After that we have the IN_BIND_WRONG_ADPT problem at our XI  QA system too.
    I started a SAPP OSS call two weeks ago but got no solution till now. They checked our systems some times but with no result.
    Our central SLD is on the XI Prod System. Perhaps there is a connection. But I don't want to patch my XI Prod system to SP 17, because it's the only system that works without errors.
    Message was edited by: Gil Ritter

  • SAP System Message: Syntx error or generation error in a screen

    dear sap basis gurus,
    i am currently having problems signing on to our DEV server. i get this error message:
    <SID>: SAP System Message
    Syntx error or generation error in a screen.
    it won't let me log on.
    there were no changes made on the server (i.e., profile parameters) lately. it was working really fine after our support package level upgrade about 5 months ago.
    have you encountered this problem before? please help me as there we have two imminent go-lives.
    thank you very much in advance.
    best regards,
    albert

    hello nick, ashok,
    thank you very much for your responses.
    i have already resolved this issue by just freeing up some space from our disks. not one of them was full though.
    i hope i would no longer encounter the error message.
    again, thank you.
    best regards,
    albert

  • Unable to open PWA in browser and MSP on application server in project server 2007. ERROR: Sending the Soap message failed or no recognizable response was received.

    Hi All,
    I am using project server 2007 and WSS 3.0. 
    I have been facing a strange issue for couple of days. I am unable to open PWA in browser and MS Project Pro on application server.
    Everything is correct whether it is URL or MS Project profile account on MSP.  This is strange because i can open same PWA/MSP from other computers (Database server / Client PCs) but not locally on server.
    When i try to connect to MSP on App server, i get the following errors in event viewer.
    Event Type: Error
    Event Source: MSSOAP
    Event ID: 16
    User: N/A
    Computer: APP-Server-Name
    Description:
    Soap error: Connection time out..
    Event Type: Error
    Event Source: MSSOAP
    Event Category: Client 
    Event ID: 16
    User: N/A
    Computer: APP-Server-Name
    Description:
    Soap error: An unanticipated error occurred during the processing of this request..
    Event Type: Error
    Event Source: MSSOAP
    Event Category: Client 
    Event ID: 16
    User: N/A
    Computer: APP-Server-Name
    Description: Soap error: Sending the Soap message failed or no recognizable response was received.
    Event Type: Error
    Event Source: MSSOAP
    Event Category: Client 
    Event ID: 16
    User: N/A
    Computer: APP-Server-Name
    Description:
    Soap error: Unspecified client error..
    One more issue i am facing and i guess that is related to above issue. The Issue is, when i am creating a new project, It's workspace gets created but doesn't get linked to the project and i can't link it manually because it already exists for the project.
    sandeep

    Hi Paul ,
    Thanks for reply. The project server URL was already added to the Trusted
    Sites/Local Intranet areas in IE. 
    sandeep

  • HealthCheck operation fails on mcsmgr.log and Error sending DAV request. HTTP code 600, status on Data transferservice.log

    Hi,
    I have a CAS, primary site and a DP.  On Site properties I have set client communication : HTTP or HTTPS  and PKI. on management point properties as well I have set Client communication as HTTPS PKI.
    1. On primary site Multicast_servicepoint status is "error": I checked the mcsmgr.log and found below details:
    Failed to send http request /SMS_MCS/.sms_mcs?op=healthcheck. Error 12030
    Call to HttpSendRequestSync failed for port 443 with 12030 error code.
    Health check operation failed, error code is 12030
    Health check operation failed, error code is 12030
    2. When I deploy any package to client it stuck in software center as "Downloading the information". no content has been getting copied.  I checked the log 'datatransferservice.log'  and found below error :
    "Successfully sent location services HTTPS failure message.
    Error sending DAV request. HTTP code 600, status ''
    GetDirectoryList_HTTP mapping original error 0x80072efe to 0x800704cf.
    GetDirectoryList_HTTP('https://myDPaddress.com:443/NOCERT_SMS_DP_SMSPKG$/CAS00028') failed with code 0x800704cf.
    Job {CFD64352-918B-4C1D-A9C4-9C52ABAC6524} reverted impersonation.
    Error retrieving manifest (0x800704cf).  Will attempt retry 1 in 30 seconds.
    Failed to send request to /NOCERT_SMS_DP_SMSPKG$/CAS00028 at host Mydpaddress, error 0x2efe
    [CCMHTTP] ERROR: URL=https://mydpaddress.com:443/NOCERT_SMS_DP_SMSPKG$/CAS00028, Port=443, Options=480, Code=12030, Text=ERROR_WINHTTP_CONNECTION_ERROR
    Raising event:
    instance of CCM_CcmHttp_Status
    ClientID = "GUID:41932A1A-ADDE-450F-8F16-22DC875D2E39";
    DateTime = "20141225182459.543000+000";
    HostName = "mydpaddress.comt";
    HRESULT = "0x80072efe";
    ProcessID = 7356;
    StatusCode = 600;
    ThreadID = 6936;
    Successfully sent location services HTTPS failure message.
    Error sending DAV request. HTTP code 600, status ''
    I think there is some issue with IIS configuration on site server or DP or on both. Please let me know a solution..
    Regards

    I have corrected the PKI certificate. still Issue not resolved.
    I checked further and found sms_mp_control_manager was stopped and was offline, Unable to communicate with component (error below)
    Unable to query the component.
    This is a child primary server. not on production yet.  Removing and adding MP will resolve the issue ? if yes what are the prerequesite you suggest. pls share any link .
    or any quick resolution you have ? please share...
    Log: mpmsi.lasterror
    Property(S): SMSCWSADSPATH = IIS://LocalHost/W3SVC/1
    Property(S): CCMSHAREMODE = 1
    MSI (s) (5C:EC) [08:22:19:157]: Note: 1: 1729 
    MSI (s) (5C:EC) [08:22:19:157]: Product: ConfigMgr Management Point -- Configuration failed.
    MSI (s) (5C:EC) [08:22:19:157]: Windows Installer reconfigured the product. Product Name: ConfigMgr Management Point. Product Version: 5.00.7804.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status:
    1603.
    MSI (s) (5C:EC) [08:22:19:368]: Deferring clean up of packages/files, if any exist
    MSI (s) (5C:EC) [08:22:19:368]: MainEngineThread is returning 1603
    MSI (s) (5C:B0) [08:22:19:372]: RESTART MANAGER: Session closed.
    MSI (s) (5C:B0) [08:22:19:372]: No System Restore sequence number for this installation.
    === Logging stopped: 12/26/2014  8:22:19 ===
    MSI (s) (5C:B0) [08:22:19:375]: User policy value 'DisableRollback' is 0
    MSI (s) (5C:B0) [08:22:19:375]: Machine policy value 'DisableRollback' is 0
    MSI (s) (5C:B0) [08:22:19:375]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (5C:B0) [08:22:19:375]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (5C:B0) [08:22:19:376]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (5C:B0) [08:22:19:376]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (5C:B0) [08:22:19:377]: Destroying RemoteAPI object.
    MSI (s) (5C:00) [08:22:19:377]: Custom Action Manager thread ending.
    MSI (c) (30:B0) [08:22:19:378]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (30:B0) [08:22:19:379]: MainEngineThread is returning 1603
    === Verbose logging stopped: 12/26/2014  8:22:19 ===

  • Fixing :there was an error sending mail"

    I am using Adobe Reader 9 and Acrobat 8 Pro on a Lenovo, Windows 7, 64bit machine. When I right-click pdf files from my directories, and select "send", the file attaches itself to a new e-mail (from Outlook) and I can send - no issues. However, if I am viewing an open pdf and I select the e-mail or send icon from the toolbar, I get an error message (first box just says "error", then second box says "there was an error sending mail". I have Googled this issue and, in turn checked my Windows settings for Outlook, etc. I see no issues. I have run Adobe updates - still doesn't work. Any ideas?
    Thanks, Wayland

    What I'm trying to say, that when I update my App there an error appears

  • Error: Sender agreement not found, lookup of binding via CPA-CACHE failed.

    Hi,
    I am doing an RFC to File Scenario in which RFC has to be triggered from CRM system. The TCP/IP connection and communication Channel are working fine. But when i trigger my RFC using the RFC destination following errors occur:
    1. The SYSTEM_FALIURE exception comes on CRM side.
    2. In adapter monitoring the following error comes on XI side:
           Error: Sender agreement not found, lookup of binding via CPA-CACHE failed for Adapter type RFC.
    I have also tried the scenario with RFC request as source message and also after J2EE cache refresh but the problem still persists. And one more thing my file adapter (In receiver communication channel) is not working means it is not started. And no message is coming in SXMB_MONI.
    Could anyone please help me to resolve this issue.
    Regards,
    Vinay Yadav

    Hi Aaron,
    I had the same error and your feedback solved my problem!
    Thank you sooo much!!!!
    Luciana

  • Proxy Generation internal error object not found.

    Hi
    We have BW-XI implementation .Recently an error has started popping up , while the checking the proxy in tcode sproxy.
    Error is - Proxy generation internal error , <message> not found, check failed . However when I double click on the proxy and do a check its fine and we are able to load data in BW successfully .
    Does any one have a clue on this and how important is this check on the first screen of sproxy ? Thanks in advance .

    Hi......Kapil,
    proxy's mainly based on msg interfaces.with out creating msg interface we can't do proxies.For this logon to IR & create data & msg types & then msg interfaces.
    after complition of this process.Under proxy generation screen u can see the  following details .......
    Ur data type,msg type,& ur interface...
    regards,
    Naresh.K

  • Error sending DAV request. HTTP code 500, status 'Internal Server Error'

    Hi All,
    I am getting the error On SCCM R2 Environment .. on the client machine we are getting the below issue and software center 
    is not showing any information..
    While checking on the client's DatatransferService.log.. i am getting the below issues..
    Successfully sent location services HTTP failure message.
    Error sending DAV request. HTTP code 500, status 'Internal Server Error'
    GetDirectoryList_HTTP('http://MachineName:80/SMS_DP_SMSPKG$/7ea0b105-5592-48cd-8b8e-81777537c34f') failed with code 0x87d0027e.
    i realize it because of Isapi filter issues.. can any one guide me to resolve the issues..
    KJSUBBU

    Hi,
    In addition, I recommend you check whether you have additional Authentication methods (like ASP.NET Impersonation) enabled. 
    Disable the authentication method and try again.
    Also, please review the link below, here is a article about troubleshoot ISAPI filter issue.
    Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 500.0 – Internal Server Error"
    http://support.microsoft.com/kb/942031
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

Maybe you are looking for