HTTP Client : Code 110 reason

hi,
when i try to send a IDOC to XI to HTTP Receiver.
The flag shows red in the SXMB_MONI and the error is HTTP Client : code 110 reason message.
I am using a HTTP adapter for a HTTPS url as a receiver.
If i test the xml from a WFETCH i get a response saying no cXML Sent but there is cXML that i am adding in the Header body.
I have not used HTTP Client.
Any tips.
Thanks,
Tirumal

Hi Tirumal,
you were going correct man ...
The 400 error that you are getting can be because of :
The verb used in the request is invalid.
The requested URL is invalid.
The requested header name is invalid.
The requested hostname is invalid.
The request contains an invalid carriage return and/or line feed as a terminator.
The request contains an invalid content length header or invalid entity chunk length.
The cumulative length of the headers in the request is longer than the maximum allowed.
The header field in the request is too long.
The request header is too long.
Check on these lines and see if your problem is solved.
Rgds
joel

Similar Messages

HTTP Receiver Adapter - HTTP client code 110 reason error when sending

Hi,
I am getting the following error when using the HTTP adapter as a receiver to perform an HTTP Post in a destination system :
<?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>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client code 110 reason</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Does anyone know what causes this error and more importantly how to trace it ?
Cheers
Colin.

hi Colin,
Check in SMICM if your HTTP service is running. Also in RFC destination one of the parameter (SSL client Certificate) might be wrong which could also cause this problem.
Also check this thread:-
XI Error when upgraded to SP14 (Error Code 110) CLIENT_RECEIVE_FAILED
Have a look into this SAP Note - 897583
Regards.
Praveen

Error in scenario "FILE to HTTP(with SSL)" - HTTP client code 110 reason.

Hi friends,
Our scenario is as follows:
We are trying to send XML file from our SAP-XI to external tool "COMMunix XC" (a multi-protocol EDI platform tool).
We have configured " FILE TO HTTP(with SSL)" scenario (trying to connect HTTPS/port)
1. We have created RFC destination of type G and refered the same RFC in Communication channel (Adapter type: HTTP)
2. We have send the SSL Server certificate to other party and ensure that they have imported at thier end.
3. We have included the certificates from other party in our SAP XI STRUST under SSL Client (Standard) node.
4. We have tried " CONNECTION TEST " in the RFC destination created in type G (in STEP 1) and it shows the GREEN TICK at bottom, no other message nor any error message
When we trigger the communication we recieve the error: HTTP client code 110 reason in SXMB_MONI.
Please let us know if we have missed out some step.
What does error message indicate,
Regards,
Rehan

Hi Rehan,
I see that the PROCTIMEOUT was already at a very high value.
Does this occur for messages of a particularly large size? If yes, you could increase the parameter
icm/HTTP/max_request_size_KB = 2097152
This would need to be done in the sender/receiver system as well as XI.
Otherwise you could try reproducing the issue and checking the dev_icm log in the work directory, or go to SMICM -> Goto -> Display trace file
check for errors like NIECONN_REFUSED or "no service for protocol HTTPS" which can often be related to this type of issue.
Kind regards,
Sarah

HTTP client code 402 reason ICM_HTTP_TIMEOUT

Hi Experts,
My Scenario is RFC-XI-HTTP syncronous and was working fine for some period.
after that when am sending request to XI it is processinig successfully till technical touting and in call adapter step under response am finding error as <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
             <SAP:P1>402</SAP:P1>
             <SAP:P2>ICM_HTTP_TIMEOUT</SAP:P2>
             <SAP:Stack>HTTP client code 402 reason ICM_HTTP_TIMEOUT</SAP:Stack>
             <SAP:Retry>N</SAP:Retry>
and i gone through relevent SAP notes and configured the parameters in ICM monotor and Visual admin for the same.
and still am getting the same error as mentioned in above.
Could you please any one help me out in this regard ?
Many thanks,
Siva

