Cloudhouse Compatibility Container Exit Codes

Save to PDF

Applies to: Cloudhouse Containers

25/05/2019 Cliff Hobbs

Symptoms

If a Cloudhouse Compatibility Container™ fails to deploy or an application fails to launch, one of the following exit codes is returned to the console and log file.

CodeDescription
-1Invalid combination of command line options, or failed to parse arguments.
-2Missing Metadata configuration file - chmetadata.json
-3Missing Program configuration file - Program.xml
-4Missing Shortcut configuration file- Shortcut.xml
-5Missing Environment Variable configuration file - EnvironmentVariables.xml
-6Missing App registry configuration file - AppRegistry.xml
-7Missing File Type Association configuration file - FileAssociations.xml
-8Invalid Metadata configuration file - chmetadata.json
-9Invalid Program configuration file - Program.xml
-10Invalid Shortcut configuration file - Shortcut.xml
-11Invalid Environment Variable configuration file - EnvironmentVariables.xml
-12Invalid App Registry configuration file - AppRegistry.xml
-13Invalid File Type Association configuration file - FileAssociations.xml
-14Run Program Exception - Programs.xml
-15Exception: Missing run.exe.config, deploy.exe.config or usage.exe.config file
-16Missing EULA file in Container, copy EULA.html from the Auto Packager's install directory
-17Exception: EULA not accepted by during deployment, use /AcceptEULA
-18Invalid Usage Token: file is corrupt, or invalid. Replace the token in the container with a valid token.
-19Missing Reporting Token: The token cannot be found in the container. Check the token is in the Container's root
-20Invalid Configuration File – ComDeployment.xml
-21Invalid Configuration File – ComRegestryKeys.xml
-22Invalid configuration of services - Services.xml
-23Invalid DeploymentScript.xml

Resolution

To resolve issues with Containers failing to deploy or an application failing to launch:

  1. Copy the Container from the source directory again, or try to restore the Container from backup.
  2. If the Container still fails to deploy or launch, then re-create the Container. This will recreate any missing configuration files.
  3. Invalid XML configuration files (error codes -8 through to -13), typically occur when XML tags are malformed. This usually happens as a result of incorrect editing of the configuration files.

If the problem is not resolved by trying all of the above, Contact Cloudhouse Support.

Source:
Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support