CLIENT_CREATE_FAILED

- <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_CREATE_FAILED</SAP:Code>
<SAP:P1>1</SAP:P1>
<SAP:P2>HOST test PORT test SCHEME 1</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP client could not be created (exception 1 call parameter HOST test PORT test SCHEME 1)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I got the above error while executing a scenario. Please help solve this error.

Hi
i hope these can also can help you
Cannot create HTTP client Exception in Http --> XI --> RFC scenario
CLIENT_CREATE_FAILED error in the Call Adapter pipeline
regards,
lpbuff

Similar Messages

CLIENT_CREATE_FAILED in XI 7.0

Hi ,
This is the error that the abaper is getting,
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_CREATE_FAILED</SAP:Code>
<SAP:P1>1</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Cannot create HTTP client (exception 1)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have found a sap note:716739. This is related to XI 3.0.
This notes talks abt updating patch for Basis 640, whereas in XI 7.0 basis release is 700.
Please suggest.
Thanks,

Hi,
This problem occurs when XI is trying to send a message, but the target-system cannot be reached.
solution of this is
- Check if the adapter engine is up and running (J2SE /J2EE) . When this is not the case, try to restart the adapter engine
- Try to reprocess the message.     When reprocessing the message, the system will ask a question about the trace level that should be used in the reprocessing of the message. This question should be answered with increased trace level, for a more detailed trace when reprocessing the message will also fail.
- If the reprocess of the message fails, the message will be put back in the processed messages list as an faulty-message
- If the message is still faulty, then the following steps could be applied to check what the problem of this system is.
     First get the communication-settings like, system name, port number and username and password
     The second step is to ping the system
     If you can access the system with the ping command, then you can use telnet to control if configured port on the machine is open.
     If this fails control the process/script that sets up the environment and configure the ports accordingly
     At last you can check if the username and password are correctly configured
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

CLIENT_CREATE_FAILED error in the Call Adapter pipeline

Hi, all.
i think i've almost done the configuration of XI 3.0(CI + 2 DIs).
SXI_CACHE, SLDCHECK, import of IR, ID objects ...etc. are O.K.
But when i really run some scenarios of,
File Adapter --> XI --> ABAP Proxy or
ABAP Proxy --> XI --> Java Proxy, messages always got error in the "Call Adapter" pipeline of IS with the following message.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_CREATE_FAILED</SAP:Code>
<SAP:P1>1</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Cannot register HTTP Client(Exception 1)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any advice appreciated.
Best Regards.

Thanks, guys. Let me update my situation.
i checked and rechecked dest:// ABAP Proxy : Error in Call Adapter step!
For the error message of #3, i already attached message in my previous email.
And following is the error message of #2. Please HELP!!!
- Help
!http://BSDEA03.darwin.denka.co.jp:50000/sap/public/icman/img/theme.jpg|alt=SAP|width=122 height=61 border=0 |src=http://BSDEA03.darwin.denka.co.jp:50000/sap/public/icman/img/theme.jpg!
500 Internal Server Error
Internal Server Error(-1)
Error:
-1
Version:
6040
Component:
ICM
Date/Time:
Tue Jul 26 15:40:19 2005
Module:
icxxthrio.c
Line:
538
Server:
BSDEA03_PDX_00
Detail:
internal error occured
© 2001-2003, SAP AG
</FONT></td></tr></table></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when receiving by HTTP (error code: 405, error text: ICM_HTTP_INTERNAL_ERROR)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Any advice appreciated.
Best Regards.

XI Error(CLIENT_CREATE_FAILED)

Hi,
I am creating a scenario HTTP --> XI -
RFC.
When we are calling RFC from the XI server we are getting the error "CLIENT_CREATE_FAILED".
RFC function module is on different R/3 server.
Please find the elaborate error below :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_CREATE_FAILED</SAP:Code>
<SAP:P1>1</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Cannot create HTTP client (exception 1)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please suggest.
Regards
Amitanshu

Hi
Check this thread ....
Cannot create HTTP client Exception in Http --> XI --> RFC scenario
CLIENT_CREATE_FAILED error in the Call Adapter pipeline
Reward points if usefulll......

Cannot create HTTP client Exception in Http -- XI -- RFC scenario

Hi,
We are testing Http --> XI --> RFC scenario
While testing this scenario from RWB we are getting following error message in the SXMB_MONI logs:
<?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_CREATE_FAILED</SAP:Code>
<SAP:P1>1</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Cannot create HTTP client (exception 1)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Following is the info from the Trace:
<Trace level="1" type="System_Error">cl_http_client exc = argument_not_found</Trace>
We have tried following things:
1. In SICF we made sure the /default_host/sap/xi/adapter_plain is active
2. Applied SAP Note: 716739
Any response will be greatly appreciated.
Thanks,
Paresh