Hi Raj,
Thanks for your reply,
I already gone through the mentioned link nd followed the steps.
still am facing the same problem for this scenario. and some other scenarios of same type RFC XIHTTP are working fine.
and could you please let me know is it throughs the error that i mentioned in case when the Target system wont give response to XI ?
why because am finding the Time out error that mentioned under Response message.
Kindly help in this regard.
thanks
siva

HTTP client code 405 reason ICM_HTTP_INTERNAL_ERROR

Hi Experts,
Getting the below error in the RWB could any one look at this and help me out.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlnsAP="_http://sap.com/xi/XI/Message/30" xmlnsOAP="_http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP1>405</SAP1>
<SAP2>ICM_HTTP_INTERNAL_ERROR</SAP2>
<SAP3 />
<SAP4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAPtack>HTTP client code 405 reason ICM_HTTP_INTERNAL_ERROR</SAPtack>
<SAP:Retry>N</SAP>
Thanks
Venkat Anil

Hi Venkat,
Just check eith your basis team had they restatred the j2ee engine proprely or not ,are all the nodes working fine in visual admin.
Regards

HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED

Hi
when using an https receiver adapter in PI 7.11 I get the error message
"HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED".
The server I am trying to connect to is running and I have activated all services under sap -> xi in SICF.
The ICM log shows this:
WARNING => Connection request from (38/18489/0) to host: https, service: 80 failed (NIEHOST_UNKNOWN)
AP-T38, U18489, 001 ALE_K01, , 15:45:37, M0, W9,     , 1/0 [icxxconn.c 2222]
On the PI Integration Server the outbound queue (smq1) is empty.
However, the message seems to be sitting in the inbound tRFC queue (smq2)
Function Module: SXMS_ASYNC_EXEC
Queue Name: XBTO6___0002
Status Text: Transaction Recorded
I also get the error message in the inbound tRFC queue:
"XI Error ATTRIBUTE_CLIENT.PLAINHTTP_ADAPTER: Queue"
It does not help to chose "save LUW" on the erroneous message in the queue.
In the http receiver adapter I entered these values:
Addressing Type: URL Address
Target Host: https://biztalk.lm-gruppen.dk
Service Number: 443
Path: /******/BTSHTTPReceive.dll
What should I do to make it work?
Mikael

Hi,
In the http receiver adapter I entered these values:
Addressing Type: URL Address
Target Host: https://biztalk.lm-gruppen.dk
Service Number: 443
Path: /******/BTSHTTPReceive.dll
If you want to enable HTTPs, you should use HTTP to RFC destination using SM59 (for the RFC destination) and STRUST (for the SSL authentication). Also, do not specify the http:// or https:// parameter in your target host. The correct parameters should be:
Target Host: biztalk.lm-gruppen.dk
Service Number: 443
Path: /******/BTSHTTPReceive.dll
hope this helps,

PI/XI: "HTTP client. Code 110 reason" for XML PO transmission

PI gurus,
We use XI to convert PO IDOC to XML message and send the XML message to our vendors.
We got the error message "HTTP client. Code 110 reason" for two POs while other POs went to the same vendor successfully.
We also have no problem for sending XML POs to other vendors.
Is this error caused from the sender or the receiver and how can I fix the problem?
Thanks in advance!
Fisher

Hi,
Below link will help
HTTP client code 110 reason
For reference check the below links too
Message not reaching Integration server
HTTPS Receiver Adapter with POST and query String

Code 110 Reason Error in HTTP Receiver adapter

Hello
I am having proxy to HTTP Receiver scenario in which i am calling the target application URL through HTTP Receiver Adapter. This interface is async interface and hence i am not expecting any response from the target system.
When i execute my interface the target system receives data from XI but in SXMB_MONI it sets the status of the message as "<b>Automatic Restart</b>" with the error description as "<b>HTTP client. Code 110 reason</b>" in HTML Code area <b><SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code></b>
This is causing multiple messages stuck in the queue and presently i am manually clearing all the messages.
i checked the quality of service of the incoming message which is correctly setted as <b>Exactly Once</b>.
Is there any configuration missing?
Thanks in advance.
Regards
Rajeev

