ConfigException: SLDAccess set to true, but not available.

[Former Member]

Hello,

I'm getting this response from my SOAP adapter when I try to send a WS message:

The input for this error in the Adapter Engine trace file is:

#

#1.5 #0003BA204A5900500000028B00003FD300046482980E7217#1236411966452#com.sap.engine.services.security.roles.SecurityRoleImpl#sap.com/com.sap.aii.af.app#com.sap.engine.services.security.roles.SecurityRoleImpl#XIRWBUSER#6666##natural_DXI_43572850#XIRWBUSER#49B130EFE9AA3F8CE10000000A01B504#SAPEngine_Application_Thread[impl:3]_12##0#0#Error#1#/System/Security/Audit/J2EE#Java###: Authorization check for caller assignment to J2EE security role .#3#ACCESS.ERROR#SAP-J2EE-Engine#administrators# #1.5 #0003BA204A59007B0000022600003FD3000464829A8C3A5F#1236412008249#com.sap.aii.adapter.xi.ms.XIEventHandler#sap.com/com.sap.aii.af.ms.app#com.sap.aii.adapter.xi.ms.XIEventHandler.onRequest(Services, TransportMessage)#DXIISUSER#6670##natural_DXI_43572850#DXIISUSER#1c96fb700aec11debf170003ba204a59#SAPEngine_Application_Thread[impl:3]_21##0#0#Error##Java###Message : was not delivered due to #2#166e4aa0-0aec-11de-b285-0003ba204a59(INBOUND)#com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.#

#1.5 #0003BA204A59006E0000026A00003FD3000464829AA3AFBC#1236412009787#XIRWB.com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage#sap.com/com.sap.xi.rwb#XIRWB.com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage#DULIAA0A#6662##natural_DXI_43572850#DULIAA0A#7bb7f7e00aeb11deb3530003ba204a59#SAPEngine_Application_Thread[impl:3]_10##0#0#Error#1#/Applications/ExchangeInfrastructure/RuntimeWorkbench#Plain###com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.

Thrown:

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

at com.sap.aii.rwb.web.componentmonitoring.util.XMBMessageAgent.sendMessage(XMBMessageAgent.java:113)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_sendtestmessage(CmDynPage.java:280)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)

at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:115)

at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)

at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)

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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)

at jsp_FC_Secure1209984970430._jspService(jsp_FC_Secure1209984970430.java:24)

at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)

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)

#

It looks like an access error as seen from this line:

#0003BA204A59007E0000024A00003FD300046482BBD14C6C#1236412566424#com.sap.engine.services.security.roles.SecurityRoleImpl#sap.com/com.sap.aii.af.app#com.sap.engine.services.security.roles.SecurityRoleImpl#XIRWBUSER#6686##natural_DXI_43572850#XIRWBUSER#49B13565E9AA3F8CE10000000A01B504#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Security/Audit/J2EE#Java###: Authorization check for caller assignment to J2EE security role .#3#ACCESS.ERROR#SAP-J2EE-Engine#administrators#

How can I find the cause of this error?

Thank you

Regards,

Gökhan

[Former Member · Accepted solution]

HI ,

Did you check the solution for the question "I got error message "SLDAccess set to true, but not available". " in Michal's FAQs blog /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions

Thanks,

Pooja Pandey

[Former Member · Accepted solution]

Yes, I have checked the business system. SLDCHECK also works properly.

Regards,

Gökhan

[Former Member]

Hi,

Pls check profile that your SLD is given the same client ID you are connecting.

Thanks .