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

This page will help you to troubleshoot fatal error you can face during the Set as current version.

1. Open the deployment log file that is in Set as current version log path CAST Management Studio - Information - How to find logs
2. Activate the DEBUG display option of the log file.
3. Search for the first Error message
4. Identify the deployment_deploy.CastLog2_[APP-GUID].CastLog2 log file :
   
5. Open the deployment_deploy.CastLog2_[APP-GUID].CastLog2
6. Activate the DEBUG display option of the log file.
7. Search for the FATAL Messages, ERROR messages and for DETAIL messages that are just before the ERROR message, like below screenshot :
   
   
   
8. Navigate to the below pages :
   
   • CMS Application - Delivery - Set as current version - Deploy source code - Fatal Error - Error occurred during initialization of VM
   • CMS Application - Delivery - Set as current version - Deploy source code - Fatal Error - Error occurred while communicating with remote log client
   • CMS Application - Delivery - Set as current version - Deploy source code - Fatal Error - java io FileNotFoundException Access is denied
   • CMS Application - Delivery - Set as current version - Deploy source code - Fatal Error - Not able to set as current version after rejecting already accepted version
   • CMS Application - Delivery - Set as current version - Deploy source code - Fatal Error - The Program Delivery Manager Tool has not ended correctly
   • CMS Application - Delivery - Set as current version - Deploy source code - Fatal Error - Unpackaging of sources failed during deployment
9. If you do not find the information you are looking for or solution for your problem, in this page,  contact CAST Technical Support with Delivery Manager Tool - Relevant Input for Support to reproduce.