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

Similar Messages

File to Proxy Scenario Error

Hi Experts,
I am working on File To Proxy Scenario. I am getting the below Error: The Messages in SXMB_MONI are going to AUtomatically Restart Status. I see some Queues with RETRY Status in SMQ2. When i am testing from SPROXY, the Table is Updated with the Corresponding Values. But when i place the file in the ftp folder then i am getting this error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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>
Please check and do the needful .
Regards,
GIRIDHAR

Hi Giridhar,
The problem is with connection. Please check the below discussion
HTTP returns status is 500(Internal Server Error)
Problem in ABAP proxy........ | SCN
regards,
Harish

File to idoc ..error in sxmb_moni

Hi Xi Friends...
In my xml to idoc scenario...
file is picking..but in sxmb_moni it is showing as mapping error like
<b>No messages created from split mapping</b> ..
i copied the the payload from sxmb_moni and i tested in static message mapping..its converting successfully...
please guide me..
regards
ram

refer these links;
Split mapping created no messages - this has a solution, check if it can help you.
Message Split without BPM - Error

File to Proxy Scenario : Error in communication channel monitoring

Hi,
I have developed File to Proxy Scenario on PI 7.1 system and it is not working. I see the below error in communication channel monitoring.
u201CError: com.sap.engine.interfaces.messaging.api.exception.ConfigException: Some of the IS access information is not available. SLDAccess property may be set to true, but SLD is not available.u201D
File will be picked from the FTP server.
I have created File system in SLD of type "Third Party", Can this be the issue?
Please guide me on this.
Thanks,
Chandravadan

Hi!
Check if the tcode SLDCHECK is ok!
Check note #764176.
Also, refer to link below and execute each steps from the links there MANUALLY.
Wizard-Based Configuration:
http://help.sap.com/saphelp_nwpi71/helpdata/EN/45/2e4c1b16bb4aa8e10000000a11466f/frameset.htm
Regards,
Caio Cagnani

File to Proxy Scenari0, Error in ECC server Messages stucked in Queue

Hi All
we have created a file to proxy scenario in PI & when we are sending the data to Proxy, proxy is not getting executed in SAP ECC & we are getting the following error in out production ECC server & all the messages are getting s
No load could be found for transformation /1SAI/TXSA9475ABE3925030F71D9
could any one of you please help me in resolving this issue.
Thanks
Rinku Gangwani

Hi,
Are you activate the ICF services in ERP system? This issue must be done for the correct execution of proxy channel.
What type of program mapping are you using for the content transformation?
If you use a ABAP mapping program make sure to activate the program correctly.
Best regards
Ivá

ICM_HTTP_CONNECTION_FAILED error in file to proxy??

