HTTP response contains status code 404 ...

Hello,
My system sceanrio is:
R/3 -> idoc -> XI-1 -> xi adapter -> XI-2 -> idoc -> R/3.
When the message sent, I get a red flag in SXMB_MONI transaction of "XI-1" system :
'HTTP response contains status code 404 with the
description Not Found'
Here is the SOAP adapter of the Call Adapter:
=============================================
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"> 404 &nbsp Not Found</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">SAP J2EE Engine/6.40 </td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> The requested resource does not exist. <table><tr><td valign="top"> Details:</td><td valign="top"><PRE>Go to <A HREF="/" target="_parent">main page</A> of this application!</PRE></td></tr></table> </body> </html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 404 with the description Not Found XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2005-04-12T06:52:37Z" wasRead="false">
<SAP:Engine type="IS">is.50.weaver</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">IDoc</SAP:Adapter>
<SAP:MessageId>550806B7-DEED-FF42-96B1-6F33852373F1</SAP:MessageId>
<SAP:Info>MATMAS.0000000000214059:20050412085231</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2005-04-12T06:52:37Z" wasRead="false">
<SAP:Engine type="IS">is.50.weaver</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>550806B7-DEED-FF42-96B1-6F33852373F1</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:IDocInbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>200</SAP:MANDT>
<SAP:DOCREL>46C</SAP:DOCREL>
<SAP:DOCNUM>0000000000214059</SAP:DOCNUM>
<SAP:DIRECT>1</SAP:DIRECT>
<SAP:IDOCTYP>MATMAS04</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>MATMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPDEV</SAP:SNDPOR>
<SAP:SNDPRN>LOGDEV200</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>XI-TEST</SAP:RCVPOR>
<SAP:RCVPRN>LOGXID700</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL>20050412085231</SAP:SERIAL>
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS>30</SAP:STATUS>
<SAP:OUTMOD>2</SAP:OUTMOD>
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>2005-04-12</SAP:CREDAT>
<SAP:CRETIM>08:52:31</SAP:CRETIM>
<SAP:ARCKEY />
</SAP:IDocInbound>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20050412</SAP:Date>
<SAP:Time>085237</SAP:Time>
<SAP:Host>weaver</SAP:Host>
<SAP:SystemId>XID</SAP:SystemId>
<SAP:SystemNr>50</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>MSSQL</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>014</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>ANNA</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>002</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
<SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
<SAP:QIdInternal>XBTO3___0000</SAP:QIdInternal>
<SAP:CommitActor>A</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="700">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">DF010AB7129C425B7035011D</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID">DF013D07020C425B70300B0A</SAP:EOReferenceInbound>
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>16517</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>0</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>16517</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>16527</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>IDOC</SAP:AdapterInbound>
<SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
<SAP:RandomNumber>71</SAP:RandomNumber>
<SAP:AckStatus>071</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.471</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.471</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.471</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.642</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.642</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.658</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.658</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.658</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.658</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.674</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.674</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.814</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.814</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.939</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.939</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.971</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.971</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SAP:OutboundBindingEntry version="30">
<SAP:OutboundBindingObjectId>B0E25658819A3AE888B48BAD55537C5E</SAP:OutboundBindingObjectId>
<SAP:FromPartyName />
<SAP:FromServiceName>DEV</SAP:FromServiceName>
<SAP:ToPartyName />
<SAP:ToServiceName>XIT</SAP:ToServiceName>
<SAP:ToInterfaceName>MATMAS.MATMAS04</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">XIT</SAP:ServiceName>
<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">GeneratedReceiverChannel_XI</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>anonymous</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>host</SAP:Name>
<SAP:Value>victor</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 />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonLanguage</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonPassword</SAP:Name>
<SAP:Value isPassword="true" encryption="hw">AQ==</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonUser</SAP:Name>
<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>56000</SAP:Value>
</SAP:Attribute>
</SAP:AdapterTypeData>
</SAP:ChannelAttributes>
</SAP:ChannelEntry>
</SAP:OutboundBindingEntry>
</SAP:OutboundBinding>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPDEV</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</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 = XID</Trace>
<Trace level="1" type="T">client = 700</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = ANNA</Trace>
<Trace level="1" type="Timestamp">2005-04-12T06:52:37Z 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 = 550806B7DEEDFF4296B16F33852373F1</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0010</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0010</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 700</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = ANNA</Trace>
<Trace level="1" type="Timestamp">2005-04-12T06:52:37Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO3___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 level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 700</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = ANNA</Trace>
<Trace level="1" type="Timestamp">2005-04-12T06:52:37Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="1" type="T">Interface Mapping urn:XI_to_XI_Simulation MATMAS04_MATMAS04</Trace>
<Trace level="1" type="T">*** APPLICATION TRACE TRUNCATED (for more details see LogViewer)***</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="1" type="T">processing the outbound binding</Trace>
<Trace level="1" type="T">search outbound bindings</Trace>
<Trace level="1" type="T">outbound bindings found</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<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 = DEV</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 = XIT</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="1" type="System_Error">HTTP-client: error response= <!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

