> For the complete documentation index, see [llms.txt](https://snappy-scripts.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://snappy-scripts.gitbook.io/documentation/getting-started/escrow-errors.md).

# Escrow Errors

Fix Keymaster and asset escrow errors when a script won't start.

Snappy scripts are protected with FiveM asset escrow. If the server console shows an escrow error when the script starts, find it below.

## "You lack the required entitlement to use …"

The server's license key belongs to a different Cfx.re account than the one that bought the script.

1. Open [Keymaster](https://keymaster.fivem.net/) with the account that **bought** the script. Check it's listed under **Granted Assets**.
2. Under **Server Keys**, create or copy a key from **that same account**.
3. Put it in `server.cfg` as `sv_licenseKey` and restart the server.

{% hint style="info" %}
Bought on the wrong account? [Get support](/documentation/getting-started/support.md) with your Tebex transaction id (`tbx-…`).
{% endhint %}

## "Failed to verify protected resource"

The encrypted files were changed or damaged, usually during upload.

1. Download a fresh copy from [Keymaster](https://keymaster.fivem.net/).
2. Upload it again. If you use FTP, set the transfer mode to **binary**; text mode corrupts the encrypted files.
3. Don't edit any file other than the config files.

## The script doesn't start at all

* **Old server artifacts.** Update your server to a recent [artifact](https://runtime.fivem.net/artifacts/fivem/build_server_windows/master/).
* **Renamed folder.** Keep the resource folder named as downloaded (for example `snappy-phone`).
* **Missing dependencies.** Check the script's installation guide, for example [Phone → Installation](/documentation/paid-scripts/phone/installation.md).