Client Error Knowledge Base

The server cannot be reached: offline, restarting, wrong IP/port, firewall or network issue.

The client is already trying to connect to a server.

There is already an unacknowledged error dialog on the screen.

The client state does not allow a new connection: it is already connecting or already in-game.

The session GUID is empty or invalid.

Server and client version or build do not match.

The client build is lower than the requiredBuild value in serverDZ.cfg.

The client build is higher than the allowedBuild value in serverDZ.cfg.

The client is missing DLC required by the server.

An empty password was submitted for a password-protected server.

The server is password-protected; this is a technical state, not always a normal error dialog.

When using BattlEye, the client has not accepted the BE license yet.

The account or character is already active on another server.

A communication timeout occurred during connection.

The player is already on this server.

Unknown or fallback error. This also appears when no more specific code is registered.

Wrong server password.

The server has already seen the connection attempt, so fresh server logs are especially useful.

With forceSameBuild enabled, server and client build are not identical.

The server has already seen the connection attempt, so fresh server logs are especially useful.

General or unknown server-side connection error.

The server has already seen the connection attempt, so fresh server logs are especially useful.

The server is full.

The server has already seen the connection attempt, so fresh server logs are especially useful.

Forbidden or invalid file patching state.

The server has already seen the connection attempt, so fresh server logs are especially useful.

The client is already connected.

The server has already seen the connection attempt, so fresh server logs are especially useful.

Host address resolution failed.

The server has already seen the connection attempt, so fresh server logs are especially useful.

The client could not create a NetChannel.

The server has already seen the connection attempt, so fresh server logs are especially useful.

The connection operation itself failed.

The server has already seen the connection attempt, so fresh server logs are especially useful.

Player request failed.

The server has already seen the connection attempt, so fresh server logs are especially useful.

Player creation failed.

The server has already seen the connection attempt, so fresh server logs are especially useful.

Network packet timeout.

The server has already seen the connection attempt, so fresh server logs are especially useful.

UID lookup failed.

The server has already seen the connection attempt, so fresh server logs are especially useful.

The server could not create a NetChannel.

The server has already seen the connection attempt, so fresh server logs are especially useful.

Session activation failed.

The server has already seen the connection attempt, so fresh server logs are especially useful.

The server is locked by an admin.

The server has already seen the connection attempt, so fresh server logs are especially useful.

The server is shutting down or disconnecting players because of shutdown.

The server has already seen the connection attempt, so fresh server logs are especially useful.

The client build is older and must be updated.

The server has already seen the connection attempt, so fresh server logs are especially useful.

The client build is newer; the server must update or the player must wait for a compatible server.

The server has already seen the connection attempt, so fresh server logs are especially useful.

The client version is lower.

The server has already seen the connection attempt, so fresh server logs are especially useful.

The client version is higher.

The server has already seen the connection attempt, so fresh server logs are especially useful.

With equalModRequired enabled, server and client mod lists do not match.

The server has already seen the connection attempt, so fresh server logs are especially useful.

The client uses the Diag executable, but the server does not.

The server has already seen the connection attempt, so fresh server logs are especially useful.

The server uses the Diag executable, but the client does not.

The server has already seen the connection attempt, so fresh server logs are especially useful.

The client did not obtain a device ID.

The server has already seen the connection attempt, so fresh server logs are especially useful.

Unknown or fallback error. This also appears when no more specific code is registered.

The server has already seen the connection attempt, so fresh server logs are especially useful.

The client is already trying to connect to a server.

The client is already trying to connect to exactly this server.

Unknown or fallback error. This also appears when no more specific code is registered.

The server disconnects the client as part of its final shutdown attempt.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

RCON/admin kicked everyone.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The server kicked everyone.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Network packet timeout.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Normal logout, not a real error.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Generic kick, often with extra text or a BattlEye reason.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The player is banned.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Kick caused by too high ping.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Modified or corrupted client data or installation.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The internet connection is too unstable.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The server is shutting down or disconnecting players because of shutdown.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The player is not whitelisted.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

No identity arrived during player creation.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