Hi Rajeev,
1.)Check in SMICM if your HTTP service is running or not.
2.)If its running fine then you can check whether your SSL certificate is configured properly or not.
Also follow the below mentioned links :
HTTP 110
HTTP Receiver Adapter -> HTTP client code 110 reason error when sending
*Pls reward with points if helpful*
Regards,
Shibani

Error while receiving by HTTP (error code: 110) ?

Hi Experts,
I am working on IDOC to file Scenario.
I am getting this error in SXMB_MONI. What may be the reason.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Best Regards,
Anil

Check these threaads:
Re: XI Error when upgraded to SP14 (Error Code 110) CLIENT_RECEIVE_FAILED
Regards,
ravi

Simple HTTP Receiver - HTTP server code 405 reason Not Allowed explanation

Hi, I am using simple HTTP Receiver to receive the XML file from the below url http://www.bank-ua.com/export/currrate.xml
But receiving the below error in SXMB_MONI
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>405</SAP:P1>
<SAP:P2>Not Allowed</SAP:P2>
<SAP:P3><html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx/1.4.1</center> </body> </html></SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP server code 405 reason Not Allowed explanation <html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx/1.4.1</center> </body> </html></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Initially the same URL was working could you advice what to change to make this working?
Thanks,
Dhill

Hi Senthil,
There is a way, you can expose the function module HTTP_GET as an rfc-enabled FM and use it to call the webservice. Here is a POC I made before:
Proof of Concept: An Alternative HTTP GET using a Remote-Enabled Version of the Function Module HTTP_GET
Another is to create a UDF that uses an HTTP Client class to call the webservice.
Regards,
Mark

HTTP server code 500 reason Internal Server Error explanation Error during

Hi,
I am trying to connect to SAP TM (Tranportation Management) System using HTTP adapter using PI 7.0.The scenario is
ECC ->PI->SAP TM. I have configured HTTP adapter as the receiver with addressing type as HTTP Destination. I have created a RFC destination of type H pointing to SAP TM on PI. I have encountered the following error after executing the scenario.
<?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>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Error during parsing of SOAP header</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
Kiran

Error during parsing of SOAP header
Can you mention what are the settings done in Receiver HTTP channel.....the request that you send to target is not in proper format.
One reason could be incorrect Content Type.....is it text/XML ?
Regards,
Abhishek.

HTTP server code 500 reason Internal Server Error

HI,
I am getting following error in Call Adapter
<?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>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Internal Server Error</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Internal Server Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have a Business system that is sending the material master data to a different Business System via XI. The message is received by XI correctly. XI correctly performs the transformation and identifies the message interface and selects correct receiver for the message. XI communicates with the receiving business system via the appropriate communication channel.
The message "fails" in the receiving system with the following error:
HTTP server code 500 reason Internal Server Exception explanation Error parsing of SOAP header.
The channel is using HTTP Adapter type, and i cross checked the communication channel details like Addressing type, target host, service number, path, user name, user password.......each and every detail is correct.
Please help me out to find the solution to the problem.
Points will be gladly awarded.
Edited by: Ashish Soni on Sep 24, 2008 9:02 PM

try sending the same XML message picking from moni and check whether you are getting same error or not?
if you get same error then check at web server for logs there you can find exact error.

Getting the error: Error while receiving by HTTP error code: 110

Hi,
I have developed an interface which actually gets data from SCM system and in BPM to gets additional data from R/3. There are five synchronous call to this R/3 to get different sets of data. I am using only one communciation channle from BPM to R/3. The interface works perfectly OK in the development system. When the interface is migrated to the test system I found that the four calls work perfectly fine while the last call error out as below and the J2ee server goes down:
<?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">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Any input/help will be appreciated. I have tried increasing timeout/connection alive time but still not get resolved.
Thanks in advance,
Sushma

