ESS Leave request and few services stopped working?

[Former Member]

Hi,

I have recently made changes to one of the ESS DC (addresses) and deployed this DC to Dev system from NWDS using SDM password. The deployed DC has my changes and looks good, but rest of the servics are failing to open (e.g. Leave request), the dump is as below when opening most of the services, any idea why .. We have even restarted portal server but still no luck

com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Could not find target object com.sap.xss.ser.tecl.fctm.FcTmDataExchange with type com.sap.tc.webdynpro.progmodel.repository.IWDComponentInfo (Hint: Is it deployed correctly?).

at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:714)

at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)

at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)

at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)

at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)

Thanks

Praveen

[siddharthrajora]

You need to patch your Java engine? What is the sp level,

Through Content admin, does these services work?

[Former Member]

It ended up being deploy was running for more than 3 hours and completed. All of a sudden everything started working and we found that it's all due to deploy activity which was taking very long time.

Thanks

Praveen

[Former Member]

Can someone please confirm if ESS DC can be deployed from NWDS directly using SDM or should it be deployed by checkin, and activate release?

Thanks

Praveen