INTERNAL" HTTP_RESP_STATUS_CODE_NOT_OK

Hi experts,
I am getting the error when i am posting IDOC to XI .
INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK
<?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>401</SAP:P1>
  <SAP:P2>Unauthorized</SAP:P2>
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Error Report</title> <style> td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active </style> </head> <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="4" color="#666666"><b>  401 &nbsp Unauthorized</b></font></td> </tr> <tr bgcolor="#3F73A3"> <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td> <td height="23"><img width=1 height=1 border=0 alt=""></td> <td align="right" height="23"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SAP J2EE Engine/7.00 </b></font></td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <br><br><br><br><br><br> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><b>  Authentication did not succeed.</b></font></td> </tr> <tr bgcolor="#FFFFFF"> <td align="left" valign="top" height="48"><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><b>  Details:</b></font></td> <td align="left" valign="top" height="48"><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><pre>  No details available</pre></font></td> </tr> </body> </html></SAP:AdditionalText>
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack>HTTP response contains status code 401 with the description Unauthorized Authorization error while sending by HTTP (error code: 401, error text: Unauthorized)</SAP:Stack>
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error>
Points will be awarded

Hi,
You can restart the J2EE Engine from transaction SMICM:
SMICM --> Administration --> J2EE-Server --> Send Hardshutdown or Softshutdown --> with restart
The below blog will resolve your problem of error code 401
How do you activate ABAP Proxies?
Refer Similar discussion
HTTP_RESP_STATUS_CODE_NOT_OK 503
INTERNAL.HTTP_RESP_STATUS_CODE_NOT_OK  503
HTTP_RESP_STATUS_CODE_NOT_OK
503 service unavailable
XIServer error raised: 503 Service Unavailable with SOAP Adapter
Http* Errors in XI
Thanks
Swarup
Edited by: Swarup Sawant on Aug 22, 2008 5:56 AM
Edited by: Swarup Sawant on Aug 22, 2008 5:57 AM

