ESS/ MSS JCO destination error...

Question

Hi All,
I have created all JCO destinations and when i test them , the result is successful
But once i click on ess/mss tab in portals, i get the error..
<i>com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_HumanResources_MetaData' in the SLD. No such JCO destination is defined in the SLD.</i>
But i have maintained SAP_R3_HumanResources_MetaData in the SLD.. Actually i have two SAP_R3_HumanResources_MetaData services one is active and another is inactive..
For SAP_R3_HumanResources -- i have used "Logon Ticket" and for SAP_R3_HumanResources_MetaData -- used userid & pwd.
Actually i have to do UserMapping as my portal userid and R/3 userid are different.. Then in this case am i creating JCO destinations correctly.. If not how to do..
Please throw some light into this problem by your valuable suggestions.
Thanks & Regards,
Mahesh.M.R

Answer 1

Hi
I am having the exact same problem (i think). I believe that the problem is caused by a failed connection to the SLD.
In my case, if I scroll the bottom of the error page, the 'Detailed exception chain' has the error:
TypeBroker failed to access SLD: Error while obtaining JCO connection.
The same error can be found in the DefaultTrace.
This ESS is on a nw2004s sandbox portal (trying to reach an ECC 6.0 sandbox), but being lazy I just reused the SLD in my Development environment.
This is however a Java WAS 6.40 and according to Note 954820 (Compatibility of SLD in the system landscape)
QUOTE
In general, the connection of systems to the SLD is released for SLD client applications with releases earlier than or equal to the SLD release (to be more precise: the AS Java release on which the SLD runs). Within a release, all Support Packages are released.
UNQUOTE
So, i'll try activating the SLD on a nw2004s JAVA WAS and use that instead.
Regards
Stig