FivePD Not Starting? Diagnose Resource and Menu Errors

Start with the first error in the FXServer/txAdmin console. Do not replace core DLLs or reinstall a database to diagnose a menu that does not open. Confirm which layer fails, then test one change at a time.

This is a legacy FivePD troubleshooting workflow, not a verified fix for every FXServer version. The inspected legacy package declares a FiveM resource with client and server .NET assemblies. See FivePD release status and evidence before changing a working server.

Diagnose by symptom

Symptom	First action
Server reports it cannot find FivePD	Check the resource folder, manifest and name used by the server configuration.
Resource is found but does not start	Capture the first assembly, runtime, config or dependency error.
Resource starts but database operations fail	Identify SQLite versus MySQL from the installed root configuration.
Only F11/menu fails for one player	Check client F8 errors, duty/department eligibility and conflicts from other keybinds.
Base FivePD works, an add-on breaks it	Restore the known-good core and isolate the recently added DLL.
Calls never arrive despite a clean startup	Use the dedicated callout failure guide.

1. Confirm the correct resource folder

The intended FiveM resource folder must contain fxmanifest.lua at its top level, beside the files supplied with that package. Avoid accidental nesting after extracting a ZIP.

resources/
  fivepd/
    fxmanifest.lua
    FivePD_client.net.dll
    FivePD_server.net.dll
    config.json
    config/
    callouts/

This illustrates a layout present in the inspected mirror, not a file checklist for every distribution. When your actual resource directory is named fivepd, the server configuration normally includes:

ensure fivepd

According to the Cfx.re server commands reference, refresh rescans manifests, and ensure starts or restarts a resource when the command runs. Neither repairs damaged files nor guarantees compatibility.

2. Record the first startup error

In txAdmin or the FXServer console, restart the resource on a test server, then copy the first relevant error and a few surrounding lines. Do not guess at the cause from the final repeated error.

Check the installed fxmanifest.lua and confirm that expected dependencies and files actually exist. The legacy manifest distinguishes client scripts, server scripts and other files. An assembly load failure may arise from a missing dependency, wrong runtime, incompatible native library or a mismatched add-on.

Never download an arbitrary replacement .NET DLL advertised as a universal FivePD fix.

3. Check JSON and database initialization

The inspected v1.5 config.json uses a db selector with sqlite as the example value and a separate database object for MySQL connection settings. Before changing anything:

1. Record the installed version, selected database backend and relevant error.
2. Validate the current JSON. Restore the last working copy if its syntax is damaged.
3. For SQLite, check access to the actual database file and compatibility of its native library with the host OS.
4. For MySQL, verify the database is reachable from the server with dedicated least-privilege credentials.
5. Test persistence and recovery; do not run a fresh-install SQL file on a live database without inspecting its statements.

The detailed procedure is in FivePD database errors and the configuration reference.

4. F11 duty menu will not open

If the server reports a clean FivePD startup but a player sees no menu, first verify that the player belongs to a department: the legacy FivePD v1.5 controls document says department membership is required for menus and callouts. Next, check F8 client errors and server-specific keybind changes. A disabled menu option in config/menu.json can also explain a missing feature; it is not evidence that the entire resource failed to load.

Compare with another player before changing global files. See the controls and keybindings reference.

5. Isolate recently installed plugins or callouts

Return to the last known working configuration. Temporarily remove a newly added callout or plugin from the test instance, restart under controlled conditions and reproduce the base flow. Restore the add-on only after matching its published dependencies, API target and release notes. A source ZIP is not always a compiled release.

For callout-specific steps, read installing custom callouts. For plugins, see FivePD plugins and add-on installation.

6. Verify the fix and prepare a support report

Complete a test patrol: join, open duty, receive a callout, use the police computer if present, restart and verify the expected persistent data. Repeat with a second player when relevant.

If unresolved, share the first sanitized error, FivePD package source/version, FXServer build, OS, database choice, and which action reproduces it. Remove passwords, tokens, license keys, user data and connection strings before posting logs.