Cloudhouse Container Exit Codes

Symptoms

Cloudhouse Container fails to deploy, or application fails to launch, and returns an exit code to the console and log file.

Exit Codes

-1Invalid combination of command line options, or failed to parse arguments.
-2Missing Metadata configuration file
-3Missing Program configuration file
-4Missing Shortcut configuration file
-5Missing Environment Variable configuration file
-6Missing App registry configuration file
-7Missing File Type Association configuration file
-8Invalid Metadata configuraiton file
-9Invalid Program configuration file
-10Invalid Shortcut configuration file
-11Invalid Environment Variable configuration file
-12Invalid App Registry configuration file
-13Invalid File Type Association configuration file
-14Run Program Exception
-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
-18 Invalid 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

Solution

  1. Copy Container from source directory again, or try to restore 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 configuration files.
  4. Contact Cloudhouse Support.

Applies To

Cloudhouse Containers

Was this article helpful?

Can't find what you're looking for?

Contact Support