There is no input interface for the player.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Invalid UID during identity creation.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Bank/PBO bank count changed; integrity is suspicious.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Kick by an admin.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Invalid player ID.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The client sent a physically impossible amount of input.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The player closed the game; no error dialog.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The player left with the Leave button; no error dialog.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

General LoginMachine fallback error.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Too much time spent in one LoginMachine state.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The player was assigned, but identity has not been created yet.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The same UID is trying to log in while the old session has not fully exited.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Login or database error (Db Ping Response). Check server-side login and database logs.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Login or database error (Db Identity). Check server-side login and database logs.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Login or database error (Db Timeout). Check server-side login and database logs.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Login or database error (Db Bad Version). Check server-side login and database logs.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Login or database error (Db Error). Check server-side login and database logs.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Login or database error (Db App Error). Check server-side login and database logs.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Login or database error (Db App Exit). Check server-side login and database logs.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Login or database error (Db Bad Data). Check server-side login and database logs.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Login or database error (Db Get Response). Check server-side login and database logs.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Player was not created on the server.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Create New Client in Client kick. Check the full error text and fresh client/server logs.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Create Loaded Char in Client kick. Check the full error text and fresh client/server logs.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Load Loaded Char in Client kick. Check the full error text and fresh client/server logs.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

No network info exists for the player.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Create Ready Client in Client kick. Check the full error text and fresh client/server logs.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

No reconnect info exists.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

No reconnect identity exists.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

No reconnect character exists.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The account or character is already active on another server.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

BIOS/online service communication error.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Respawn or character state could not be processed correctly (Init Respawn Identity).

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Respawn or character state could not be processed correctly (Respawn Identity).

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Respawn or character state could not be processed correctly (New Respawn Network).

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Respawn or character state could not be processed correctly (New Respawn Identity).

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Respawn or character state could not be processed correctly (New Respawn Info).

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Respawn or character state could not be processed correctly (Respawn New Client).

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

General player verification fallback error.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

No player info exists.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Corrupted data prevents verification.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

General verification error.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Unknown verification error.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Data received by the server is corrupted or cannot be decompressed.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The client is missing a mod that exists on the server.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The client has a mod that the server does not use.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Client installation or mod is corrupted.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Server installation or mod is corrupted.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The client has an unexpected PBO that is not part of the server.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Unexpected or foreign PBO on the client side.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Extra PBO is likely caused by a newer client mod version.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Extra PBO is likely caused by a newer server mod version.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The source of the extra PBO cannot be determined.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Patched or modified PBO on the client.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Corrupted file or integrity error.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The .bisign file is missing for a PBO.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Missing PBO.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Missing PBO of unknown origin.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Missing PBO is likely caused by a newer client mod version.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Missing PBO is likely caused by a newer server mod version.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Server-side installation or mod is corrupted.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Client-side installation or mod is corrupted.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The source of the missing PBO cannot be determined.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Client and server .gproj files do not match.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Server and client are using different PBO files.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Server and client PBO versions are different.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The client PBO is newer.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The server PBO is newer.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

General authentication fallback error.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

User not found.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Authentication error (Auth Invalid Steam Validate). Check Steam or online service state, ticket and account status.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Authentication error (Auth No Server). Check Steam or online service state, ticket and account status.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Invalid Steam ticket.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Authentication error (Auth Duplicate Request). Check Steam or online service state, ticket and account status.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Authentication error (Auth Invalid Version). Check Steam or online service state, ticket and account status.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Authentication error (Auth Game Mismatch). Check Steam or online service state, ticket and account status.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Expired ticket.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Authentication error (Auth Invalid Steam Onvalidate). Check Steam or online service state, ticket and account status.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Authentication error (Auth User Not Connected). Check Steam or online service state, ticket and account status.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Expired or invalid license.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

VAC/service ban for this game.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The account is also logged in elsewhere.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

VAC/anti-cheat verification timed out.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Authentication error (Auth Canceled). Check Steam or online service state, ticket and account status.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

The ticket has already been used.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Authentication error (Auth Ticket Invalid). Check Steam or online service state, ticket and account status.

For ClientKicked codes, the extra kick/BattlEye text is often more useful than the technical code itself.

Publisher/game ban.