Similar Messages

  • IDOC---JDBC scenario error: "INTERNAL" HTTP_RESP_STATUS_CODE_NOT_OK

    i have a IDOC-XI--JDBC   scenario,
    the scenario fails at  the Call Adpater Pipeline step............giving following error:
    <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:Stack>HTTP response contains status code 401 with the description Unauthorized Authorization error when sending using HTTP (error code: 401, error text: Unauthorized)</SAP:Stack>
    pls help me.....
    Message was edited by:
            sudeep dhar

    but this error occurs after few message pass successfully.....
    means at an interval this error happens...then again few messgae pass successfully,
    This is the error which i get in MONI:
    ERROR_CATEGORY: INTERNAL
    ERROR_ID: HTTP_RESP_STATUS_CODE_NOT_OK
    and in the pipeline step i can see the error:
    <?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>401</SAP:P1>
      <SAP:P2>Unauthorized</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      </SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP response contains status code 401 with the description Unauthorized Authorization error when sending using HTTP (error code: 401, error text: Unauthorized)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

  • INTERNAL.HTTP_RESP_STATUS_CODE_NOT_OK  503

    Hi,
    We are facing an unusual error in XI.
    All our scenaros are showing same error.
    <SAP:Error>
    <SAP:Category>XIServer</SAP:Category>
    <SAP:Code>INTERNAL.HTTP_RESP_STATUS_CODE_NOT_OK
    </SAP:Code>
    <SAP:P1>503 </SAP:P1>
    <SAP:P2>Service Unavailable</SAP:P2>
    Some service is unavailable ??
    Can any one help.
    Thanks in Advance
    Chemmanz

    Hi Chemmanz,
    Check out these threads..
    Error in Call Adapter (IDOC->XI->FILE)
    XI Server Malfunction:Error in Receiver Adapter
    Hope they are useful!
    cheers ,
    Prashanth

  • INTERNAL.HTTP_RESP_STATUS_CODE_NOT_OK HTTP response contains status code 50

    Hi Gurus,
    I am getting error message "INTERNAL.HTTP_RESP_STATUS_CODE_NOT_OK HTTP response contains status code 500 with the description Timeout" when I call a proxy to retrieve data from external database (oracle) through XI (Synchronous Call). This proxy works fine if the data size is limited to 120 MB but terminates with above message if data size is larger may be > 130 MB but some time it works as well with this data size.
    Me & our basis team are working hard to fine out the issue but still could not succeeded. we have applied the OSS Note 807000  but still we are getting the error message. To make it more clear I am sending SQL Query to Reciever (Oracle) from SAP through ABAP proxies.
    If I check the status of messages in "Monitor for processed XML messages" the message has status icon which says "Log version" I am new in XI Please help me to solve the issue.

    hey...try increasing the synchronous timeout parameter. I think the default is 180 secs.
    I would suggest you look at redesigning the the interface  to pull the data in smaller pieces...120 Mb is really big...Pi gives max throughput at around 5 mb...
    Dont worry about the log version....It just persisted in the system when a job is still running... try looking at the same message after a while...it would have changed its stsatus.
    Arvind R

  • XMB_MONI which is the PI log says: INTERNAL" HTTP_RESP_STATUS_CODE_NOT_OK

    Bom dia! Hoje é nosso primeiro dia e estamos com problema de comunicação com a SEFAZ SP.
    Alguém já passou por isso?
    Grata,Fabiana

    Bom dia Pessoal,
    No dia de hoje é provável que vários time outs acontecem em virtude dos diversos GoLives em andamento.
    Isto deverá acontecer até as secretarias "acomodarem" a nova quantidade de clientes que está entrando em produção HOJE.
    Minha sugestão para reduzir o número de problemas é "fazer menos lotes":
    - Coloque o número de notas por lote = 50
    - Aumente o tempo de fechamento de lote (primeiro parm de segundos) para que sejam gerados menos lotes. (Sem valor fixo, mas tente colocar o maior número possível de notas por lote). Acompanha na /xnfe/batsta campo QTDENFE
    - Aumente também o tempo de consulta.
    Sei que isto pode ser horrível para o negócio, porém é uma situação necessária justamente para diminuir o impacto no negócio.
    Atenciosamente,
    Fernando Da Ró

  • 500 Internal Server Error in FiletoFile Scenario

    Hi All,
    Here we are doing FiletoFile Scenario but not on our Central Instance we are using LocalPlainJ2SE Adapters for both sender and receiever so we configured PlainJ2SEFile Adapters in both ends.In the ID of XI i configured th *XI recievr adapter* and *haven't configured any sender adapter or sender agreements.*
    *I did only RecievrAgreements,Recvr determination,InterfaceDetermination*.
    But
    When we test the scenario file is getting pickedp by the PlainJ2SE file Adapter and also sent to the XI (IS) but we are getting an error in the SXMB_MONI saying that
    *<?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: java.lang.NullPointerException</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText><html> <head> <title>Transport Service Error</title> </head> <body> <h1>HTTP/1.0 500</h1> <h3>internal server error: java.lang.NullPointerException</h3> </body> </html></SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP response contains status code 500 with the description internal server error: java.lang.NullPointerException Error while sending by HTTP (error code: 500, error text: internal server error: java.lang.NullPointerException)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Kindly give me some suggestions ??
    Thanks,
    Kalyan.

    >
    Kalyan chakravarthy p wrote:
    In the ID of XI i configured th XI recievr adapter and haven't configured any sender adapter or sender agreements.
    >
    > I did only RecievrAgreements,Recvr determination,InterfaceDetermination.
    Why didn't you configure Sender Adapter and Sender Agreement ?
    I am asking this since, the sender file adapter type determine the payload of the message based on their configuration. The information about the fields of the message header is determined from the corresponding sender agreement for the communication channel. Also the information from the sender agreement is used to construct the address header of the message.Moreover information from the adapter configuration in the sender channel is required for successful inbound processing.
    Is it still possible to process message from a file without going for  file adapter and SA ??

  • HTTP_RESP_STATUS_CODE_NOT_OK 404 Not Found

    Since moving from SP9 to SP12, all of our communication channels using a receiver file adapter get an HTTP error. One specific scenario is we read a file from UNIX (this works) and then remap and write a file back to the same directory (this gets the HTTP error).
    receiver adapter config is as follows:
    Adapter type = File
    Receiver
    Transport Protocol = File System (NFS)
    Message Protocol = File Content Conversion
    Adapter Engine = Integration Server
    Target Directory = /sap_int/XI_railmax
    File Name Scheme = new_sapack.txt
    A sender agreement has been created (and worked prior to the upgrade to SP12)
    Main Trace log:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
      <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
      <SAP:MessageId>A8363CC0-0FF2-11DA-BB1B-0003BA9CEFBD</SAP:MessageId>
      <SAP:TimeSent>2005-08-18T14:16:23Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Service>NXY_BS_KLEINSBX</SAP:Service>
      <SAP:Interface namespace="http://nexeninc.com/kleinschmidt/sap/BSSDRT076C_BOL_Ack">MI_BOL_RemapFromFile</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>NXY_BS_KLEINSBX</SAP:Service>
      <SAP:Interface namespace="http://nexeninc.com/kleinschmidt/sap/BSSDRT076C_BOL_Ack">MI_BOL_RemapToFile</SAP:Interface>
      </SAP:Receiver>
      <SAP:Interface namespace="http://nexeninc.com/kleinschmidt/sap/BSSDRT076C_BOL_Ack">MI_BOL_RemapToFile</SAP:Interface>
      </SAP:Main>
    Error:
    <?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>404</SAP:P1>
      <SAP:P2>Not Found</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Error Report</title> <style> td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active </style> </head> <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="4" color="#666666"><b>  404 &nbsp Not Found</b></font></td> </tr> <tr bgcolor="#3F73A3"> <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td> <td height="23"><img width=1 height=1 border=0 alt=""></td> <td align="right" height="23"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SAP J2EE Engine/6.40 </b></font></td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <br><br><br><br><br><br> <p><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><b>  The request can&#39;t be processed.</b></font></p> <p><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><table><tr><td valign="top"><b> Details:</b></td><td valign="top"><PRE>Requested resource &#40; MessagingSystem/servlet/MessagingServlet &#41; not found.</PRE></font></td></tr></table></font></p> </body> </html></SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP response contains status code 404 with the description Not Found XML tag Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    NOTE - this is only an issue when writing a FILE.  IDOC's inbound and outbound still work, the JDBC adapter still works, reading a file still works....just a problem with a 'receiver' File Adapter....any ideas?
    thanks /Dave

    Thankyou all for the quick responses:
    Sudhir - the parameters for the file conversion worked prior to our moving to SP12, but i tried chnaging the protocol to just 'file' anyways - same error
    Saravana-had a look at the OSS note - seems unrelated
    Michal - checked with our basis person, he has already redeployed the adapter framework and SDA files...i checked the service for the HTTP RFC dest, and it is in the format 5<instance>00, but when i change it to 80<instance> and run a 'test connection', it comes up with the 404 error.  Looked in the ICM and according to the display of the HTTP server the port is 52800 just as it is in the service of the rfc dest. So, i guess i am still stuck, and getting some Basis time here is proving difficult (i do not have access to the J2EE tools) -

  • HTTP_RESP_STATUS_CODE_NOT_OK HTTP Response 404

    Hello experts.
    I'm facing the following problem with XI IDoc to IDoc scenario.
    The problem is that XML messages appear in SXMB_MONI transaction with an error status, the status is
    HTTP_RESP_STATUS_CODE_NOT_OK.
    The error looks as following:
    <?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>404</SAP:P1>
         <SAP:P2>Not Found</SAP:P2>
         <SAP:P3 />
         <SAP:P4 />
         <SAP:AdditionalText>..{some text here} ..</SAP:AdditionalText>
         <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP response contains status code 404 with the description Not Found Error when  sending by HTTP (error code: 404, error text: Not Found)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    I have an assumption that the problem is in the HTTP port of requested URL. because of the following:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!--  Call Adapter   -->
    <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SAP:OutboundBindingEntry version="30">
    <SAP:OutboundBindingObjectId>06720EBBEDD533F3ABBD5CAEC853280E</SAP:OutboundBindingObjectId>
      <SAP:FromPartyName />
      <SAP:FromServiceName>NW0</SAP:FromServiceName>
      <SAP:ToPartyName />
      <SAP:ToServiceName>SXI</SAP:ToServiceName>
      <SAP:ToInterfaceName>ZULIST.ZULIST</SAP:ToInterfaceName>
      <SAP:ToInterfaceNamespace>urn:sap-com:document:sap:idoc:messages</SAP:ToInterfaceNamespace>
      <SAP:OutboundBindingAttributes>
      <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      </SAP:OutboundBindingAttributes>
      <SAP:HeaderMapping>
      <SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      </SAP:HeaderMapping>
      <SAP:ChannelEntry version="30">
      <SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">SXI</SAP:ServiceName>
      <SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">IDOC</SAP:ChannelName>
      <SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">XI</SAP:AdapterName>
      <SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
      <SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">3B787A8035C111D6BBE0EFE50A1145A5</SAP:AdapterSWCV>
      <SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType>
      <SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">XI</SAP:MessageProtocol>
      <SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">3.0</SAP:MessageProtocolVersion>
      <SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">HTTP</SAP:TransportProtocol>
      <SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">1.0</SAP:TransportProtocolVersion>
      <SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
      <SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:Attribute>
      <SAP:Name>addressingMode</SAP:Name>
      <SAP:Value>url</SAP:Value>
      </SAP:Attribute>
      <SAP:Attribute>
      <SAP:Name>authenticationModeBasicAnon</SAP:Name>
      <SAP:Value>basicSAP</SAP:Value>
      </SAP:Attribute>
      <SAP:Attribute>
      <SAP:Name>host</SAP:Name>
      <SAP:Value>drobnitsa</SAP:Value>
      </SAP:Attribute>
      <SAP:Attribute>
      <SAP:Name>httpDestination</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
      <SAP:Attribute>
      <SAP:Name>isMessageSecurity</SAP:Name>
      <SAP:Value>0</SAP:Value>
      </SAP:Attribute>
      <SAP:Attribute>
      <SAP:Name>logonClient</SAP:Name>
      <SAP:Value>000</SAP:Value>
      </SAP:Attribute>
      <SAP:Attribute>
      <SAP:Name>logonLanguage</SAP:Name>
      <SAP:Value>EN</SAP:Value>
      </SAP:Attribute>
      <SAP:Attribute>
      <SAP:Name>logonPassword</SAP:Name>
      <SAP:Value isPassword="true" />
      </SAP:Attribute>
      <SAP:Attribute>
      <SAP:Name>logonUser</SAP:Name>
      <SAP:Value>XISUPER</SAP:Value>
      </SAP:Attribute>
      <SAP:Attribute>
      <SAP:Name>passHopList</SAP:Name>
      <SAP:Value>1</SAP:Value>
      </SAP:Attribute>
      <SAP:Attribute>
      <SAP:Name>path</SAP:Name>
      <SAP:Value>*/sap/xi/engine?type=entry*</SAP:Value>
      </SAP:Attribute>
      <SAP:Attribute>
      <SAP:Name>port</SAP:Name>
      <SAP:Value> 50000 </SAP:Value>
      </SAP:Attribute>
      </SAP:AdapterTypeData>
      </SAP:ChannelAttributes>
      </SAP:ChannelEntry>
      </SAP:OutboundBindingEntry>
      </SAP:OutboundBinding>
    If I am no mistaken
      <SAP:Attribute>
      <SAP:Name>port</SAP:Name>
      <SAP:Value> 50000 </SAP:Value>
      </SAP:Attribute>
    this attribute is setting the port of requested URL, it is 50000, but it should be, I guess, 8000.

    Thank you for your answers I had already checked this and I'am sure that the port should be 8000.
    Where did this port number should be specified?
    Unfortinatally I did not have any basis men around me, I did installation and post-installtion check by myself, I have rechecked all post-installation activities but found nothing wrong.
    Please guide me.

  • 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

  • Problem in HTTP Request HTTP_RESP_STATUS_CODE_NOT_OK

    Hai Gurus,
          I am sending request from HTTP --> XI --> ABAP Proxy (Inbound). Its working fine when i execute proxy manually in tcode "sproxy". When do the same with HTTP Client it is throwing the following error.
    <?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="1">
      <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:P4 />
    My proxy does the work of uploading the files to Document Storage System KPro using standard BAPI's. I have used SAPFTP and SAPHTTP dlls in client machine's system32 folder (Which will help in downloading the document from client windows OS machine to SAP GUI AIX based machine).
    Still facing the same problem which will throw error HTTP_RESP_STATUS_CODE_NOT_OK with error code 500.
    Any help is highly appreciated.
    Regards,
    Pushparaju Bollapalli.

    Also Check these Foloowing ;
    - URL for the receiver is like this:
    http://<host>:<port>/sap/xi/engine?type=receiver .The XI 2.0 differs from XI 3.0 in this.
    -path in the receiver communication channel
    The path has to be defined as:
    /sap/xi/engine?type=entry for XI 3.0
    /sap/xi/engine?type=receiver for XI 2.0
    Regards
    Aashish Sinha
    PS : Reward points if Helpful

  • 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

  • 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

  • Posting XML using FILE adapter returns "HTTP_RESP_STATUS_CODE_NOT_OK"

    Hi,
    I am trying do very simple demo which reads a simple XML message from a ftp server and post that message directly to the same ftp server using FILE adapter.
    So, I add my xml message like this:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns:TxMessage xmlns:ns="http://bsa.sisl.com">
      <Name>Bibinu</Name>
      <Address>Kalyan</Address>
    </ns:TxMessage>
    but I get a error message back from the Integration Server as:
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <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 />
      <SAP:AdditionalText>&lt;!DOCTYPE HTML PUBLIC &quot;-//W3C//DTD HTML 4.0 Transitional//EN&quot;&gt; &lt;html&gt; &lt;head&gt; &lt;title&gt;Error Report&lt;/title&gt; &lt;style&gt; td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active &lt;/style&gt; &lt;/head&gt; &lt;body marginwidth=&quot;0&quot; marginheight=&quot;0&quot; leftmargin=&quot;0&quot; topmargin=&quot;0&quot; rightmargin=&quot;0&quot;&gt; &lt;table width=&quot;100%&quot; cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; align=&quot;left&quot; height=&quot;75&quot;&gt; &lt;tr bgcolor=&quot;#FFFFFF&quot;&gt; &lt;td align=&quot;left&quot; colspan=&quot;2&quot; height=&quot;48&quot;&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;4&quot; color=&quot;#666666&quot;&gt;&lt;b&gt;&amp;nbsp;&amp;nbsp;401 &amp;nbsp Unauthorized&lt;/b&gt;&lt;/font&gt;&lt;/td&gt; &lt;/tr&gt; &lt;tr bgcolor=&quot;#3F73A3&quot;&gt; &lt;td height=&quot;23&quot; width=&quot;84&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt; &lt;td height=&quot;23&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt; &lt;td align=&quot;right&quot; height=&quot;23&quot;&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;2&quot; color=&quot;#FFFFFF&quot;&gt;&lt;b&gt;SAP J2EE Engine/6.40&amp;nbsp;&lt;/b&gt;&lt;/font&gt;&lt;/td&gt; &lt;/tr&gt; &lt;tr bgcolor=&quot;#9DCDFD&quot;&gt; &lt;td height=&quot;4&quot; colspan=&quot;3&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt; &lt;/tr&gt; &lt;/table&gt; &lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt; &lt;p&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;3&quot; color=&quot;#000000&quot;&gt;&lt;b&gt;&amp;nbsp;&amp;nbsp;User is locked.&lt;/b&gt;&lt;/font&gt;&lt;/p&gt; &lt;p&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;2&quot; color=&quot;#000000&quot;&gt;&lt;table&gt;&lt;tr&gt;&lt;td valign=&quot;top&quot;&gt;&lt;b&gt;&amp;nbsp;Details:&lt;/b&gt;&lt;/td&gt;&lt;td valign=&quot;top&quot;&gt;&lt;PRE&gt;No details available&lt;/PRE&gt;&lt;/font&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;/font&gt;&lt;/p&gt; &lt;/body&gt; &lt;/html&gt;</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP response contains status code 401 with the description Unauthorized XML tag Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Seems like I am missing the Envelope. What does the Envelope supposed to look like or should contain so that the scenario should work?
    Thanks !

    Did you resolve the problem?? I have the same problem, and there's no informatin about it.
    Thanks!!

  • HTTP_RESP_STATUS_CODE_NOT_OK

    Hi All,
    When I place any source file for processing, the message ends with the below error in MONI.
    <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
      <SAP:P1>401</SAP:P1>
      <SAP:P2>Unauthorized</SAP:P2>
    <SAP:Stack>HTTP response contains status code 401 with the description Unauthorized Authorization error while sending by HTTP (error code: 401, error text: Unauthorized)</SAP:Stack>
    Earlier all went fine, but recently the server was down for sometime and then restarted all services. Since then this problem is occurring.
    I have gone through similar kind of threads and as per the suggestion from those threads, have gone throughrestarting the J2EE server. But still have the same problem. Please anybody help me to resolve this issue.
    Thank you

    Hi Bhanu ,
    SAP J2EE Engine returns HTTP response with status code 500 when many parallel users are trying to login to one application. One or several
    requests may fail with HTTP response code 500 during the load scenario. In such cases, when the error happens, the following
    exception must be present in the default trace of the j2ee engine .
    java.lang.NullPointerException
    at
    com.sap.engine.services.security.login.LoginContextFactory.initializeLog
    inContextmp;#40;LoginContextFactory.java:180mp;#41;
    at
    com.sap.engine.services.security.login.FastLoginContext.loginmp;#40;Fast
    LoginContext.java:127mp;#41;
    at
    com.sap.engine.services.servlets_jsp.server.runtime.context.SessionServl
    etContext.doLoginmp;#40;SessionServletContext.java:619mp;#41;
    at
    If this error happens in XI load scenarios, this trace is visible in the
    additional information of the failed message.
    Reason and Prerequisites
    Reason: The authentication stack for the corresponding application is
    not initialized properly.
    check SAP Note - 822211 .
    there is no harm in refreshing the cache also .
    Regards,

  • I got "500 Internal Server Error " as Response in HTTP Client Prog

    In my Java Server Proxy the following are the configurations that I followed right from SLD: Please help me where I went wrong:
    In SLD->Business Landscape:
    Web As Java,
    ->Technical System: Web As Java.
    created Product and Software Component version accordingly.
    In IR->created Data types and Message Types of same Data type. 
      In Message Interface created Inbound synchronous--specified both input and output message there
      In Message Mapping-> selected source and target message types and done the mapping
      In Interface Mapping->Selected source and target interfaces->read interfaces; In request tab->selected source msg and selected mapping program of type Fatal Error: com.sap.engine.lib.xml.parser.Parser</SAP:P3><SAP:Stack>Während des Anwendungs-Mappings com/sap/xi/tf/_Folder_MM_ wurde eine com.sap.aii.utilxi.misc.api.BaseRuntimeException geworfen: Fatal Error: com.sap.engine.lib.xml.parser.Parser.</SAP:Stack></SAP:Error>
    =========================
    Thanks a lot

    Hi I got this as result when my Pyload is like what you said: <ns0:Foldername_MT xmlns:ns0="http://jps.com">
    <name>
    <XISystemhost>\<xyzdir>
    </name>
    </ns0:Foldername_MT>
    ===================
    and for that I got:
    Result:
    http-Status:  500 Internal Server Error
    Payload:
    <SAP:Error><SAP:Category>XIServer</SAP:Category><SAP:Code>INTERNAL.HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code><SAP:P1>503 </SAP:P1><SAP:P2>Service Unavailable</SAP:P2><SAP:AdditionalText>&lt;!DOCTYPE HTML PUBLIC &quot;-//W3C//DTD HTML 4.0 Transitional//EN&quot;&gt;
    &lt;html&gt;
    &lt;head&gt;
         &lt;title&gt;Error Report&lt;/title&gt;
    &lt;style&gt;
    td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}
    A:link
    A:visited
    A:active
    &lt;/style&gt;
    &lt;/head&gt;
    &lt;body marginwidth=&quot;0&quot; marginheight=&quot;0&quot; leftmargin=&quot;0&quot; topmargin=&quot;0&quot; rightmargin=&quot;0&quot;&gt;
    &lt;table width=&quot;100%&quot; cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; align=&quot;left&quot; height=&quot;75&quot;&gt;
    &lt;tr bgcolor=&quot;#FFFFFF&quot;&gt;
        &lt;td align=&quot;left&quot; colspan=&quot;2&quot; height=&quot;48&quot;&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;4&quot; color=&quot;#666666&quot;&gt;&lt;b&gt;&amp;nbsp;&amp;nbsp;503 &amp;nbsp Service Unavailable&lt;/b&gt;&lt;/font&gt;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr bgcolor=&quot;#3F73A3&quot;&gt;
        &lt;td height=&quot;23&quot; width=&quot;84&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt;
        &lt;td height=&quot;23&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt;
        &lt;td align=&quot;right&quot; height=&quot;23&quot;&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;2&quot; color=&quot;#FFFFFF&quot;&gt;&lt;b&gt;SAP J2EE Engine/6.40&amp;nbsp;&lt;/b&gt;&lt;/font&gt;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr bgcolor=&quot;#9DCDFD&quot;&gt;
        &lt;td height=&quot;4&quot; colspan=&quot;3&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;/table&gt;
    &lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;
    &lt;table width=&quot;100%&quot; cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; align=&quot;left&quot; height=&quot;75&quot;&gt;
    &lt;tr bgcolor=&quot;#FFFFFF&quot;&gt;
        &lt;td align=&quot;left&quot; colspan=&quot;2&quot; height=&quot;48&quot;&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;3&quot; color=&quot;#000000&quot;&gt;&lt;b&gt;&amp;nbsp;&amp;nbsp;The requested application, JPR, is currently unavailable.&lt;/b&gt;&lt;/font&gt;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr bgcolor=&quot;#FFFFFF&quot;&gt;
        &lt;td align=&quot;left&quot; valign=&quot;top&quot; height=&quot;48&quot;&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;2&quot; color=&quot;#000000&quot;&gt;&lt;b&gt;&amp;nbsp;&amp;nbsp;Details:&lt;/b&gt;&lt;/font&gt;&lt;/td&gt;
        &lt;td align=&quot;left&quot; valign=&quot;top&quot; height=&quot;48&quot;&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;3&quot; color=&quot;#000000&quot;&gt;&lt;pre&gt;&amp;nbsp;&amp;nbsp;No details available&lt;/pre&gt;&lt;/font&gt;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;/body&gt;
    &lt;/html&gt;
    </SAP:AdditionalText><SAP:Stack>In der HTTP-Antwort liegt der Status-Code 503 mit der Beschreibung Service Unavailable vor</SAP:Stack></SAP:Error>
    =========================================
    What is that? Can u help me!!!
    Thanks

Maybe you are looking for

  • Reading barcodes

    Hi all, I have generated a barcode using barcode4j API. I want to read the encoded data from the generated barcode using Java. Plz explain the entire process how to read the data from the barcode using Java. Any help is highly appreciated. Thanx, Har

  • Procedure/batch file to export data from sql to excel(predefined path)

    Hi, I have countries, sites, states tables (total 3) in database (i have user id and password to connect to this database). every week i need to extract data from these tables into excel files and i need to save those in shared drive for team use. Cu

  • How to find Exits in Function Module & BAPI

    Hi,   How to find exits in Function Module & BAPI. Thanks In advance

  • How to call WEB Service From SAP 4.6 c

    Hi Friend, How to call WEB Service From SAP 4.6 c Report Thanks in advance.

  • Global application module settings

    Is there a better way than having to explicitly do the following (for example) <% myAppMod.useApplicationModule().getSession().setLocale(new java.util.Locale("en", "AU")); %> <% myAppMod.useApplicationModule().getTransaction().setBundledExceptionMode