Hi
In my file to proxy,
i am maintaining one Http RFC destination..intest Connection i am getting 500 as status.
two TCP/IP destinations LCRSAPRFC and SAPSLDAPI.
i am maintaing values in SPROXSET table.
in SLDAPICUST also.
and in SXMB_ADM i configuerd Integration engine.
but i am getting error in sxmb_moni
SAP:P4></![CDATA[>
<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://dcexi0605.aaaa.com:8030/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://dcexi0605.aaaa.com:8030/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td> </tr><tr><td background="http://dcexi0605.aaaa.com:8030/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>404 Resource not found</b></H2><br><hr><br>Partner not reached<br><br><hr> <table border="0"> <tr><td>Error:</td><td>-20</td></tr> <tr><td>Version:</td><td>6040</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Wed Feb 28 12:28:10 2007 </td></tr> <tr><td>Module:</td><td>icxxconn_mt.c</td></tr> <tr><td>Line:</td><td>2121</td></tr> <tr><td>Server:</td><td>ciBGX30_BGX_30</td></tr> <tr><td>Detail:</td><td>Connection request from (42/31087/0) to host: dcesssss08.aaaa.biz, service: 8010 failed (NIECONN_REFUSED) AP-T42, U31087, 100 SOA_AAA, M2B-36-D-1787, 12:28:10, M0, W2, , 1/0</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>Error when receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)</b></SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
please guide me where i did mistake
regards
Ram

hi friends..
now i am getting HTTP_RESP_STATUS_CODE_NOT_OK HTTP response contains status code 403 with the description Forbidden Error when sending by HTTP (error code: 403, error text: Forbidden)
i maintaind in RZ10 the values.intially port is 8100 , now i changed it 8000
in sxmb_adm..
corresponding Integarion server:
http://hostname:8030/sap/xi/engine?type=entry
the same value is maintained in Sproxset table also
in SMICM -Services Http services port is 8000
please suggest me
regards
Ram

File Content Conversion Error in PI 7.1 (file to Proxy)

Hi
I am working on File to Proxy Scenario and I gave the File content conversion as below, File is picking up by the PI Server when I look at Communication Channel Monitoring, However when I open the Message ID in the CC monitoring it says as
404 Not Found
The requested resource does not exist.
and I do not see any message SXMB_MONI(Because the content is not converted), Can anyone give an idea how to debug this
Thanks
PR
Please find the details below which I gave in the content Conversion
Document Name : MT_TW_AK
Document NameSpace : http://aiwcd.com/Claims_Management(CM)_Rel2.0
RecordSet Name : FROISROIAcknowledgement
RecordSet Structure : Header,1,Record,*,Trailer,1
Recordset Sequence : Ascending
KeyField Name :TransactionSetID
Key Field Type : String (Case Sensitive)
IgnoreRecordsetName : true
Header.fieldNames :TransactionSetID,SenderID,ReceiverID,DateTransmissionsent,TimeTransmissionsent,OriginalTransmissionDate,OriginalTransmissionTime,TestProductionCode,InterchangeVersionID
Header.fieldFixedLengths: 3,25,25,8,6,8,6,1,5
Header.keyFieldValue : H
Record.fieldSeparator :
Record.fieldNames : TransactionSetID,RecordSequenceNumber,DateProcessed,TimeProcessed,InsurerFEIN,ClaimAdministratorPostalCode,ClaimAdministratorFein,AcknowledgementTransactionSetID,ApplicationAcknowledgmentCode,InsuredReportNumber,ClaimAdministratorClaimNumber,JuridictionClaimNumber,MaintenanceTypeCode,MaintenanceTypeCodeDate,RequestCode,FreeFormText,NumberofErrors,MaintenanceTypeCorrectionCode,MaintenanceTypeCorrectionCodeDate,JurisdictionBranchOfficeCode,ClaimAdministratorAlternatePostalCode,NumOfErrors
Record.fieldFixedLengths: 3,9,8,6,9,9,9,3,2,25,25,25,2,8,3,60,2,2,8,2,9,19
Record.keyFieldValue : A
Trailer.fieldNames:TransactionSetID,DetailRecordCount,TransactionCount
Trailer.fieldFixedLengths: 3,9,9
Trailer.keyFieldValue : T
ignoreRecordsetName: true

PR,
Can you check the error in sender communication channel?
Go to RWB ---> Component Monitoring ---> Adapter Engine ---> Communication cahnnel monitoring --> it displays new page. Then give your file sender communication cahnnel name. There you will definitely see some error.
The error what you are getting is a different to this one. Can you please check the error what I have given above path.
Regards,
---Satish

File To Proxy Error ICM HTTP CONNECTION FAILED

Dear All ,
Iam Doing File to Proxy Scenario.
XML File is picked by XI Adapter is Properly and if i go and Check in SXMB_MONI,
It is Showing Status is Scheduled for outbound processing and if i see in Que Status is stop with red symbal .If I Click on QueueID it is opening the inbound qRFC Monitoring ,there if click on Queue Name it is showing Status :SYSFAIL,If I Click on SYSFAIL it is Showing the XI Error CLIENT_RECIVE_FAILED.INTERNAL:Que Stop, If I Click on QueueName it is showing while Executing the Functiomodule SXMS_ASYNC_EXE It is having prob i thik showin Error Text :CLIENT_RECIVE_FAILED.INTERNAL:Que Stop,If I Click on Quename it is showing a program RSXMB_SELECT_MESSSAGES is Similar to our SXMB_MONI ,here it is showing the Status Falg Red ,If I Click on that message it is opening the pipeline steps , here while calling Adapter Showing red symbal giving the Error Message ICM_HTTP_CONNECTION_FAILED
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Please help me its urgent.
Regards
Kumar

hi
This is the problem relleated to the HTTP connections, since using the proxy theXML travels to the destination, on your receiveing system make sure HTTP service are active.
in R/3 run this report :SPROX_CHECK_HTTP_COMMUNICATION you will get the error then proceed with the below steps to fix it.
YOur HTTP seriveces on the R/3 have some problem.....
Goto SMICM>goto>servicess you should see the HTTP service running with the ABAP port entry, if this is up then check
SICF--->press f2 you should not have any proxy check there.....
if these are fine then problem is with the Sproxy configuration........

Error in SXMB_MONI -"HTTP_RESP_STATUS_CODE_NOT_OK

Hi all,
In a file to file to scenario, i'm getting this error in SXMB_MONI
Error - " HTTP_RESP_STATUS_CODE_NOT_OK"
503
Service Unavailable
Please provide me the exact solution
Thanks,
Younus

Hi younus,
this should solve ur purpose
INTERNAL.HTTP_RESP_STATUS_CODE_NOT_OK 503
Http* Errors in XI
503 service unavailable
XIServer error raised: 503 Service Unavailable with SOAP Adapter
regards
srinivas

Error in FILE 2 Proxy Scenario

Hi All,
I am doing File to Proxy Scenario i am getting following error
Could any one provide the solution for this.
*<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
*- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
<SAP:P1>ifmmessif</SAP:P1>
<SAP:P2>MI_Emp_Sender</SAP:P2>
<SAP:P3>Namespace</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message MI_Emp_Sender, request message, namespace )</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Thanks in Advance
Mahesh
</SAP:Error>
Edited by: Mahesh Reddy on Jul 10, 2008 12:47 PM

Hi Mahesh,
1) Use SPROXY transaction.
Menu-> Proxy -> Activate All.
2) check in the interface determination if u are using correct
inbound interface.
3) If this if fine....try deleting all proxy objects of the interface
and create new.
Regards,
Praveen K

