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

# Common Issues

Fixes for the problems that are not specific to one script.

Check these before opening a ticket. They cover most of what we see, whichever script you run.

## You lack the required entitlement to use \<resource>

The server's license key does not belong to the account that owns the script.

* Use a license key (`sv_licenseKey`) created on the **same Cfx.re account** that made the purchase, or transfer the asset to the account that owns the key in the [Cfx.re Portal](https://portal.cfx.re/assets/granted-assets).
* Just bought it? Restart the server completely. A resource restart is not enough for a new entitlement.

## Failed to verify protected resource / syntax error near <\1>

The encrypted files were damaged on the way to the server, or the server build is too old to read them.

* Upload the `.zip` and unzip it on the server, or set your FTP client's transfer type to **binary**. Text-mode transfers corrupt encrypted files.
* Update your server artifacts to a recent recommended build.
* Make sure the resource's `fxmanifest.lua` was not edited.

## The script starts but behaves as if there were no framework

Our scripts pick the framework and the target resource **when they start**. If the script starts before your framework, it does not see it.

* In `server.cfg`, `ensure` the script **after** the database resource, ox\_lib, your framework and your target resource.
* After fixing the order, restart the script (or the server).

## attempt to index a nil value (global 'lib') / No such export

A dependency is missing or starts too late.

* Install every dependency listed on the script's Installation page.
* Start them before the script.
* Keep ox\_lib up to date.

## Database tables are missing

Scripts that create their own tables do it on start, through oxmysql.

* Start oxmysql before the script and check that its connection string works (oxmysql prints an error on start if it does not).
* If a script ships an `.sql` file, import it once before the first start. The script's Installation page says which case applies.

## Nothing above helped

Open a ticket and bring the details listed on the [Support](/docs/getting-started/support.md) page.