> For the complete documentation index, see [llms.txt](https://quannsstudios.gitbook.io/quannsstudio-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quannsstudios.gitbook.io/quannsstudio-docs/introduction/common-issues.md). # Common Issues **Script Transfers** If you need to move one of your purchased scripts over to a different account, the process is straightforward. Start by logging into the [Cfx.re Portal](https://portal.cfx.re/) and navigating to your [Granted Assets](https://portal.cfx.re/assets/granted-assets) page. From there, locate the resource you want to move and select the transfer option next to it. You'll be prompted to enter the username of the receiving account — once that's confirmed, the transfer will be processed. If anything goes wrong during this process, reach out through our Discord and we'll get it handled. *** **Missing Entitlement** If your server is throwing an entitlement error, there are a few things worth checking before reaching out for support. First, confirm that the FiveM account you used to purchase the script is the same one linked to your server. This is the most common cause of entitlement issues — if they don't match, use the transfer process above to move the script to the correct account. Second, make sure you've fully restarted your server since the purchase. A lot of people skip this step and wonder why nothing is working — a fresh restart is required for the script to be recognized. Third, check that your server's system time is accurate. Visit [Time.is](https://time.is/) and compare it to your server's local time. If there's a gap of more than a minute, correct your system clock and try again. *** **Syntax Error Near `<\1>`** This error almost always comes down to how the files were moved onto your server. If you used FileZilla without enabling binary transfer mode, or if you dragged files individually through Remote Desktop, the script's structure may have been corrupted during the move. The cleanest way to get files onto your server is to upload the zip directly and extract it server-side rather than transferring individual files. The other thing to check is your server build version. Quanns Studios scripts require version **4752 or higher** to run correctly. Open your server console and type `version` to see what you're currently on. *** **Updating Your Server Artifacts** Keeping your artifacts up to date is important for both compatibility and performance. Here's how to do it on each platform: **Linux** — Download the latest recommended build from the [Linux artifacts page](https://runtime.fivem.net/artifacts/fivem/build_proot_linux/master/). Shut your server down, remove the `cache` and `alpine` folders, then extract the new build using `tar -xf fx.tar.xz`. Start your server back up and run `version` in the console to confirm the update went through. **Windows** — Grab the latest build from the [Windows artifacts page](https://runtime.fivem.net/artifacts/fivem/build_server_windows/master/). Stop your server, delete the old server folder, and replace it with the freshly downloaded version. Restart and run `version` to verify everything updated correctly. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://quannsstudios.gitbook.io/quannsstudio-docs/introduction/common-issues.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.