cancel
Showing results for 
Search instead for 
Did you mean: 

Internal error: Could not find SLD name for XI Application

Former Member
0 Kudos

Hello Experts,

Configuration Wizard in Integration Directory tool fails to load and states "cannot connect to repository". Java memory logs indicate it cannot find the repository because SLD entries are not correct.

I implemented notes 764176 and 1031321 because it looked like the SLD wasn't properly populated for the system (BID which is a dev system). After that it still didn't appear all entries were there so I manually created many missing entries for dev that I saw for production

Dev didn't even have a domain defined in SLD so I created one will all dependencies which took a while as there were many

The restarted the instance (Java+ABAP to be sure), but no change.

error in java memory log that show it's an SLD problem is this: 193 17:10:42 [SAPEngine_Application_Thread[impl:3]_21] ERROR com.sap.aii.ib.core.util.AbstractWebUtils: Internal error: Could not find SLD name for XI Application "RWB"

Thrown:

MESSAGE ID: com.sap.aii.ib.bom.landscape.rb_landscape.SLD_ASS_NOT_FOUND_EX

com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: Unable to find an associated SLD element (source element: SAP_XIIntegrationRepository, [CreationClassName, SAP_XIIntegrationRepository, string, Name, repository.bid.albbid1, string], target element type: SAP_XIIntegrationServer)

at com.sap.aii.ib.server.sldquery.SLDQuery.getMyRuntimeManagementServer(SLDQuery.java:450)

at com.sap.aii.ib.web.util.WebUtils.getMyRuntimeManagementServer(WebUtils.java:204)

at com.sap.aii.ib.core.util.AbstractWebUtils.getSLDName(AbstractWebUtils.java:48)

I done the following also

check the configuration in the transaction SLDAPICUST. Make sure that the password maintained is correct and the maintained service user is not locked

in the Integration Repository go to Environment ? Clear SLD Data Cache. Also go to Integration Directoy and clear the cache using menu Environment ? Clear SLD Data Cache.

The SLD Data Supplier in the Java Visual Admin is not set correctly. This should resolve the error

SLDCHECK should be ok,

then clearing of cache work also;

restart the J2EE engine

at com.sap.aii.ib.core.util.AbstractWebUtils.getBaseURL(AbstractWebUtils.java:60)

at com.sap.aii.ib.web.util.WebUtils.createLink(WebUtils.java:68)

at jsp_Main1295372594243._jspService(jsp_Main1295372594243.java:150)

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

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(AccessController.java:219)

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

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

more concise:

ERROR com.sap.aii.ib.core.util.AbstractWebUtils: Internal error: Could not find SLD name for XI Application "RWB"

Thrown:

MESSAGE ID: com.sap.aii.ib.bom.landscape.rb_landscape.SLD_ASS_NOT_FOUND_EX

com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: Unable to find an associated SLD element (source element: SAP_XIIntegrationRepository, [CreationClassName, SAP_XIIntegrationRepository, string, Name, repository.bid.albbid1, string], target element type: SAP_XIIntegrationServer)

Accepted Solutions (1)

Accepted Solutions (1)

sunil_singh13
Active Contributor
0 Kudos

Delete all the entries from SLD for Technical System of Type "PI". Restart your java stack. then reopen IR and ID

(Make sure Serveice users (users starting with PI*) are not locked ).

Restarting will register all the PI component in SLD. There could be chances that TS: Integration Engine will be missing its domain name. To resolve that refer SAP Note.

There is also Opetion in NWA configuration Wizard to register PI component in SLD.

Thanks,

Sunil Singh

Former Member
0 Kudos

Hello,

same error: Unable to find an associated SLD element Unable to find aUnable to find an associated SLD element n associated SLD element

I tried all the above...!!

Any further suggestions...

Regards,

Rao.

0 Kudos

Hi Rao,

Check for inconsistence in SLD with note 764176.

Kind regards,

Caio Cagnani

Former Member
0 Kudos

Hello,

Yes, that is the original note I implemented all changes from.

SAP has replied stating I may need to re-import a package with JSPM. I will check and let you know.

Regards,

Rao.

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Have you performed PI readiness check. If not please perform it

[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0b96675-87cf-2c10-b489-dee0ac03f782?QuickLink=index&overridelayout=true]

Regards,

Venkata S Pagolu

former_member854360
Active Contributor
0 Kudos
Former Member
0 Kudos

Hello,

Thanks for the replies. I will update you.

Regards,

Rao