Question Re: HTTP_RESP_STATUS_CODE_NOT_OK HTTP Response 404 in Technology Q&A

HTTP_RESP_STATUS_CODE_NOT_OK HTTP Response 404

Former Member — Mon, 03 Mar 2008 14:23:10 GMT

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"><a href="http://sap.com/xi/XI/System" TARGET="test_blank">http://sap.com/xi/XI/System</a></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.

Re: HTTP_RESP_STATUS_CODE_NOT_OK HTTP Response 404

Former Member — Mon, 03 Mar 2008 14:39:55 GMT

hi,

Check this blog for all HTTP error Codes

[https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4061] [original link is broken] [original link is broken] [original link is broken];

Reward points if useful

Regards,

Abhishek

Re: HTTP_RESP_STATUS_CODE_NOT_OK HTTP Response 404

agasthuri_doss — Mon, 03 Mar 2008 15:05:26 GMT

Hi,

Check that the port tcode - SMICM, Menu goto .... services and check the port number for HTTP. It should be HTTP port and your guess is right and check with Basis team

Regards

Agasthuri Doss

Re: HTTP_RESP_STATUS_CODE_NOT_OK HTTP Response 404

Former Member — Mon, 03 Mar 2008 15:33:38 GMT

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.

Re: HTTP_RESP_STATUS_CODE_NOT_OK HTTP Response 404

agasthuri_doss — Mon, 03 Mar 2008 18:02:51 GMT

Hi,

Go to Tcode - Sxmb_ifr then Go to Administration Tab > Exchange profile > Parameters > Run time Work environment bench > com.sap.aii.rwb.server.centralmonitoring.httpport > Check the value .

Regards

Agasthuri Doss

Re: HTTP_RESP_STATUS_CODE_NOT_OK HTTP Response 404

Former Member — Mon, 03 Mar 2008 22:30:28 GMT

Hi Valad,

Check the sender/inbound file adapter configuration. the XMB.TargetURL parameters generally refer to the j2ee port, which is in the 50000 not the SAP netweaver AS port 8000.

smicm->goto->HTTP SERVER->display data look at the j2ee HTTP port. it should be in the 50000.

thanks,

Re: HTTP_RESP_STATUS_CODE_NOT_OK HTTP Response 404

Former Member — Tue, 04 Mar 2008 09:25:21 GMT

Hello Agasthuri, I checked mentioned parameter it 50000. Should it be the same as HTTP port from transaction SMICM?

Re: HTTP_RESP_STATUS_CODE_NOT_OK HTTP Response 404

nisarkhan_n — Tue, 04 Mar 2008 10:58:07 GMT

Yes it should be same as the HTTP port not J2ee port.

Re: HTTP_RESP_STATUS_CODE_NOT_OK HTTP Response 404

Former Member — Wed, 12 Mar 2008 07:50:23 GMT

Everybody thanks for the answers. Unfortunately I does not have a chance to check whether it works.

I will post my reply as soon as I check this.

Regards Vlad

Re: HTTP_RESP_STATUS_CODE_NOT_OK HTTP Response 404

Former Member — Fri, 14 Mar 2008 12:03:24 GMT

Excellent, it works, finally. Everybody thanks for your response.

Our expectations was right the port in exchange profile was incorrect. It should be set to ABAP HTTP port from SMICM transaction.