Documentum CTS (Content Transformation Services) service error:
Below one is the common error that cause CTS service to stop.
ERROR
13:26:55,118 INFO [ main] CTSServerHandlerImpl - *************** Content Transformation 5.3 - Release Build 0.206 ICTSService Framework startup initiated. ***************
13:26:55,587 ERROR [ main] CTSServerHandlerImpl - Unable to start the default handler.
com.documentum.cts.exceptions.internal.CTSServiceManagerException: Unable to start the default handler.
Cause Exception was: A new instance of ICTSService with SUBTYPE = CTSPLUGIN could not be created
com.documentum.cts.exceptions.internal.CTSServiceException: Unable to start the default handler.
at com.documentum.cts.impl.services.CTSServiceBaseImpl.startAll(CTSServiceBaseImpl.java:930)
at com.documentum.cts.impl.services.CTSServiceBaseImpl.start(CTSServiceBaseImpl.java:565)
at com.documentum.cts.services.CTSServiceManager.getServiceBySubType(CTSServiceManager.java:545)
at com.documentum.cts.impl.services.ctsserver.CTSServerHandlerImpl.getMediaPluginHandler(CTSServerHandlerImpl.java:1165)
at com.documentum.cts.impl.services.ctsserver.CTSServerHandlerImpl.start(CTSServerHandlerImpl.java:559)
at com.documentum.cts.impl.services.CTSServiceBaseImpl.startAll(CTSServiceBaseImpl.java:925)
at com.documentum.cts.impl.services.CTSServiceBaseImpl.start(CTSServiceBaseImpl.java:565)
at com.documentum.cts.services.CTSServiceManager.registerServices(CTSServiceManager.java:268)
at com.documentum.cts.services.CTSServiceManager.bootstrapServiceFramework(CTSServiceManager.java:161)
at com.documentum.cts.services.CTSServiceManager.getInstance(CTSServiceManager.java:118)
at com.documentum.cts.services.ctsserver.CTSServerStartup.main(CTSServerStartup.java:107)
Enable the dmcl.trace in dmcl.ini
trace_file =
trace_lvel=
Cause: CTS not configured properly for one of the docbases.
Solution:
1. Find out the docbase from CTS logs
2. Delete the configuration for that docbase (make sure profiles are deleted from docbase under System/MediaServer)
3. Configure CTS for the docbase again
Below one is the common error that cause CTS service to stop.
ERROR
13:26:55,118 INFO [ main] CTSServerHandlerImpl - *************** Content Transformation 5.3 - Release Build 0.206 ICTSService Framework startup initiated. ***************
13:26:55,587 ERROR [ main] CTSServerHandlerImpl - Unable to start the default handler.
com.documentum.cts.exceptions.internal.CTSServiceManagerException: Unable to start the default handler.
Cause Exception was: A new instance of ICTSService with SUBTYPE = CTSPLUGIN could not be created
com.documentum.cts.exceptions.internal.CTSServiceException: Unable to start the default handler.
at com.documentum.cts.impl.services.CTSServiceBaseImpl.startAll(CTSServiceBaseImpl.java:930)
at com.documentum.cts.impl.services.CTSServiceBaseImpl.start(CTSServiceBaseImpl.java:565)
at com.documentum.cts.services.CTSServiceManager.getServiceBySubType(CTSServiceManager.java:545)
at com.documentum.cts.impl.services.ctsserver.CTSServerHandlerImpl.getMediaPluginHandler(CTSServerHandlerImpl.java:1165)
at com.documentum.cts.impl.services.ctsserver.CTSServerHandlerImpl.start(CTSServerHandlerImpl.java:559)
at com.documentum.cts.impl.services.CTSServiceBaseImpl.startAll(CTSServiceBaseImpl.java:925)
at com.documentum.cts.impl.services.CTSServiceBaseImpl.start(CTSServiceBaseImpl.java:565)
at com.documentum.cts.services.CTSServiceManager.registerServices(CTSServiceManager.java:268)
at com.documentum.cts.services.CTSServiceManager.bootstrapServiceFramework(CTSServiceManager.java:161)
at com.documentum.cts.services.CTSServiceManager.getInstance(CTSServiceManager.java:118)
at com.documentum.cts.services.ctsserver.CTSServerStartup.main(CTSServerStartup.java:107)
Enable the dmcl.trace in dmcl.ini
trace_file =
trace_lvel=
Cause: CTS not configured properly for one of the docbases.
Solution:
1. Find out the docbase from CTS logs
2. Delete the configuration for that docbase (make sure profiles are deleted from docbase under System/MediaServer)
3. Configure CTS for the docbase again