cancel
Showing results for 
Search instead for 
Did you mean: 

Still problem with not able to find URL for adapter

Former Member
0 Kudos

I see in message monitoring in call adapter - soap header - Trace

<Trace level="1" type="T">error reading from exchange profile:Error when reading Exchange Profile</Trace>

</Trace>

</Trace>

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

<Trace level="3" type="T">Persisting message after plsrv call</Trace>

<Trace level="3" type="T">Message-Version = 012</Trace>

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

<Trace level="3" type="T">Pipeline CENTRAL</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 004</Trace>

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

</SAP:Trace>

Also

I can see in message monitoring in call adapter - soap header - 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="">

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

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

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>3: Unable to find URL for Adapter Engine af.mxp.mxiprd</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine</SAP:Stack>

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

</SAP:Error>

This problem is not yet been resovled even after followed the regular activities...

Please update me what exatctly the problem and with solution.

Thanks.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

Check with this

Regards

Seshagiri

Former Member
0 Kudos

Hi,

in this thread:

it's solved by changing the RFC destination configuration.

Regards

Patrick

Former Member
0 Kudos

Please can you define "regular activities"?

Have you checked the CIM associations in the SLD?

GabrielSagaya
Active Contributor
0 Kudos

please visit the thread

this might be helpful for you...