Hi,
The 'Communication Channel' in Integration Builder was not configured right in the 'Service Number' field. There was a J2EE port instead of HTTP port.
J2EE port: 5<instance number>00
HTTP port: 80<instance number>
Good luck to everyone,
Dimitry

Similar Messages

Demo Error - HTTP response contains status code 404

Dear all,
While configuring the first demo on XI 3.0, I encountered the following errors when executing the scenario. The scenario is "Configuring Integration Scenarios for proxy-to-proxy communication" - Checking flight seat availability.
<?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="1">
<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"> 404 &nbsp Not Found</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">SAP J2EE Engine/6.40 </td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> The requested resource does not exist. <table><tr><td valign="top"> Details:</td><td valign="top"><PRE>Go to <A HREF="/" target="_parent">main page</A> of this application!</PRE></td></tr></table> </body> </html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 404 with the description Not Found XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Any pointers on this is greatly appreciated!!
Thanks,
Cyanna

Hi Michal,
Thanks for your response! I followed the instruction on question 17, and recheck my configuration of the integration engines (for client 105/106/107 as stated in the SAp demo), and change the 'Corresponding Inte. Server" back to the format "dest://<RFC destination for inte. server>". I had that initially, and decided to try using the entire http path (http://<local_host:J2EE port>/sap/xi/engine/?type=entry). Neither of them worked.
Do I need to restart or reactivate any components after I changed the corresponding integration server value after the configuration?
Since the above did not work, so I went back to the possible root cause (Integration Server RFC destination). I have set up the integration server RFC destination in client 100, with the following parameters:
Under Technical Settings:
Host: <local_host>
path prefix: /sap/xi/engine/?type=entry
service no.: 5<instance>00
Under Logon/Security:
Logon Precedure: chose Basic Authentication
Client: 100
Login ID : XIAPPLUSER
Afterwards, I did the "Test Connection", and it returns the 404 error.
In addition, on the application systems side (in the demo, the case will be client 105/106/107), I have ensured the business systems are set to "application system".
Any help is greatly appreciated!
Thanks much!
Regards,
Cyanna

HTTP response contains status code 415 with the description Unsupported

