> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementlabs.net/llms.txt
> Use this file to discover all available pages before exploring further.

# A product does not start

> The product reports an error at start, stops right after starting, or never appears at all.

## Symptoms

One of these, after adding or updating a product:

* the console shows an error naming the product, and it stops;
* the console shows `Started resource …` for the product and then `Stopping resource …`;
* the server says it could not find `element_sdk`;
* the console never mentions the product at all;
* the product is running but nothing it adds works in game.

## Causes

In the order worth checking:

1. **`element_sdk` is missing, or a version the product does not accept.** The product checks it at
   start and stops when the check fails.
2. **A resource the product needs is not running**, or starts after it: a framework, an inventory or
   a database.
3. **The folder is one level too deep.** The archive extracted into a folder of its own, so the
   server cannot see the resource.
4. **The product is not in `server.cfg`.**
5. **Your server's license key belongs to a different Cfx.re account** than the one that bought the
   product.
6. **The product needs its integration** and it was not installed. The product starts, but a
   feature that relies on your other resources does nothing.

## Fix

**1. Read the first error line**

Restart the product (`restart element_3d_pausemenu`) and find the first line naming it or
`element_sdk`. Look it up in [Console messages](https://docs.elementlabs.net/troubleshooting/console-messages.md). If there is
no line at all, go to the folder check below.

**2. Check element\_sdk**

`element_sdk` is installed, listed in `server.cfg`, and its version (the `version` line in
`element_sdk/fxmanifest.lua`) is inside the range the product's `INSTALL.md` names. A
line starting `[ERROR] [Dependencies]` says which of the three failed. See
[Versions and releases](https://docs.elementlabs.net/compatibility/versions.md).

**3. Check the resources the product needs**

A line like this means one is missing:

```text theme={null}
[ERROR] [FrameworkAdapter] No supported Framework adapter detected. Checked: [es_extended, qb-core, qbx_core]
```

Install one of the listed resources and start it **before** the product. See
[Supported resources](https://docs.elementlabs.net/compatibility/supported-resources.md) and
[Start order](https://docs.elementlabs.net/configure/start-order.md).

**4. Check the folder**

This file must exist at exactly this depth:

```text theme={null}
resources/[element]/element_3d_pausemenu/fxmanifest.lua
```

If you find `element_3d_pausemenu/element_3d_pausemenu/fxmanifest.lua`, move the inner folder up
one level and delete the empty outer one.

A product that came with an `_assets` folder needs it beside, at the same depth:

```text theme={null}
resources/[element]/element_3d_pausemenu_assets/fxmanifest.lua
```

Without it the console says it could not find the dependency `element_3d_pausemenu_assets`, and
the product does not start.

**5. Check server.cfg**

```cfg theme={null}
ensure element_sdk
ensure element_3d_pausemenu_assets
ensure element_3d_pausemenu
```

The resource name is the folder name. Then restart the server fully, not with `refresh`.

**6. Check the license key**

The `sv_licenseKey` in your `server.cfg` must come from the Cfx.re account that bought the
product. See [Licensing](https://docs.elementlabs.net/policies/licensing.md).

**7. Check the integration**

If the product starts but a feature that uses your other resources does nothing, check whether
its `install` folder has installer files. If it does, see
[Install an integration](https://docs.elementlabs.net/get-started/integrations.md).

## Check that it worked

> [!TIP]
>
> The console shows the product and `element_sdk` starting, with no `[ERROR]` or `[WARN ]` line
> naming either, and no `Stopping resource` line after them.

If it starts but a feature does not work, the installation is done: see the **Troubleshooting**
group in the product's own tab.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.