cancel
Showing results for 
Search instead for 
Did you mean: 

Accessing the System Landsape Directory (SLD) failed.

Former Member
0 Kudos

Hi all,

I know, there have been plenty of other threads regarding this topic, but i just can't seem to solve it!

I could not find any reason to get on ESS iviews this error:

Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics_MetaData' in the SLD. No such JCO destination is defined in the SLD

On Portal logs we get:

#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of Web Dynpro application . The causing exception is nested.

[EXCEPTION]

#2#sap.com/ess~wiw/WhoIsWhoApplication#com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.sap.pcuigp.xssfpm.wd.model.types.Ext_Service could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.

If I go to Visual Administrator/ SLD Data Supplier and I trigger send data information, a message appears like if all were working... but not.

Note 1234847 - Analysing WebDynpro session LockException & Note 710154 - How to create a thread dump for the J2EE Engine 6.40/7.0 were checked, but did not resolve nothing for me.

I have restarted Portal, but the problem does not fix.

Only happens on ESS iviews, other parts on Portal works ok

Do you have any idea why is happening this??

Thanks in advance

Scottie

Accepted Solutions (1)

Accepted Solutions (1)

hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear Scottie,

First of all go through the note throughly and implement it:

1544135 - Internal Server Error- Active component must exist when getting interface control

We have seen similar issues when the Jcos are maintained in the SLD. It is not recommended to change the JCOdestinations using SLD only. Use the WD content admin, although of course you have the possibility to change certain settings using the SLD. You can change any other data using the SLD webUI, but the reason is that in case you use the WD content admin it'll register the data in SLD and executes certain other internal steps, which won't happen if you maintain those data directly.

I attach you documentations which describes how to use the application:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot

/docs/library/uuid/1870c690-0201-0010-fca0-b66794ea3ea3

How to use WD Content Administrator

http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid

/526bd490-0201-0010-038e-d3ff7eb1d16e

WD Best Practices How to configure JCO

http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid

/3103eb90-0201-0010-71af-be6f4a6f61d1

Please close the thread if the query is resolved.

Thank you and have a nice day!

_____________

Kind Regards,

Hemanth

SAP AGS

Answers (1)

Answers (1)

former_member182598
Active Contributor
0 Kudos

Hi Scott,

Can you just check and confirm

When you are maintaining the JCO, on the third step it asks you about the Data Type, there you need to specify Application Data for SAP_R3_SelfServiceGenerics and for SAP_R3_SelfServiceGenerics_MetaData you have to select the Dictionary Meta Data type.

Aso try executing this

http://<portal host>:<Port>/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenuArea?sap.xss.menuhdr=SAPDEFAULT&sap.xss.menuargrp=SAPDEFAULTESS

If JCO and SLD are configured properly, this should work.

Let me know how it goes.

Thanks

Prashant