cancel
Showing results for 
Search instead for 
Did you mean: 

com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not av

Former Member
0 Kudos

Hello,

I'm getting the below error while making a call to the sender soap communication channel which was working fine until my client went for an enhancement to the server. What can be the possible causes of error and how can they be fixed? Thank you.

<?xml version='1.0'?>

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

<SOAP:Body>

<SOAP:Fault>

<faultcode xmlns="">SOAP:Server</faultcode>

<faultstring xmlns="">Server Error</faultstring>

<detail xmlns="">

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

<context xmlns="">XIAdapter</context>

<code xmlns="">ADAPTER.JAVA_EXCEPTION</code>

<text xmlns="">

com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.

at com.sap.aii.adapter.xi.ms.XIMessage.addHopListEntry(XIMessage.java:3187)

at com.sap.aii.adapter.xi.ms.XIMessage.prepareToSend(XIMessage.java:1923)

at com.sap.aii.adapter.xi.ms.XIEventHandler.onSend(XIEventHandler.java:273)

at com.sap.aii.af.ra.ms.impl.ConnectionImpl.send(ConnectionImpl.java:166)

at com.sap.aii.af.ra.ms.impl.ConnectionImpl.send(ConnectionImpl.java:215)

at com.sap.aii.af.ra.ms.impl.ConnectionImpl.send(ConnectionImpl.java:235)

at com.sap.aii.af.mp.soap.ejb.AFCallerApplication.perform(AFCallerApplication.java:123)

at com.sap.aii.messaging.srt.ApplicationBubble.onMessage(ApplicationBubble.java:29)

at com.sap.aii.messaging.srt.ExtensionBubble.onMessage(ExtensionBubble.java:56)

at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:913)

at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3.process(ModuleLocalLocalObjectImpl0_3.java:103)

at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:292)

at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)

at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:174)

at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:436)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

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:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

</text>

</s:SystemError>

</detail>

</SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

Accepted Solutions (1)

Accepted Solutions (1)

aashish_sinha
Active Contributor
0 Kudos

Hi,

have a look into [SAP Note 1282862|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1282862].

Also have a look into thread

Regards

Aashish Sinha

Edited by: Aashish Sinha on Mar 4, 2009 6:37 AM

Answers (5)

Answers (5)

Former Member
0 Kudos

The error is still there. The basis team informed me that the all users have been checked and they are consistent on the LDAP server where SLD runs, the PI server and the exchange profile.

SLDCHECK results OK, there are no visible inconsistencies in SLD, all technical/business systems are correctly defined and the cache refresh works fine.

What else needs to be checked for this error?

Former Member
0 Kudos

OK I will ask the basis team to check for the users for consistency.

Edited by: S. Gökhan Topçu on Mar 6, 2009 4:37 PM

former_member568822
Active Participant
0 Kudos

Hi,

I am getting this error when the sld server is down. Please check whether it has down. Just type tcode sldcheck on you XI server to check.

Best regards,

Gan

JoelTrinidade
Active Contributor
0 Kudos

Dear Friend,

I have not faced with this error but i went through you log and what caught my attention is "com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available." .

First and foremost you will need to check for sld access. If that fails then go ahead with what alka says. I will not repeat her words.

Take the help of basis to resolve the sld access error.

Rgds

joel

Former Member
0 Kudos

Hi,

This problem occurs when,

1. The Web Service which is invoked is a secure Web Service,

2. The User which is used to authenticate the Web Service call does not have authorizations to work with the SLD of the PI Server,

3. Or, The User has access to SLD, but the password for the XI login and SLD login are different, which can haapen in the case that the PI Server does not have a local SLD.

As you have mentioned that the server in your landscape has been upgraded, point 2 and 3 may prove helpful.

Regards,

Alka.

Former Member
0 Kudos

"2. The User which is used to authenticate the Web Service call does not have authorizations to work with the SLD of the PI Server,

3. Or, The User has access to SLD, but the password for the XI login and SLD login are different, which can haapen in the case that the PI Server does not have a local SLD."

I don't think PI uses the user that sends the message to retrieve data from SLD, it should be using its own service users. Is it not true?

prateek
Active Contributor
0 Kudos

I don't think PI uses the user that sends the message to retrieve data from SLD, it should be using its own service users. Is it not true?

True :). Any user with APPL related role could post the message but service users usually helps in talking to SLD.

For your case, you may proceed as follows:

1. Perform SLDCHECK and see if you get all green.

2. Check the url for integration server in sxmb_adm -> integration engine cofiguration.

3. See if your service users like PIAFUSER are locked. And if there was a recent password change, then it wasn't only from su01 but also at exchange profile.

4. After checking this all, perform a full CPACache refresh.

Regards,

Prateek