Receiver Proxy adapter

[Former Member]

Hello Experts,

I am getting a message in SXMB_MONI "Pipeline ENTRY does not exist (table SXMSPIPE)" <SAP:Category>XIServer</SAP:Category>

I am using a receiver XI adapter with HTTP protocol. Appreciate your help in resolving this.

Thanks

Ricky

[Former Member]

can u explain more on how u have configured the scenario?

[Former Member]

Entry maintained for SLD Business System IS, SXMB_ADM IS_URL. SMICM http port ..What else is missing

Thanks

Ricky

[Former Member]

This is the error message I am getting

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

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="CONFIG">PL_NOT_FOUND</SAP:Code>

<SAP:P1>ENTRY</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>Pipeline ENTRY does not exist (table SXMSPIPE)</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

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

Thanks

Ricky

[Former Member]

Has anyone got any idea?

Thanks

[prateek]

Apply SAP Note 602959

Regards,

Prateek

[Former Member]

Now, I am getting the following error message in MONI.

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

<SAP:Code area="PARSER">ITEM_MISSING</SAP:Code>

<SAP:P1>/MessageHeader/MessageId</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Das XML-Element /MessageHeader/MessageId fehlt im SOAP-Message Header (SAP XI Extension)</SAP:Stack>

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

</SAP:Error>

Any help is appreciated

Thanks

[Former Member]

Hi,

I resolved this one by changing the XI 3.0 to 2.0 since R/3 is running on 6.20

But I am stil gettng the previous error <?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="1">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="CONFIG">PL_NOT_FOUND</SAP:Code>

<SAP:P1>ENTRY</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>Pipeline ENTRY does not exist (table SXMSPIPE)</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

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

</SAP:Error>

Has anyone encounterd this type of error? It's long time waiting for resolving ..:(

Thanks

[Former Member]

Hi Ricky,

Just curious, but I assume the system that issued the message is the receiving R/3 6.20 System?

The error message says: "Pipeline ENTRY does not exist".

This means that the system that issued the message is looking for a pipeline called 'ENTRY' in its 'XML Message Server: Pipeline Definition' table SXMSPIPE.

The question is "Why would the system that issued the message be looking for a pipeline called 'ENTRY'". A possible answer follows.

I noticed in the SAP Note 602959, mentioned earlier in the forum thread, the following paragraph:

• Begin of SAP Note quoted paragraph ****

The correct URL is http://<host>:<port>/sap/xi/engine?type=entry&pipelineid=entry whereby you ... transaction SMICM (Goto -> Services).

If you are working exclusively in XI 2.0 (that is, you do not have a XI 1.0 sender), the correct URL is: http://<host>:<port>/sap/xi/engine?type=entry

• End of SAP Note quoted paragraph ****

I notice that the first URL in the above paragraph contains the parameter '&pipelineid=entry' while the second URL does not.

I don't know if you have control over the URL that calls the proxy in the receiving R/3 6.20 System, but if I were you, I'd try to make sure that the URL doesn't contain the parameter '&pipelineid=entry' because I think this parameter might be the reason for the system trying to find a pipeline called 'ENTRY'.

What do you think?

Best Regards,

Andy