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

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.

1. Open the deployment_deploy.castlog2_<package_uuid>.castlog2 log file in DEBUG display option.
2. Check the DETAIL Message that are before the ERROR message
3. If the DETAIL is containing the following message : Preparing to run Importer with process JVM to 2G like below screenshot :
   
   
   1. The CAST Management Studio is a 32 bits application and cannot run a process with memory higher than 1.2 GB. Then, it is expected to get a failure of the Set as current version when the memory configured in the DMT is 2 GB. The solution is to modify the configuration file where this information is stored.
      
   2. Change the jvmMemory value and set it to 1G.
   3. Save the file, it will save it in the zip file
   4. Run the set as current version again.
4. If the message are : Preparing to run Importer with process JVM to 1G and Could not reserve enough space for object heap like below screenshot :
   
   
   This means that the Java Runtime was not able to get enough memory to execute the process, and there is less than 1 GB free memory. The solution is to kill process to get more memory (at least more than 1 GB) and then run the Set as current version again.
   Make sure that you do not have any static memory settings, Xmx runtime parameter set which prevents in allotting the required memory for JVM. If yes, then you need to clear the Xmx runtime parameter to make it empty.
   See the attached below screenshot which points to the Xmx runtime parameter for Java settings.
   
   
5. If the above point do not help you, contact CAST Technical Support with Delivery Manager Tool - Relevant Input for Support to reproduce.