PI 7.1 - Unable to find associated SLD element for specified class

[Former Member]

Hello,

I'm getting the following error message in PI 7.1 Integration Builder Directory after I used the Menu > Envirnoment > Clear SLD Data Cache. Most of my communication channels now give this error when I try to open them.

Unable to find associated SLD element for specified class (source element: SAP_XIIntegrationDirectory, (CreationClassName, SAP_XIIntegrationDirectory, string, Name, directory.XXX.sapXXXdb, string), target element class: SAP_XIIntegrationServer)

What might cause this?

Thanks,

Matt Herbert

Edited by: Matthew Herbert on Jun 22, 2009 7:22 PM

[Former Member]

Hi Herbert,

Even if problem has been solved for you, i am putting this for others who are facing the issue.

Go to NWA - Operations - Java applications - restart com.sap.xi.directory alone and try accessing ID. It will work.

[former_member205423]

Thanks Harish for Your Help

It Worked

[Former Member]

This message was moderated.

[Former Member]

Hi All,

I am also facing the same issue and looked at this as well other posts. As per suggestion, i tried stopping the service However when i click on the stop service i get the message this service is being stopped asynchronously, but refreshing the status, nothing changes ( from start to Stop or vice versa)

Also doing the other way around as not effect on our system. We just created this system by doing copy of out Production and and now doing the validations. While opening the CC i am getting this error.

Also when i doing Cache connectivity test from RWB, getting below error

Unable to find associated SLD element for specified class (source element: SAP_XIIntegrationRepository, [CreationClassName, SAP_XIIntegrationRepository, string, Name, repository.sxp.sapcisxp, string], target element class: SAP_XIIntegrationServer)

Please advice if you have any suggestion on this.

Thanks!

[jorge_velasquez]

Hi,

I cant see that link.

Where it is?

NWA - Operations - Java applications

[Former Member]

We started following the notes that you suggested and ran into more problems. After some digging we were able to locate the problem. Although, we thought set the password as non-expiring; the password for the ID that PI uses to communicate with the SLD expired.

Problem solved.

Thanks,

Matt Herbert

[Former Member]

Mathew,

Please check this thread for the same error:

---Satish