> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jaksam-scripts.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Troubleshooting
> Common issues and how to fix them
If your error mentions the FiveM escrow system (for example "Failed to verify protected resource" or "You lack the required entitlement"), see the dedicated [Escrow errors](/jaksams-scripts/escrow-errors) page instead.
If your server crashes when starting the script, it means you are using an old version of the `mysql-async` script.
Fixing this issue is very simple and fast, you have 2 options:
**Strongly recommended.** Replaces `mysql-async` with improved performance and full compatibility, allowing an easy swap. Check the installation guide for details.
**Not recommended.** Install the updated script instead of your current `mysql-async`. Be sure to rename the script folder to `mysql-async`.
It may happen that if you have particular inventories, item addition or removal causes errors in server console.
In this case, to try fixing the issue try doing the following steps:
Go in the script folder in `integrations/sv_integrations.lua` file and set this option from
```lua theme={null}
SKIP_ITEM_EXISTS_CHECK = false
```
to
```lua theme={null}
SKIP_ITEM_EXISTS_CHECK = true
```
If the script has a `default_config.json` file, edit this option in the `"server"` section from
```json theme={null}
"canAlwaysCarryItem": false,
```
to
```json theme={null}
"canAlwaysCarryItem": true,
```
If the script has a `current_config.json` file (which is a different file from the previous one), edit the `canAlwaysCarryItem` option to `true` there as well.
If you don't have the `canAlwaysCarryItem` option, you simply need to add it. Be sure to add it at the **beginning** of the `server` part.
The item you are working on must exist to be used in the scripts. To be sure the item exists, you can try to give it to yourself.
Creating the item depends on your framework and/or on your inventory, so creating it will be up to you.
On ESX, it may happen for many reasons that you encounter the following error (in F8 console or in server console):
This usually happens because the script cannot find the *ESX shared object* of your `es_extended` script automatically.
To solve the issue, you have to find the shared object name of your `es_extended` script in the file `es_extended/client/common.lua`.
This is an example of what you can find (you may have something else):
After you found your *ESX shared object* name, you can manually set it in the files `integrations/sv_integrations.lua` **and** `integrations/cl_integrations.lua`, replacing `nil` with the name of your shared object **(between double quotes)**.
Do **not** replace the left side, only replace the right side.
An example:
## Related topics
- [How to](/jaksam-inventory/how-to-update.md)