Hi All,
While transferring the data from SRM to CCM , We are getting following error,
HTTP response contains status code 415 with the description Unsupported Media Type Error while sending by HTTP (error code: 415, error text: Unsupported Media Type
Where need to check on this?
Thanks ,
NR

415 Unsupported Media Type
The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.

HTTP response contains status code 503

Hi All,
Im working on File to JDBC scenario using MsAccess.My file is been picked by XI from the sender folder (im using NFS at the sender side), but it is not inserting the data in the table which i have created on the server.
When i do SXI_MONI , i'm getting a error in call adapter "HTTP response contains status code 503 with the description Service Unavailable Error while sending by HTTP (error code: 503, error text: Service Unavailable)".
Plz do help me to solve it.
Thanks,
Suma

Hi,
503 Service unavailable
this is because of the server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
you can go for the possible solution as mentioned below:
Because of J2EE application com.sap.aii.af.ms.app not active
1. Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine.
2. The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
3. Refer SAP Note 803145,807000,791655
4. In Visual Admin, check if all the required services are running and start them, else restart the Java Stack in the XI server.
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi /people/vinoth.murugaiyan/blog/2007/08/06/how-to-the-change-the-application-stopped-message
http://help.sap.com/saphelp_nw04/helpdata/en/64/351941edd5ef23e10000000a155106/frameset.htm
thanq
krishna

ABAP Proxy HTTP response contains status code 401

We have a client ABAP proxy running in a program successfully in our development system. Today I transported this to our Test system. When I tested, there were no messages in the adapter engine pipeline.
One of my colleagues discovered that when running SXMB_MONI on the Application system (_not_ the XI system), the XML queue there shows the message with an error, the error being:
HTTP response contains status code 401 with the description Unauthorized
I have looked at quite a few posts here with this error; the PIAPPLUSER is not locked, Integration engine is configured the same way in both Development and Test, but I cannot figure out why this is happening.
Any assistance more than welcome!
BR,
Tony.

hi,
Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
If the error is in Adapter Engine
then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
May be wrong password for user XIISUSER
May be wrong password for user XIAFUSER
for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message
Thanks
Swarup

SRM SUS PO response:HTTP response contains status code 401

Hi,
While sending the PO response from SUS to mm am getting the error as below in SUS :
SAP:Stack>HTTP response contains status code 401 with the description Unauthorized
Authorization error while sending by HTTP (error code: 401, error text: Unauthorized)
Please advise.
Thanks,
Venky

Hi,
Is this the error you see when you click on "Send" button from POResponse? Or, does it happen when SUS is trying to send the XML message through PI/XI?
SG

HTTP_RESP_STATUS_CODE_NOT_OK HTTP response contains status code 500 with th

hello friend,
I have developed a proxy to JDBC synchronous scenario.
My scenario works like this.
i run an abap program which calls a client proxy,
the proxy fetches the data from database table and returns the data in the ABAP program.
My program is working fine but there is a small problem.
when i run the report for the first time, it gives me an exception while calling proxy
HTTP_RESP_STATUS_CODE_NOT_OK HTTP response contains status code 500 with the description Timeout
and when i run the report for the second time with same variant it works fine.
i can see the exception mostly in the morning when i run the report for the first time
please help me to find the solution of this problem.
thanks
kannu.

1. Increase the proctimeout in smicm as per note - 824554
2. Application threads in the J2EE engine might have got consumed in high load situations.
Increase the count of application threads in config tool at location Config Tool -> cluster-data ->
<configuration template> -> <instance-ID> -> managers -> ApplicationThreadManager ->
MaxThreadCount
3. Increase the parameter ServletInputStreamTimeout from 180000 to 1728000000.
Steps for setting this parameter:
a. If you have configured ICM to forward requests to the J2EE dispatcher then apply Note
1048692. If the problem is not resolved, then apply section b.
b. The request bytes are reaching the Engine too slowly
i. Start the configtool in <J2EE>/configtool directory
ii. Browse the tree in the left pane
cluster-data -> Global server configuration -> services -> http
iii. Press the ServletInputStreamTimeout key in the keylist on the right
iv. Change the value of the "Value" field at the bottom of the right pane to the
preferred one (in milliseconds).
-1 means there is no timeout - that is unless the full request comes into a single
chunk, an error will be thrown
180000 means the Engine would wait for 3 minutes for any byte to be entered in
the stream.
1728000000 means the Engine would wait for 20 days for any byte to be entered
in the stream
v. Press the "Set" button in the top-right corner
vi. Select from the menu File -> Apply and confirm all popups.
vii. Restart the Engine for changes to take effect

HTTP response contains status code 403 with the description Forbidden

Hello all,
I have configured a simple scenario like this:
File ftp Adapter -> XI -> File ftp Adapter
I activate the communication channel to start the message processing. Then I am able to see my messages in transaction SXMB_MONI in the XI Integration server but I get the error message mentioned in the subject of this thread.
When I look at the message processing details I got the following informtion in Call Adapter -> SOAP Header -> 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">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
 <SAP:P1>403 </SAP:P1>
 <SAP:P2>Forbidden</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;403 &amp;nbsp Forbidden&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;You are not authorized to view the requested resource.&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 403 with the description Forbidden
 XML tag Envelope missing in SOAP message header (SAP XI Extension)
</SAP:Stack>
 <SAP:Retry>M</SAP:Retry>
</SAP:Error>
Does anyone have a hint for me how to solve this issue?
Thanks in advance
Fabian

Hi,
This error may be because of Inactive Services in internet communication framework-
Go to SICF transaction and activate the services. Have a look into SAP note-517484
SO because of huge message this may be the reason.
Hope this helps,
Regards,
Moorthy

HTTP response contains status code 401 - Unauthorized

Hi all,
When executing any scenario , i am getting the following error.Before i executed successfully all the scenarios.
<?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>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"> 401 &nbsp Unauthorized</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">SAP J2EE Engine/6.40 </td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"> Access Denied.</td> </tr> <tr bgcolor="#FFFFFF"> <td align="left" valign="top" height="48"> Details:</td> <td align="left" valign="top" height="48"><pre> No details available</pre></td> </tr> </body> </html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 401 with the description Unauthorized XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
please suggest me abt the problem ?
Thanks & Regards,
sekhar.

Sekhar,
what user id you are using ? did you generate the roles ? What SP level you are on ? Did you upgrade it recently ?
I am not Siva....
regards
Shravan

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

Error in XIDemo: HTTP response contains status code 401 with the descriptio

Hi Gurus
I try to configure the XI DEMO, in the fase of "Check Flight Seat Availability" the system show the next Error:
Error Information
Unable to check flight availability.
Error Type: XI system error
Error Details: HTTP response contains status code 401 with the description Unauthorized
I check the pasword and it is ok!!
Any idea for this issue?
Thanks and regards

Hello
- Check that the required users are available on all clients involved in the scenario.
- Are the users PIAFUSER/PIISUSER locked
- Generate the roles and do a Mass Comparison for SAP_XI, SAP_SLD and SAP_BC_AI_LANDSCAPE_DB_RFC (your Basis admin will know how to do this).
- Double check all necessary configurations e.g. in the application system -> sxmb_admin -> Integration Engine Configuration ensure you are using the format DEST://<RFC destination name>
Regards
Mark

HTTP response contains status code 401 with the description Unauthorized

Hi,
I have an IDOC-XML mapping,when the IDOC is sucessfully passed on to the XI but in XI I encounter an errror
"HTTP response contains status code 401 with the description Unauthorized".Could somebody let me know what
could be the reson for this error.
Regards,
Arun

Dear Arun,
1) This might cause due to wrong permissions.
2)Try with this Login XIISUSER
3)Tcode SICF -> Default_host -> sap -> xi
( Check right password for the user id )
Regards
Agasthuri Doss

