cancel
Showing results for 
Search instead for 
Did you mean: 

PLAINHTTP_ADAPTER - ATTRIBUTE_SERVER

Former Member
0 Kudos

Hi,

I'm facing problem with HTTP services. we are getting XML message with status <b>System Error - Manual Restart Possible</b> and the error is

-


>

<?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>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><b>Message ID 1A0FC7735437434C8CD1D93603E96D5B already exists in called system</b> (pip</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack><b>Http server code 500 reason Internal Server Error explanation Message ID 1A0FC7735437434C8CD1D93603E96D5B already exists in called system</b> (pip</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

-


>

we done changes in J2EE stack via Visual Admin according to OSS note 804124. we still getting the Plain HTTP Adapter problem.

How to resolve this Plain HTTP Adapter problem.

Thanks in Adv,

Yallabandi.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Moorthy,

I am working with Rajesh on the same project.

The HTTP adapter configuration done by us is as given below:

Addressing Type: <b>URL Address</b>

Target Host: <b>IP of the XI server</b>

Service Number: <b>8030</b>

Path<b>:/sap/xi/adapter_plain?namespace=<my namespace>&interface=ALEAUD_out_asy&service=ABCXI1&QOS=EO</b>

Next we have provided the logon data for sap system.

All this values are provided following the given weblog:

<b>/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements

The adapter engine is also up and running.

This time the error msg we are getting is:

<b><?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>XIAdapter</SAP:Category>

<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>

<SAP:P1>404</SAP:P1>

<SAP:P2>Not Found</SAP:P2>

<SAP:P3>Not Found</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Http server code 404 reason Not Found explanation Not Found</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error></b>

What coyld be the possible reason for this error?

Is something missing in the configuration values?

Pls help.

Thanks in advance.

Regards,

Neetu

former_member187339
Active Contributor
0 Kudos

Hi,

Are you calling a R/3 then go for Addressing type = <b> HTTP Destination</b>

http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm

Have a look at the SMICM->Trace file. Are you getting any errors?

Explain your scenario so that it might be more helpful.

Regards

Suraj

Former Member
0 Kudos

Hi,

In SMQ2 no entries found. and

RFC AI_RUNTIME_JCOSERVER is working fine.

Wereas in Adapter Monitoring HTTP adapter is not there. what does this means? its our first development with HTTP services. do we need to install any support pack?

Looking forward for Ur inputs.

Thanks,

Yallabandi.

moorthy
Active Contributor
0 Kudos

Hi,

That's ok.You will not see the Http adapter in the Adapter Engine.

Even Idoc adapter . Because Idoc and Http Adapters are part of ABAP stack. You can see only adapters which are part of J2EE adapter engine.

Can you recheck your Http adapter configuration? URL etc.

Also make sure that Adapter engine is running.

Regards,

Moorthy

moorthy
Active Contributor
0 Kudos

Hi,

If it is System Error, go to SMQ2 and check the status of this. It will give you reason also. if there is any JCO communication error etc , then go to SM59->TCP/IP connections->AI_RUNTIME_JCOSERVER and test the connection. If there is error then it is better to restart system and go further testing.

Also make sure that http adapter is running or not.

Regards,

Moorthy