CMS Application - Delivery - Set as current version - Deploy source code - Fatal Error on Documentation - V2

CMS Application - Delivery - Set as current version - Deploy source code - Fatal Error - Error occurred during initialization of VM

Mon, 01 Jan 0001 00:00:00 +0000

*Purpose

This page will help you to troubleshoot the fatal error “Error occurred during initialization of VM” that is diplayed in the deployment_deploy.castlog2_<package_uuid>.castlog2 log file.

*Observed in CAST AIP

Release	Yes/No
8.3.x	✅

*Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Action Plan

Open the deployment_deploy.castlog2_<package_uuid>.castlog2 log file in DEBUG display option.
Check the DETAIL Message that are before the ERROR message
If the DETAIL is containing the following message : Preparing to run Importer with process JVM to 2G like below screenshot :

CMS Application - Delivery - Set as current version - Deploy source code - Fatal Error - Error occurred while communicating with remote log client

Mon, 01 Jan 0001 00:00:00 +0000

Description

When setting as current version in CMS, the following errors are seen in the CAST-MS log, Refer to the page CAST Management Studio - Information - How to find logs to locate this log.This error causes the operation to stop:

An error has occurred while communicating with the remote log client. The error is as follows

Insufficient system resources exist to complete the requested service

com.castsoftware.util.logger.exceptions.FatalLogException

Here’s the full list of messages captured in the log:

CMS Application - Delivery - Set as current version - Deploy source code - Fatal Error - java io FileNotFoundException Access is denied

Mon, 01 Jan 0001 00:00:00 +0000

Description

On accepting the delivery and setting as current version,we get the error FATAL Unpackaging of sources failed during deployment java.io.FileNotFoundException:[PATH_OF_THE_FILE] (Access is denied)

On checking the Castlog2 file,you can find the error like

java.io.FileNotFoundException: …..\Thumbs.db (Access is denied)

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Step by Step Scenario

Package and deliver the application
Set as current version

Action Plan

Check if the sources are already present at the location where you are trying to deploy.Remove all the source codes from the deployment folder path and then accept delivery and set as current version.It is an expected behaviour.
If the error is java.io.FileNotFoundException: thumbs.db Access is denied
**About Thumbs.db file:**It stores graphics, movie, and some document files then generates a preview of the folder contents using a thumbnail cache.These folders are generated automatically by Windows so that folder content doesn’t need to be recalculated every time the folder is viewed.Thumbs.db files are stored in each directory that contains thumbnails on Windows systems. The file is created locally among the images, however, preventing system wide use of the data and creating additional data load on removable devices.
We can ignore these types of files while extraction.To ignore the following files you can use the below regular expression while packaging the code.
It is mentioned in the below page: Delivery Manager Tool - Information - File Types and folders which can be ignored

Impact on Analysis Results and Dashboard

CMS Application - Delivery - Set as current version - Deploy source code - Fatal Error - Not able to set as current version after rejecting already accepted version

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page outlines the issue of not able to set as current version after rejecting the package which is already accepted.

Refer the below error message:

Error: DETAILPreparing to run Importer with process JVM to 1G
            DETAILDefining Log server thread as a new logging context without any writers
            DETAILError occurred during initialization of VM
            DETAILCould not reserve enough space for object heap

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

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

Mon, 01 Jan 0001 00:00:00 +0000

Description

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).

CMS Application - Delivery - Set as current version - Deploy source code - Fatal Error - Unpackaging of sources failed during deployment

Mon, 01 Jan 0001 00:00:00 +0000

*Purpose

This page will help you to solve the fatal error “Unpackaging of sources failed during deployment java.io.FileNotFoundException: [path] (The system cannot find the path specified)” which is diplayed in the deployment_deploy.castlog2_<package_uuid>.castlog2 log file.

*Observed in CAST AIP

Release	Yes/No
8.3.x	✅

*Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Action Plan

Check that you have access to the path specified in the deployment_deploy.castlog2_<package_uuid>.castlog2 log file.
If you have no access to the path specified in the log, define the path, or change the deployment folder path in CAST Management Studio, in the preferences as described in CMS - Preferences - Platform Settings