HTTP_RESP_STATUS_CODE_NOT_OK Error

[Former Member]

Hi All,

I am doing a scenario in XI as follows;

r/3--- [Idoc] -> XI -

---

http-->APO

The r/3 to XI is working perfectly and to send to APO I am using XI adaptor with HTTP transport protocol.

But I am getting the following error.

<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>

<SAP:P1>200</SAP:P1>

p1="" p2="" p3="" p4="">CALLER.MSG_GUID_NOT_QUALIFIED</SAP:Code><SAP:Text language="EN">Attribute message GUID not specified

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">

<Trace level="3" type="T">No persisting of message after plsrv call, because of config</Trace>

</Trace>

<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

<Trace level="3" type="T">Persisting message Status = 014</Trace>

<Trace level="3" type="T">Message version 002</Trace>

<Trace level="3" type="T">Pipeline CENTRAL</Trace>

Can someone share his knowledge in resolving this issue.

[Former Member · Accepted solution]

Hi Roopesh,

In your WAS where XI is running go to transaction SICF and in SAP-> XI-> Engine, maintain the user id and password for the HTTP default host connection and it should work...

Cheers

JK

PS: Award points if this helps you

[Former Member · Accepted solution]

Hi Rupesh,

Is the solution provided by Jayakrishnan worked for you?. Can you please confirm it.

Thanks,

Raj.

[Former Member]

Hi Roopesh,

Just check the mentioned possibilities for your error one by one:

1.Did you maintain Client, userid, password, and lang information in SICF transaction -> sap/xi/engine? Double click on service and check whether you have entered correct information.

2.Then you might check the roles of the XIISUSER in SU01. In some case there are some double roles, i.e., two times the role SAP_XI_IS_SERV_USER assigned. One might have the date of the last update, the other one might have apparently the older version. Delete the older roles manually and the error should disappear.

3.to send messages to xi you need a service id / pwd which is specific to your landscape usually its xiappluser. Contact your basis group for password.

4.

- Activated all services on the r3 system.

- Create HTTP connection to XI from r3

sm59-> http connetons to r3

- let us say you have created a HTTP connection in the integrationserver_XI, make sure in its settings the prefix path is set to /sap/xi/engine?type=entry. Also check its log on credentials, you can use xiappluser.

- IN Integration builder, receiver communication channel make sure you have entered proper

host service number

path = /sap/xi/enigne?type = receiver.

5. can you also try the following;

Visual Admin -> start the service,

"com.sap.aii.af.ms.app".

Please go through the followings links also :

http://help.sap.com/saphelp_nw04/helpdata/en/82/f4993c03e0cd37e10000000a11405a/content.htm

/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions

http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm

I hope the info provided help you solve your error.

Regards,

abhy

NOTE: reward the helpful.