File-XI-IDOC : error in sxmb_moni because of empty idoc

Hi !
I'm converting a CSV file to IDOC segments (CREMAS04).
XI uses a lookup table to convert CSV records to IDOC segments. It is normal that some records could not be converted. When I process a CSV file that has ALL non-convertable records, I get an error in sxmb_moni :
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>MSGGUID 99889D40A4D811DBAD4A0017A4510466: Tag found instead of tag IDOC BEGIN=</SAP:P1>
And the final payload is:
<?xml version="1.0" encoding="UTF-8" ?>
<CREMAS04 />
In the integration repository, the occurance of the complex type CREMAS04 is "1..1", I modified the xsd to minOccurs=0 , maxOccurs=1 , and imported it, but it keeps showing me "1..1"...
How do I deal with these case ?? I don't want error red flags in monitor because of empty idocs...
Thanks.

Hi Bhavesh !
Thanks !
The problem is that because of mapping rules, the value of my target fields is SUPPRESS, not "empty".
For example, I have a file with this records:
A
A
B
A
"B" records should fill an IDOC segment, "A" not.
If I receive a file with only "A" records, for example 48 "A" records...then the IDOC segment, now, is receiving 48 SUPPRESS values...then the mapWithDefault doesn't work because they are SUPPRESS and not EMPTY.
Any ideas?
Thanks,
Matias.

HTTP_RESP_STATUS_CODE_NOT_OK - Error in ABAP proxy

Dear all,
I work in a scenario in which we send data from the R/3 to XI using the ABAP proxies.
But the messages are not received in XI.
The messages are in error in SXMB_MONI of the R/3 system.
The error message we get in SXMB_MONI of the R/3 system is "HTTP_RESP_STATUS_CODE_NOT_OK"
<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>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3 />
<SAP:P4 />
Could anyone kindly suggest a solution to rectify this error?
Thanks.
Best Regards,
Thangesh

