Problems

A problem that only affects one resource is on that resource's own page.

The resource does not start

Read the console line under the resource name. It says which file it stopped on.

A typo in Config.Framework.name reads differently depending on the resource. ktx_garages names the file it looked for:

[ktx_garages] Framework adapter not found: bridge/server/esxx.lua

ktx_cases, ktx_fishing and ktx_dispatch name the values they take:

[ktx_cases] Unknown framework "esxx". Available: esx, qb-core, qbox, ox, custom.

Allowed are esx, qb-core, qbox, ox and custom.

[ktx_dispatch] public/framework.lua is missing: getPlayerJob

A custom adapter without every function it needs. ktx_garages says the same in its own words, see Frameworks. The file lists them.

It starts and nothing happens

Load order. ox_lib and oxmysql have to be ensured before the resource, see Install.

If the order is right, set Config.Debug = true and restart. Every step is printed with what it decided, which is normally enough to see where it stops.

Database errors on the first start

oxmysql is not running, or it is running without a connection string. The resource creates its tables on start, so a missing database shows up on the first query.

No notifications

Config.UI.name is custom and public/ui.lua is still empty. See Notifications.

ox_lib itself is not a candidate. It stands in the dependencies block of all four, so a server that does not start it does not start the resource either, and the console says so.

Jobs are not recognised

The adapter returns the job name your framework has, not its label. What the config compares against is compared as it stands, so police and Police are two different jobs. Spell it the way it stands in your jobs table.