Cloudhouse Application Compatibility Package and Compatibility Container Exit Codes

Save to PDF

Applies to: Cloudhouse Application Compatibility Packages and Cloudhouse Compatibility Containers

05/05/2020 Cliff Hobbs   ID: 266774

Symptoms

If a Cloudhouse Application Compatibility Package (also known as 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 written to the relevant log file.

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

Resolution

To resolve issues with an Application Compatibility Package (ACP) failing to deploy or an application failing to launch:

  1. Copy the ACP from the source directory again, or try to restore the ACP from backup.
  2. If the ACP still fails to deploy or launch, then re-create the ACP which recreates 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 ACPs configuration files.

Please contact Cloudhouse Support if trying the above does not resolve the problem.

Source:
Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support