HTTP response contains status code 401 with the description Unauthorized Er

Hi All,
I am getting the below error, i have reset the password and username also but i am not getting where exactly it is failing out.

<?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>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>Enter User Name and Password</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 401 with the description Unauthorized Error when sending by HTTP (error code: 401, error text: Unauthorized)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Can anyone have the idea how can i check it out...??
Thanks in advance.

I have changed every password and username from XIAPPLUSER to XIAPPLTEST, but still in MONI--->oubound binding ..,, i am getting the logon user as the XIAPPLUSER... I check the perticular communication channel it is maintained XIAPPLTEST but still i am getting XIAPPLUSER.....
Do i have to refresh somewhere.
Can anyone have the idea is there anywhere else it is maintained..
================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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>041B892AC87B38A4AE46D4E443C88E55</SAP:OutboundBindingObjectId>
<SAP:FromPartyName />
<SAP:FromServiceName>BS_PSEWC</SAP:FromServiceName>
<SAP:ToPartyName />
<SAP:ToServiceName>BS_SAPRP1</SAP:ToServiceName>
<SAP:ToInterfaceName>sub_MeterReading</SAP:ToInterfaceName>
<SAP:ToInterfaceNamespace>urn://WCM_SR3_02/SAP/Meterreading</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">BS_SAPRP1</SAP:ServiceName>
<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">CCO_Proxy_WCM_MeterReading</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">2.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>drprd-db1</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>httpDestination</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonClient</SAP:Name>
<SAP:Value>300</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonLanguage</SAP:Name>
<SAP:Value>E</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>XIAPPLUSER</SAP:Value> </SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>path</SAP:Name>
<SAP:Value>/sap/xi/engine?type=receiver</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>port</SAP:Name>
<SAP:Value>8001</SAP:Value>
</SAP:Attribute>
</SAP:AdapterTypeData>
</SAP:ChannelAttributes>
</SAP:ChannelEntry>
</SAP:OutboundBindingEntry>
</SAP:OutboundBinding>

