Cloudhouse Application Compatibility Package and Compatibility Container Exit Codes

Save to PDF

Applies to: Cloudhouse Application Compatibility Packages and Cloudhouse Compatibility Containers

29/06/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 "Failed to parse command line arguments: Invalid argument combination"
-2 "Package metadata file <path>\chmetadata.json is not found in package directory."
-3 "The specified configuration file does not exist. '<path>\Programs.xml'"
-4 "The specified shortcuts configuration file does not exist. '<path>\Shortcuts.xml'"
-5 "The specified environment variables configuration file does not exist. '<path>\EnvironmentVariables.xml'"
-6 "App registry file <path>\AppRegistry.xml not found"
-7 "FileAssocation keys file <path>\FileAssociations.xml not found."
-8 "Can not parse package metadata from file <path>\chmetadata.json '<path>\chmetadata.json'"
-9 "The programs file contains invalid XML. '<path>\Programs.xml' ---> System.Xml.XmlException: Root element is missing"
-10 "The shortcuts file contains invalid XML. '<path>\Shortcuts.xml' ---> System.Xml.XmlException: Root element is missing"
-11 "The environment variables file contains invalid XML. '<path>\EnvironmentVariables.xml' ---> System.Xml.XmlException: Root element is missing."
-12 "App registry file <path>\AppRegistry.xml contains invalid xml '<path>\AppRegistry.xml' ---> System.Xml.XmlException: Root element is missing."
-13 "The specified file associations file is invalid '<path>\FileAssociations.xml' ---> System.Xml.XmlException: Root element is missing."
-14 Run Program Exception - Programs.xml
-15 Exception: Missing run.exe.config, deploy.exe.config or usage.exe.config file
-16 "EULA file <path>\eula.html is not found in package 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 "Container has no container token files."

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