Knowledgebase
Welcome Guest! Please log-in to access all of our functions.

Billing Center

Failed to check session lock

At random, your server might not start and appear like it’s crashing, and if you look in your console and server log you will see this error:
net.minecraft.server.WorldConlictException: Failed to check session lock, aborting

To fix this:
1. Stop your server.

2. Access your files and go into your main world’s folder.

3. Delete the session.lock file you see.

4. Start your server and it should start up with no issues.
Was this answer helpful?

Also Read

Common Errors and Fixes (Views: 1123)
These are common issues that you may have with your server and how to solve them:"Can't connect to Minecraft bridge" or "Intermittent connection issues to your node. (auth:...
Failed to bind to port (Views: 416)
[WARNING] **** FAILED TO BIND TO PORT!This issue is caused when your server isn't properly stopped (typically a crash) and the process continues running in the background...
Login Temporarily Blocked (Views: 3285)
Login temporarily blocked is an error that is caused when you use the incorrect login info.Note two things:1) You were sent an email when you bought your server with the correct...
JSON - Exception in server tick loop (Views: 2943)
If you find your server not starting up with the following error: java.lang.NullPointerException: Exception in server tick loop at...
Crashing every time a specific player joins (Corrupted Chunk) (Views: 1939)
If your server crashes every time a specific player joins, it is likely that the player is in a corrupted chunk. To temporarily fix the issue:1) Identify the player's UUID. Do...

Powered by WHMCompleteSolution