HTTP response contains status code 503 with the description

<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 503 with the description
Service Unavailable Error when sending by HTTP (error code: 503, error
text: Service Unavailable)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Please advice. Initially we thought the J2EE services were unavailable . But now even when the services are running we still have the same issue when there is a http call from an external application to XI . The message get posted but there is an error on the response back to the external application.
Even the contract which was supposed to be created in ERP from the external application did not get created.
Please advice.
Thanks,
Nivedita

Hi Nivedita,
503 means Service Unavailable
just check whether you cn ping the HTTP server host and port is open.
if not then consult the vedor and make both open first.
Also if you want to restart the java engine
then run T-code SMICM
Then go to administration then JAVA restart soft.
it will help you.
Regards,
Sumit Gupta

Error in file-file scenario: HTTP response contains status code 503

Hi folks,
I've encountered the foll error in file-file scenario:
Testing file-file scenario (followed the blog: https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/flatFILETOFLATFILE&)
Initially i was hving problems with recvr comm channel, which are now resolved. File is sent successfully but not recvd. I tried to modify the scenario above and change the file type to 'Text' but still got the same error.
I've checked SICF -->default_host/xi/engine , we dont maintain logon data there. when i test the default_host/xi/engine service, it resolves into an ip addr as follows:
http://<hostname>.<domain.com>:8001/sap/xi/engine?sap-client=<clientNo>
(Also, we hv a BW system running on the same server ,which uses a fully qualified domain, while we dont which is why we get the above domain. Im not sure if there are any issues with that.)
and we get the foll error:
Error Code 10060: Connection timeout
If i remove the domain manually, im prompted for userid/pwd and get the foll result:
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header />
- <SOAP:Body>
- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Client</faultcode>
<faultstring>Pipeline specified in URL attribute (type) not existing</faultstring>
<faultactor>http://sap.com/xi/XI/Message/30</faultactor>
- <detail>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">URL_PIPELINE_NOT_FOUND</SAP:Code>
<SAP:P1>/sap/xi/engine?sap-client=<clientNo></SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Pipeline ID , which is expected as value of attribute "type" in the URL, does not exist in the Integration Engine (URL = /sap/xi/engine?sap-client=811)</SAP:Stack>
</SAP:Error>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
also, we dont hv any overload issues as this is dev env and not many of us are using the xi server. Would really appreciate if any of you can share your inputs on how to resolve this. Thanks!!
cheers
Prachi

Hi ,
Look in to this for all errors
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
Refer SAP Note 803145,807000,791655
Award Points if found usefull.

HTTP response contains status code 404 ...

Similar Messages

Maybe you are looking for