> ## 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

> Diagnose a product that fails at start or never appears on the server at all.

## Symptoms

One of the following, after adding a product to your server:

* the console reports an error naming the product, and the product never starts;
* the console says nothing about the product at all;
* the product is listed but nothing it provides works in game.

## Likely cause

Four causes account for almost every case, in the order they are worth checking:

1. **The SDK is missing, stopped, or a version the product does not accept.** A product checks this on
   its server side as it starts and stops itself when the check fails, so the resource ends up
   `stopped` with the reason on the line above.
2. **A resource the product needs is not running.** A product that needs a framework, an inventory
   or a database does not start without one.
3. **The resource directory is one level too deep.** Archives frequently unpack into a folder of
   their own. A server only sees a resource whose `fxmanifest.lua` is directly inside the resource
   directory.
4. **The resource is not in `server.cfg`**, or is listed before the resources it depends on.

## Resolution

<Steps>
  <Step title="Read the highest error line" icon="terminal">
    Find the first line naming the product or `element_sdk` and match it in [Console
    messages](/support/console-messages). The lines below it are usually consequences. If there is
    no line at all, the server never found the resource. Go to step 3.
  </Step>

  <Step title="Check the SDK" icon="cube">
    Confirm `element_sdk` is installed, is listed in `server.cfg` **before** the product, and is a
    version the product accepts:

    ```text theme={null}
    version element_sdk
    ```

    A `[Dependencies]` error tells you which of the three failed. See [SDK version
    requirements](/sdk/compatibility).
  </Step>

  <Step title="Check the directory layout" icon="folder-tree">
    ```text theme={null}
    resources/[element]/element_map/fxmanifest.lua
    ```

    That file must be at that depth. If you find `element_map/element_map/fxmanifest.lua`, move the
    inner directory up one level and delete the empty outer one.
  </Step>

  <Step title="Check the resources the product needs" icon="plug">
    A line of this shape means the product needs something your server does not run:

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

    Install one of the listed resources and make sure it starts **before** the product. The choice
    is made once, when the product starts, so starting the resource afterwards does not fix it. See
    [Supported server resources](/sdk/supported-resources).
  </Step>

  <Step title="Check server.cfg" icon="file-pen">
    ```cfg theme={null}
    ensure oxmysql
    ensure es_extended

    ensure element_sdk
    ensure element_map
    ```

    Everything the product uses comes before it. Then restart the server: a full restart, not a
    `refresh`.
  </Step>
</Steps>

## Verification

<Check>
  The console reports a clean start for `element_sdk` and for the product, with no `[ERROR]` or
  `[WARN ]` line naming either.
</Check>

If the product now starts but does nothing in game, the installation is complete and the problem is
elsewhere: check the product's own troubleshooting pages, and whether it ships an integration that
has not been installed. See [Product integrations](/concepts/integrations).