Hi,
>>401
1) Might cause due to insufficient right of the User ID
2)Try with this Login XIISUSER
3)Tcode SICF -> Default_host -> sap -> xi
( Check right password for the user id )
4) Check the RFC connection User Id..and it's settings.
This Might Help you
HTTP_RESP_STATUS_CODE_NOT_OK - 401 Unauthorized
HTTP_RESP_STATUS_CODE_NOT_OK 404 Error
HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
Regards
Agasthuri Doss

File 2 Proxy error

Hi All,
i am getting following error while doing the File to Proxy Scenario.
No implementing class registered for the interface
(ABAP interface, request message MI_Emp_Sender,
request message, namespace http://tcs.com/Demo)
How to resolve this error.
Plz, help in this concern.
With Regards,]
Mahesh

hi mahesh
It means that ,there is no ABAP proxy generated for that interface (transaction SPROXY)
Can you regenerate your proxy and activate the same again
You an check the Pipeline URL in SXMB_ADM -- >Integration Engine cofiguration.
PROXY problem
reward points if helpfull
regards
kummari

ABAP Proxy Outbound Error

hello everybody,
i have the next scenario ABAP Proxy->XI->RFC, the problem is that in the sender system I'm getting the next error in SXMB_MONI of sender system:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="401" p2="Unauthorized" p3="" p4="">HTTP.HTTP_STATUS_CODE_NEQ_OK</SAP:Code>
<SAP:Text language="EN">HTTP status code 401 : Unauthorized</SAP:Text>
</SAP:ErrorHeader>
the status is system error, can anyone help me with this error, cause messages are not aariving to Integration Server, thanks in advance.
Regards,
Julio Cesar

Hi Julio
Check Following Steps:
1:Have you insterted the correct URL of your Integration Server?
XMB.TargetURL=http://<host>:<ICM_Port>/sap/xi/engine?type=entry
2: Is the user and password correct?
XMB.User=XIAPPLUSER
XMB.Password=*****
3: Are the read permissions in the source directory correct?
file.sourceDir=/usr/sap/...
4: Be sure you use the ICM Port in my case 8000, e.g.
XMB.TargetURL=http://server:8000/sap/xi/engine?type=entry
If you use SLD information also include
XMD.SLDConfiguration=SLDaccessor in the file.
Check also that the XI user has the right profiles in the XI ABAP instance.
Thanks
Abhishek Mahajan
***Reward points if helpful*********

File to Proxy Scenarion

Hi,
All Iam doing File to Proxy Scenarion.
File is picked up by XI Properly and Pushing in to R/3 also Successful.When I checked in R/3 SXMB_MONI ,My Status is Scheduled and Green status.If I go and checked in to the Trace Is giving following.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<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=receiver</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = SED</Trace>
<Trace level="1" type="T">client = 110</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = CSYAM</Trace>
<Trace level="1" type="Timestamp">2007-10-09T02:15:06Z 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 = AB0B13E0760B11DCC45100118566337F</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0008</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0008</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface MI_APAR_Proxy*</Trace>
<Trace level="1" type="T">select interface namespace http://com.starhub/FICO-BILLING-APAR</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
</SAP:Trace>
Please help us,its urgent.
Regards
KUMAR

Hey kumar,
What you can do step by step is as follows:
1. Go to SMQ2 and ctivate/delete the queues, then re-run your scenario. If problem solved well and good.
2. If problem is not solved, then use tcode <b>SICF</b> -> F8 and check the default_host->sap--->XI. check if all the services are active or not. if active then it will be in pure black color. if not active then activate it and then your scenario. If problem solved well n good.
3. If problem is not solved yet, then use tcode <b>SM59</b> and test HTTP connectioin.
SM59 ---> open "HTTP connection to ABAP system" ---> double click on "INTEGRATION_DIRECTORY_HMI".
Now pree the connection test button and select the "Accept all further Cookies" check box and press "Yes". If test results are positive i.e. if there is no error then test your scenario and if you have problem please consult with your Basis persion.
I hope all above mention setps will resolve your problem.
Regards,
Sarvesh
*****Reward Points, if it helped you.

File to proxy ..HTTP_RESP_STATUS_CODE_NOT_OK error in sxmb_moni??

Similar Messages

Maybe you are looking for