---
title: "Exiting with code -25"
description: "What exit code -25 from the Deployment Tool means and how to fix it."
product: "Alchemy"
edition: "Public"
type: "reference"
url: "https://docs.cloudhouse.com/public/troubleshooting-packages/errors/exit-codes/exit-code-25/exiting-with-code-25/"
---
# Exiting with code -25

**Problem**: When deploying a Compatibility Package, one of the following errors are displayed, each ending with `Exiting with code: -25`:

Applies to: `Alchemy`

- `Customer's licence has expired`.
- `The provided licence has expired`.
- `The provided licence is for a different version of this Package or the Package's configuration has been modified`.
- `The provided licence is not valid for this Package`.
- `The provided licence is not valid for this machine`.
- `The provided licence is not valid for this user`.
- `The provided licence does not allow deployment`.
- `The provided licence does not allow running`.

Example: `ERROR Cloudhouse.Container.Deployment. Program - Failed:
 Cloudhouse.Container.Core.Exceptions.DeploymentValidationException: Could not authorise deployment with the provided token. Customers license has expired.
ERROR Cloudhouse.Container.Deployment. Program - Exiting with code: -25`.

**Solution**: If you receive an error ending with `Error with code: -25` when deploying an Alchemy Compatibility Package, it means your license is invalid. To troubleshoot this error:

1. Enable DEBUG logging as detailed in the [Configuring DEBUG Logging](https://docs.cloudhouse.com/public/troubleshooting-packages/logging/configuring-logging/configuring-logging/index.md#configuring-debug-logging) section of [Configuring Logging](https://docs.cloudhouse.com/public/troubleshooting-packages/logging/configuring-logging/configuring-logging/index.md).
2. Generate a new license for the customer by following the relevant Licensing Workflow as detailed in [Licensing and Usage Reporting](https://docs.cloudhouse.com/public/licensing-and-reporting/licensing-and-usage-reporting-overview/index.md).

!!! tip

    Please contact Cloudhouse Support for assistance if you encounter this error.