Failed to resolve JCO destination name

[krishg]

When I run my dynpro application, I am getting the above error.

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException:
Failed to resolve JCO destination name 'WD_RFC_META' in the SLD. No such JCO
destination is defined in the SLD.

    at

com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:420)

    at

com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:243)

    at

com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:228)

    at

com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:84)

    at

com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:151)

    ...

70 more

As far as i can see it is happening the preprocessing phase.

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was

thrown in preprocessing phase of application session

I have migrated my old ARFC1 to ARFC2 model and created the destination in NWA and did not create my JCO destination in webdynpro admin. When I went and created the WD_RFC_META, the application ran fine. Please do note I created only the META destination in JCO and it worked (application destination still exist only in NWA)

Just curious if I am missing the migration steps? or did my migration fail (I no longer have the context menu to migrate to ARFC2). I am not familiar enough with this dynpro to recreate the model.Only difference between my other applciations is that sap.authentication is turned on for this application (application properties).  other application did not have it turned on and there was no problem migrating to ARFC2

[ErvinSzolke · Accepted solution]

Hi Krish,

have a look at the guide about migration from ARFC to ARFC2 to see whether you missed any steps:

http://scn.sap.com/docs/DOC-2594

Regards,

Ervin

[krishg · Accepted solution]

Jun,

I justed deleted my JCO destination from webdynpro admin content and it is working..I will test the changes again tomorrow (or after a system restart) and close this thread (if I don't have that error again).

[krishg · Accepted solution]

As I had indicated earlier, I removed the JCO destination (SLD) from webdynpro admin.  I had tested the dynpro using Technical user (backend user) and it worked.

I decided to change the model to use single sign on (as I have some authorization checks in background). it worked and i thought problem solved.

and then the trouble started, the next day... I got the following error,

Unable to connect to the backend - error: Typed model execution failed; see nested exception for details: JCO Exception occured while exceution of the ARFC2 Executable Model Object for destination '{0}': System received an expired SSO ticket on server

When I changed my model destination back to Technical user, the error went away.. I see lot of users have reported this exception in SDN and one person solved it by going to technical user. Wondering if this is correct? it works for 8 hours (using the single sign on user) and then after 8 hours, when I log back in, it fails.

Edited

Okay, after researching OSS note, there is a note.

1929964  Typed model execution failed; see nested exception for details


For metadata RFC destination, need to use "Technical User" option so as to 
log on ABAP with one specific user. For the other RFC destination, need to use 
"Current User(Assertion ticket)". If choose "Current User(Logon Ticket)", "Typed 
model execution failed" error happens intermittently even if time of JAVA and 
ABAP systems are synchronized. Please refer to note 1166904 
- Assertion ticket SSO for Web Dynpro Java JCO Destinations for more 
details. 

I have changed my destination to use Assertion ticket , but it did not work. May be I need to restart. will keep you posted.

[junwu · Accepted solution]

please check if there is any time difference between the java and abap server

[krishg · Accepted solution]

I am still getting an error after the system has been restarted. I am going to try to synch 'SessionExpiry' and single sign on (though i thought it was not required for assertion ticket)

Could you please elaborate when you say "please check if there is any time difference between Java and ABAP"? How do i check that?

[junwu · Accepted solution]

the sso never worked or not working after every 8 hours?

check

[krishg · Accepted solution]

When I set it to 'Technical User', it worked. When I changed it to SSO user, I do not get an error immediately. But the next day, when I log on , I get this error.

To answer your question, it has not worked after I changed it to SSO (and we have restarted our system after changing it to SSO)

As per the OSS note, that I had indicated earlier, I used the "Current user (assertion ticket)".

I am now trying to set my Sessionexpiration to same as SSO expiry.

[krishg · Accepted solution]

Just frustrating.. I am getting my original error back. I had set my session expiration time to same as SSO expiry time and restarted our system.

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException:

Failed to resolve JCO destination name 'WD_RFC_META' in the SLD. No such JCO

I have other webdynpro apps using other jco destinations (and they don't give this error). and I am getting this error even before application processing (so this error goes away when I created META destination in SLD) and only for META destination. model destination works in JCO.

The one strange thing I noticed; my other applications which works has the following zip file "com.sap.tc.arfc2.modeltype.content" in the public folder of the DCs (_comp->gen->default->public->compname->lib->java

While the application that does not work do not have this zip file. I am very hesitant to re-create the model (I have re-imported), as I am not completely familiar with this application.

[krishg · Accepted solution]

I changed the name of my Destination (both for model and meta) .. validated that destination name is updated everywhere.. My application still fails 'Unable to resolve the JCO destination WD_RFC_META in sld' even after changing the meta data destination name..

and for the first time, WD_RFC_MODEL shows up in the JCO references (in the webdynpro admin). it never did that previously.

[Former Member · Accepted solution]

I had the same error that was fixed by creating new model with ARFC2.  Sorry...  we didn't seem to have a better solution for this migration issue.

[Former Member · Accepted solution]

HI Krish,

Even we are faced this issue, we solved this by adding. As"providerFactoryName="com.sap.dictionary.runtime.ProviderFactory4J7" value in *.dtlogicalddic files for every DC.

As per my knowledge there is some problem with nwds, it is not modifying required *.dtlogicalddic files properly. So we manually modified *.dtlogicalddic files in each DC's

Check in your DC "providerFactoryName="com.sap.dictionary.runtime.ProviderFactory4J7" value is available in all *.dtlogicalddic files, if not follow the below steps.

Go to Navigator view.

Follow the below steps for every DC,

     a.Select the DC and find all the available *.dtlogicalddic files.

     b.Open the *.dtlogicalddic file.

     c.Add text

     (providerFactoryName="com.sap.dictionary.runtime.ProviderFactory4J7")

     after (name="...") and before (package="...").

Make sure providerFactoryName added in all the *.dtlogicalddic files.

Perform DC build.

Deploy.

regards,

Rakesh Mathew

[Former Member · Accepted solution]

I have followed your instructions. To get it working I had to restart my server.

Nevermind, thanks a lot! This solved my problem.

Cheers
Klaudio

[krishg · Accepted solution]

Rakesh, my files had the correct value in there already..

[krishg · Accepted solution]

Hi ,

I noticed the following warning in my build log..

[cda] No component dependency exists for reference to "tc~cm~arfc2" (sap.com).

  [cda] Collecting modules ...
  [cda] Missing deploy-time dependency for hard runtime reference to "tc~cm~arfc2" (vendor "sap.com").

I do not have the above module listed in component properties as dependency(though - project -> properties-> webdynpro -> LIbrary reference contains the above component). Is this causing the above issue (looking for the SLD jco destinations)? Any way to remove this if it is no longer required?

Okay, I was able to remove that component, but it does not appear related to this issue. it is still looking for sld references.

Krish

[junwu]

all should be in nwa destinations

maybe try restarting