cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP Adapter - INTERNAL.EXCHANGE_PROFILE_ACCESS error

Former Member
0 Kudos

Hi all,

We are trying to set up a Webservice scenario in XI where we receive a request via a SOAP channel we forward it to a BPM and from there we return the response (synchronously).

We are able to receive the message and it seams that it then reaches the Integration Engine however this message then goes in error and we get the following:

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP:Body>

<SOAP:Fault>

<faultcode>SOAP:Server</faultcode>

<faultstring>System Error</faultstring>

<detail>

<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">

<context/>

<code>INTERNAL.EXCHANGE_PROFILE_ACCESS</code>

<text>Error while reading exchange profile for system AS1 and client 001</text>

</s:SystemError>

</detail>

</SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

Does anyone know what may be causing this: INTERNAL.EXCHANGE_PROFILE_ACCESS error?

We have looked everywhere and haven't found anything that could explain how to resolve this problem.

Many thanks.

Aldo Lazzarini

Accepted Solutions (1)

Accepted Solutions (1)

prateek
Active Contributor
0 Kudos

1. Perform SLDCHECK on abap stack. See if its successful or not.

2. Check the RFC LCRSAPRFC

Regards,

Prateek

Former Member
0 Kudos

Hi

Done some checks

- RFC connections are tested, no problems there

- SLDCHECK fine as well

Edited by: Steven Sillis on Feb 8, 2008 4:06 PM

Answers (6)

Answers (6)

Former Member
0 Kudos

Hi,

This problem was resolved but unfortunately I can't give you any feedback as we had to call in support.

Apparently there were multiple reasons behind it.

Regards,

Aldo

Former Member
0 Kudos

Hi Aldo

I also faced the same problem, may I know what are the things causing this? thanks

Former Member
0 Kudos

Thanks to all for the help so far.

However, as mentioned by Steven, we are still facing this problem.

@Harald, I believe that our XI system is still at SPS12.

Any other idea guys? What else can we do?

Regards,

Aldo

Former Member
0 Kudos

Hi,

Some stachtrace dump of the error we're still facing:

<text>com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:EXCHANGE_PROFILE_ACCESS:

at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)

at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:133)

at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:850)

at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</text>

Rgrds,

Steven

former_member334189
Active Participant
0 Kudos

Dear Aldo,

the exception might point to a wrong direction, you should check the SLD instead (tx sldcheck or call function module LCR_GET_IS_DETAILS directly).

Technical background: each time a message enters the Integration Server or Integration Engine the identity of the business system is determined. Up to XI3.0 SPS16 this information was retrieved from the Exchange Profile. As of XI3.0 SPS17 this information is coming from SLD. Unfortunately the exception was not changed. Thus, the old exception pointing to the Exchange Profile was raised in case the data retrieval from SLD failed. This is fixed as of XI3.0 SPS22.

Best Regards,

Harald Keimer

XI Development Support

SAP AG, Walldorf

Former Member
0 Kudos

Aldo,

The error says that your exchange profile is pointing to 001. But I dont think it is the case. Login into ABAP stack of XI and see in which client you are logging. If it is not 001 then the exchange profile should also point to the same client number. If this is yes then ask your basis guys to change the client in exchange profile.

Regards,

---Satish

Former Member
0 Kudos

Client 001 verified and this is also correct

Former Member
0 Kudos