cancel
Showing results for 
Search instead for 
Did you mean: 

Why do JCo destinations green in designtime, fail during runtime ?

Former Member
0 Kudos

Manually verified JCo destination, both ping and test works.

Ran the WebDynpro console sanity check tool. All tests green.

When the application then tries to create a Jco connection during runtime I get these logs in defaultTrace on EP:

Could not create JCOClientConnection for logical System: 'WD_BN_MODELDATA_DEST' - Model: 'class com.company.models.bn.BN'.

supplyCheckInfos ...Class casted to IExternalStandardCheckInterface is class com.sap.tc.webdynpro.check.jcodest.wdp.InternalJCODestAvailabilityCheckInterface$External

supplyCheckInfos ...Class cast issue CompUsage is class com.sap.tc.webdynpro.progmodel.components.ComponentUsage

Any suggestions ?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Make sure your metadata is updated in the model to that of the backend.

Regards

Ayyapparaj

Answers (1)

Answers (1)

Former Member
0 Kudos

Yes, this was indeed a metadata difference. The functionmodule had actually been removed from backend, which wasn't obvious in the exception.