CMS Application - Delivery - Set as current version - Deploy source code - Fatal Error - The Program Delivery Manager Tool has not ended correctly

This page outlines the error that is encountered when we try to accept the delivery.

When you set as current version, you might face the below mentioned error

 ERROR The program Deployment Deploy has not ended correctly (2001).
 DETAIL     Please see the DMT log and/or the program log for further details
 DETAIL     com.castsoftware.dmt.model.tasks.utilities.CommandLineTask.handleReturnCode(CommandLineTask.java:177)
 DETAIL     com.castsoftware.dmt.model.tasks.utilities.CommandPluginTask.handleReturnCode(CommandPluginTask.java:92)
 DETAIL     com.castsoftware.dmt.model.tasks.utilities.CommandLineTask.executeProcess(CommandLineTask.java:341)
 DETAIL     com.castsoftware.dmt.model.tasks.utilities.CommandLineTask.documentExecute(CommandLineTask.java:318)
 DETAIL     com.castsoftware.mda.impl.MemoryTask.execute(MemoryTask.java:82)
 DETAIL     com.castsoftware.java.treatment.Task.run(Task.java:275)
 DETAIL     com.castsoftware.java.treatment.Task.runChildren(Task.java:388)
 DETAIL     com.castsoftware.mda.impl.MemoryAction.execute(MemoryAction.java:253)
 DETAIL     com.castsoftware.mda.impl.MemoryAction.topExecute(MemoryAction.java:246)
 DETAIL     com.castsoftware.mda.transactions.SectionAction.runInternal(SectionAction.java:44)
 DETAIL     com.castsoftware.mda.transactions.Section.runInTransaction(Section.java:192)
 DETAIL     com.castsoftware.mda.transactions.Section.run(Section.java:137)
 DETAIL     com.castsoftware.mda.transactions.Section.runHeadless(Section.java:308)
 DETAIL     com.castsoftware.mda.run.ConfigurationManager.runVerb(ConfigurationManager.java:512)
 DETAIL     com.castsoftware.mda.run.ConfiguredApplication.onTreatment(ConfiguredApplication.java:386)
 DETAIL     com.castsoftware.deliverytool.CLI.onTreatment(CLI.java:98)
 DETAIL     com.castsoftware.mda.run.ConfiguredApplication$2.call(ConfiguredApplication.java:238)
 DETAIL     com.castsoftware.mda.run.ConfiguredApplication$2.call(ConfiguredApplication.java:1)
 DETAIL     com.castsoftware.util.logger.Logging.execute(Logging.java:500)
 DETAIL     com.castsoftware.util.logger.Logging.runInNewContext(Logging.java:389)
 DETAIL     com.castsoftware.mda.run.ConfiguredApplication.run(ConfiguredApplication.java:227)
 DETAIL     com.castsoftware.deliverytool.CLI$1.call(CLI.java:41)
 DETAIL     com.castsoftware.deliverytool.CLI$1.call(CLI.java:1)
 DETAIL     com.castsoftware.util.logger.Logging.execute(Logging.java:500)
 DETAIL     com.castsoftware.util.logger.Logging.runInNewContext(Logging.java:389)
 DETAIL     com.castsoftware.deliverytool.CLI.main(CLI.java:32)
 DETAIL     sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 DETAIL     sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 DETAIL     sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 DETAIL     java.lang.reflect.Method.invoke(Method.java:606)
 DETAIL     com.castsoftware.bootstrap.JarBootstrap.executeMain(JarBootstrap.java:529)
 DETAIL     com.castsoftware.bootstrap.JarBootstrap.main(JarBootstrap.java:755)
 DETAIL Task message: The program Deployment Deploy has not ended correctly (2001).

You will find this error in the DMT Deploy log file.

Refer the page to find the log path: How to find logs

1. Package and Deliver the source in DMT.
2. Launch CMS and select the application to be managed.
3. Accept the delivery
4. Set as current version.

This issue here is, due to large database extraction. The system was taking too much memory or other system resources. Hence the Accept Delivery was throwing an error message.

So the solution is,

1. Instead of doing the extraction during the set as current version step, it is to be done outside of CAST using the offline database extractor GUI/CLI (basically using the CAST-DatabaseExtractor.jar). This way we can also control the memory being used and increase it to something that your machine can handle. To find the offline database extractor tool, click here CAST_DB_Extractor_2.0.0-beta1.zip How to use it, refer this page CAST Database Extractor
2. Once the files are extracted, then you can deliver them directly through DMT (Reuse existing CAST delivery output in DMT) so that the set as current version does not do the extraction work again.
   

Impact of issue: Delivery can't be accepted and is marked as current version in CMS.

Impact after applying solution: No error encountered after the changes done.