Hi UDO,
Thanks for your reply. The error was gone when I tested again this morning. I am guessing it must be the SAP Note 716739 that we applied and might not have refreshed the cache.
I am still intereseted in confirming what exacly fixed this issue.
As per your suggestion, I looked at the left Nav bar and the error was at the "Call Adapter" step. Even in the log message it says the same. The reciever/interface determination and mapping were successfull. I could successfully test the scenario in the integration directory.
Here is what the 716739 Note said:
Symptom
If you call the Integration Server from a sending Integration Engine (proxy), the following error message occurs:
Category = XIServer
Area = INTERNAL
Id = CLIENT_CREATE_FAILED.
In transaction SXMB_ADM, you used the Configure Integration Engine function to enter a URL of the type http://<host>:<port>/sap/xi/engine?type=entry instead of a URL of the type dest://<name>.
Other terms
SICF, SXMB_MONI, SXMB_ADM, XI
Reason and Prerequisites
You have configured the communication route from the sending proxy (Integration Engine) to the Integration Server using the URL of the type
http://<host>:<port>/sap/xi/engine?type=entry and have saved the logon data on the Integration Server in the Service
/sap/xi/engine (transaction SICF).
A program error has occurred: the communication log is not correctly set when the HTTP client is set up.
Solution
The problem is eliminated with SAP_BASIS Support Package 2. To eliminate the problem, you can use an URL of the type dest://<name>, where <name> refers to the name of a HTTP destination that you have maintained with transaction SM59.
Now, I was not using the proxies but Http post to XI. Do you guys also think this might have fixed my issue?
Thanks,
Paresh

ICM_HTTP_TIMEOUT - INTERNAL.CLIENT_RECEIVE_FAILED

Hello,
I have set up the following scenariro:
Synchronous Communication between SAP R/3 and an external Orcale Database via ABAP-Proxy on the R/3-Side and JDBC on the Oracle-Side. The whole thing works fine as long as the requests don't get too big.
But now I have to make an initial Download from the Oracle-DB which approximately lasts about 5 hours. In this case my "Timeout-Problem" begins:
In R/3 I get the following Error in SXMB_MONI:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="402" p2="ICM_HTTP_TIMEOUT" p3="" p4="">INTERNAL.CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:Text language="DE">Fehler beim Empfangen per HTTP (Fehlercode: 402, Fehlertext: ICM_HTTP_TIMEOUT)</SAP:Text>
</SAP:ErrorHeader>
In XI the following Erorr appears:
- <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>402</SAP:P1>
<SAP:P2>ICM_HTTP_TIMEOUT</SAP:P2>
<SAP:P3 />
<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://cat01135:50100/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://cat01135:50100/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td> </tr><tr><td background="http://cat01135:50100/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>500 Connection timed out</H2><br>Connection timed out (-5) <br><hr> <table border="0"> <tr><td>Error:</td><td>-5</td></tr> <tr><td>Version:</td><td>6040</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Wed Aug 17 02:21:14 2005 </td></tr> <tr><td>Module:</td><td>icxxthr_mt.c</td></tr> <tr><td>Line:</td><td>2559</td></tr> <tr><td>Server:</td><td>cat01135_XY1_01</td></tr> <tr><td>Detail:</td><td>Connection to partner timed out</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-2003, SAP AG</a></FONT></td></tr></table></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Fehler beim Empfangen per HTTP (Fehlercode: 402, Fehlertext: ICM_HTTP_TIMEOUT)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
The trace in R/3 doesn't say anything important I think.
The trace in XI is only a little more interesting:
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for adapter engine: JDBC</Trace>
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" />
- 
<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET): af.xy1.cat01135</Trace>
<Trace level="3" type="T">URL = http://cat01135:50100/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User = XIISUSER</Trace>
<Trace level="3" type="T">Cached =</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</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="System_Error">HTTP-Client: exception during receive: HTTP_COMMUNICATION_FAILURE</Trace>
</Trace>
</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
<Trace level="3" type="T">Persisting message Status = 023</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
</Trace>
<Trace level="1" type="T">SystemError message generated. Guid: 43010F97F29A007F020000000A180A87</Trace>
<Trace level="1" type="T">Error during execution of message : 43010594DCA300A0020000000A180A28</Trace>
<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): 43010594DCA300A0020000000A180A28</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 023</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Has anybody an idea, which Parameter(s) can be responsible for this situation ???
I tried to lift up the TIMEOUT-PARAMETERS on both sides. Here are the Parameters in R/3:
icm/server_port_0     PROT=HTTP,PORT=1080,TIMEOUT=36000
icm/keep_alive_timeout (sec.) = 60
icm/conn_timeout (msec.)       = 5000
Here are the Parameters in XI:
icm/server_port_0     = PROT=HTTP,PORT=8001,TIMEOUT=34200
icm/keep_alive_timeout (sec.) = 60
icm/conn_timeout (msec.)       = 5000
The Timeout always comes after 15 min.
Would be great if anybody has an idea - Thanks a lot
Werner Knapp

Hi Werner,
check these links, hope they help to fix your issue
Messages stuck in Queue
Re: SOAP Adapter XI 3.0 Response HTTP 402 ICM_HTTP_TIMEOUT
Re: CLIENT_CREATE_FAILED error in the Call Adapter pipeline
Re: CLIENT_RECEIVE_FAILED in XI 3.0
Re: HTTP_RESP_STATUS_CODE_NOT_OK in IS after performing client copy
Re: "Scheduled for Outbound processing" message
Regards
Vishnu

CLIENT_CREATE_FAILED

Similar Messages

Maybe you are looking for