Skip to Content
author's profile photo Former Member
Former Member

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" ?>

- <!--

Call Adapter

-->

- 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,

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 21, 2007 at 04:41 AM

    Hi,

    check the RFC connection of your receiver adapter and post wats the error is and we can analyse futher ...

    And also refer for more help:

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

    CLIENT_CREATE_FAILED error in the Call Adapter pipeline

    Regards

    Sai Ganesh

    Reward points if usefulll......

    Add a comment
    10|10000 characters needed characters exceeded

    • 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

  • author's profile photo Former Member
    Former Member
    Posted on Dec 18, 2008 at 04:51 AM

    Hi all,

    Thank you very much for your answers.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.