ADTS : [DM_VEL_INSTANTIATION_ERROR]error: "Cannot instantiate Java class"

com.documentum.cts.exceptions.internal.CTSProfileServiceException: [DM_VEL_INSTANTIATION_ERROR]error: "Cannot instantiate Java class"
Cause Exception was: Exception during updating profile cache document_to_pdf_dts

ADTS 6.0 6.0SP1 [DM_VEL_INSTANTIATION_ERROR]error: Cannot instantiate Java class

ID: esg93948
Product(s): Advanced Document Transformation Services
Related Bugs: 154355, 150077
SOLUTION

Symptoms

ADTS 6.0 6.0SP1 [DM_VEL_INSTANTIATION_ERROR]error: Cannot instantiate Java class. ADTS 6SP1 does not rendition documents.

The following error is thrown in the CTS log file:
com.documentum.cts.exceptions.internal.CTSProfileServiceException: [DM_VEL_INSTANTIATION_ERROR]error: "Cannot instantiate Java class"
Cause Exception was: Exception during updating profile cache transformEmlToPDF
DfException:: THREAD: Thread-10; MSG: [DM_VEL_INSTANTIATION_ERROR]error: "Cannot instantiate Java class"; ERRORCODE: 1902; NEXT: null
at com.documentum.services.dam.impl.transform.MediaProfile.initParameters(MediaProfile.java:417)
at com.documentum.services.dam.impl.transform.MediaProfile.getProfileNameAttr(MediaProfile.java:149)
at com.documentum.services.cts.impl.profile.CTSProfile___PROXY.getProfileNameAttr(CTSProfile___PROXY.java)
at com.documentum.cts.impl.services.ctsprofile.CTSProfileManagerImpl.createProfile(CTSProfileManagerImpl.java:1208)
at com.documentum.cts.impl.services.ctsprofile.CTSProfileManagerImpl.addInCache(CTSProfileManagerImpl.java:1060)

Caused by: DfServiceInstantiationException:: THREAD: Thread-10; MSG: [DM_VEL_INSTANTIATION_ERROR]error: "Cannot instantiate Java class"; ERRORCODE: 1902; NEXT: null
at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.loadModuleClass(ModuleManager.java:211)
at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.getModuleClass(ModuleManager.java:165)
at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.newModule(ModuleManager.java:120)
at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.newService(ModuleManager.java:89)
at com.documentum.fc.client.DfClient$ClientImpl.newService(DfClient.java:412)
at com.documentum.services.dam.impl.transform.MediaProfile.initParameters(MediaProfile.java:340)

Cause

ADTS 6.0/6.0SP1 is installed against the 5.3/5.3SPx repository without any D6 repository.

Resolution

Customers may tend to assume that D6 ADTS is fully backward compatible with the 5.3/5.3SPx repository and they may be misled due to a lack of accurate and explicit documentation. ADTS 6/6SP1 requires a D6 global registry to successfully get ADTS up and running. This in turn requires installing the D6 Content Server. Even if you follow the instructions in Bug 150077 and deploy Transformation and Rich_Media_Services docapps manually, ADTS will not work unless you have a D6 Global registry.

Per Support solution esg92090, this issue could be worked around by manually deploying the ctsTransformImpl.jar file locally in the BOF registry with the CTS host. Although esg92090 is proven to work, this method has not been tested by the CTS QA Team and is therefore not officially supported by CTS/ADTS Engineering.

A Documentation bug# 154355 is logged to include these details in the ADTS6/6SP1 Release Notes or Installation Guide.

Note: If you already have D6 installed with GR, the steps to resolve the same error are provided in support note esg98200.

SEE THESE SOLUTIONS ALSO:

esg92090 CTS 6.0 users need to have a D6 Global Repository
esg98200 DM_VEL_INSTANTIATION_ERROR --CTS docapps Tranformation and Rich media doesn't install properly