on 07-17-2008 9:19 AM
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 ?
Hi,
Make sure your metadata is updated in the model to that of the backend.
Regards
Ayyapparaj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, this was indeed a metadata difference. The functionmodule had actually been removed from backend, which wasn't obvious in the exception.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.