Hi Prateek,
Thanks. But this note I have checked before and this seems not related. I actually found out the system logs in SM21 and saw the "Operating system call recv failed (error no. 10054)". What I did then is I seach notes related to this error and found a numebr of SAP notes. And I have informed the Basis guys to look into the notes and the system logs. They are working on this and they are deleting the old messages which have errored out. They are suspecting the system memory or too many old messages would have caused this issue.
If you have any knowledge of why this error would have occurred please let me know.
Thanks,
Sushma

Http server code 401 reason Unauthorized

Hi,
I am trying to setup a scenario of sending an IDOC from R/3 to XI and then sending it further to a 3rd party program using the HTTP Channel.
If I go to transaction IDX5 in XI, I can see my IDOC sitting there as Inbound. When I check the error message on it, I get the message "Http server code 401 reason Unauthorized explanation Unauthorized" Also further along on the screen it says that the error category is "PLAINHTTP_ADAPTER" and Error ID is "ATTRIBUTE_SERVER".
Can someone guide me towards a solution?
Thanks in Advance!
Miguel

Hi Rekha,
I have checked the settings and they appear to be correct.
Here is a piece of the trace of the monitor where the error occurs:-
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">---- Plain HTTP Adapter Outbound----</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_HTTP_PLAIN_OUTBOUND-ENTER_PLSRV">
<Trace level="3" type="T">Quality of Service EO</Trace>
<Trace level="1" type="T">Get XML-Dokument from the Message-Objekt</Trace>
<Trace level="2" type="T">HTTP-Destination : SBO_ITK</Trace>
<Trace level="3" type="T">Server pgsap09.sap.pg.co.za</Trace>
<Trace level="3" type="T">Service-Nr. 80</Trace>
<Trace level="3" type="T">URL /SBOWebService/xi</Trace>
<Trace level="3" type="T">~request_method POST</Trace>
<Trace level="3" type="T">~server_protocol HTTP/1.0</Trace>
<Trace level="3" type="T">accept: /</Trace>
<Trace level="3" type="T">content-type: text/xml</Trace>
<Trace level="3" type="T">msgguid: 2F7389425DBE1711E100000082010B5A</Trace>
<Trace level="3" type="T">service: DR0</Trace>
<Trace level="3" type="T">interface namespace: http://sap.com/xi/SBO</Trace>
<Trace level="3" type="T">interface name: MasterDataFunctionModule__vendorMasterUpdate</Trace>
<Trace level="3" type="T">quality of service: EO</Trace>
<Trace level="3" type="T">Header-Fields</Trace>
<Trace level="3" type="T">Prolog conversion Codepage: UTF-8</Trace>
<Trace level="3" type="T">Epilog conversion Codepage: UTF-8</Trace>
<Trace level="3" type="T">content-length 3273</Trace>
<Trace level="2" type="T">HTTP-Response :</Trace>
<Trace level="2" type="T">Code : 401</Trace>
<Trace level="2" type="T">Reason: Unauthorized</Trace>
<Trace level="2" type="T">Code : 401</Trace>
<Trace level="2" type="T">Reason: Unauthorized</Trace>
</Trace>
From this it appears that it is complaining about the user name into the external program, although when I do a test connection in SM59, I get a positive response?
Thanks,
Miguel

Http server code 503 reason Service Unavailable explanation Service Unavail

Hi all
I am trying to send data to a HTTP SITE.
I am getting the following error.
Could somebody guide me how to solve this.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Oxalate</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>503</SAP:P1>
<SAP:P2>Service Unavailable</SAP:P2>
<SAP:P3>Service Unavailable</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Http server code 503 reason Service Unavailable explanation Service Unavailable</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thankyou

Same errors are comming up.
Could not do a RFC connection to website.

HTTP Client : Code 110 reason

Similar Messages

Maybe you are looking for