Error map
3902 SQL Server Msg 3902: The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION
SQL · layer 5, Data
Centre: this error. First ring: errors it is linked with (12). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (12)
Deadlock found when trying to get lock; try restarting transaction
Two transactions waited on each other’s locks; the database killed one so the other could continue.
ERROR: current transaction is aborted, commands ignored until end of transaction block
An earlier statement in the same transaction failed; PostgreSQL rejects everything until you ROLLBACK.
Lock wait timeout exceeded; try restarting transaction (MySQL 1205)
A query waited too long for a row lock held by another transaction and gave up.
FATAL: terminating connection due to idle-in-transaction timeout
A session opened a transaction and sat idle longer than idle_in_transaction_session_timeout.
MySQL ERROR 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
MySQL detected a deadlock between two transactions and rolled one back.
ERROR: could not serialize access due to concurrent update
A REPEATABLE READ/SERIALIZABLE transaction conflicted with a concurrent one and must be retried.
Inconsistent results inside a transaction: non-repeatable and phantom reads (isolation level)
Two reads in the same transaction see different data because another transaction committed in between.
Changes disappear: transaction never committed (autocommit off, missing COMMIT)
Data inserted or updated "works" in your session but isn't there for others, or is gone after reconnecting.
SQL Server Msg 1205: Transaction was deadlocked on lock resources and has been chosen as the deadlock victim
Two sessions each hold locks the other needs, so SQL Server rolled one of them back.
SQL Server Msg 209: Ambiguous column name
A column exists in more than one table of the query and isn't qualified.
SQL Server Msg 266: Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements
A stored procedure or trigger exited with a different @@TRANCOUNT than it started with.
SQLite: cannot start a transaction within a transaction
BEGIN was issued while a transaction was already open on the same connection.
Two steps away (35)
MySQL ERROR 1062 (23000): Duplicate entry for key
An INSERT/UPDATE would create a duplicate value in a PRIMARY or UNIQUE key.
MySQL ERROR 2006 (HY000): MySQL server has gone away
The connection to MySQL was closed — usually by a timeout or a packet larger than `max_allowed_packet`.
sqlite3.OperationalError: database is locked (SQLITE_BUSY)
Another connection holds a write lock on the SQLite file, and this one gave up waiting.
ERROR: canceling statement due to statement timeout
A query ran longer than statement_timeout and PostgreSQL cancelled it.
ERROR: bind message supplies 2 parameters, but prepared statement requires 1
The number of query parameters sent doesn’t match the $1, $2 … placeholders in the SQL.
MySQL ERROR 1040 (08004): Too many connections
MySQL reached `max_connections` and refuses new clients.
HikariPool-1 - Connection is not available, request timed out after 30000ms
The connection pool was exhausted — all connections were busy for 30 seconds.
SQL Server: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The command ran longer than the client’s CommandTimeout (default 30 seconds).
Cloudflare Error 522: Connection Timed Out
Cloudflare’s TCP connection to your origin timed out — the origin didn’t answer at all.
Cloudflare Error 524: A Timeout Occurred
Cloudflare connected to the origin, but the origin didn’t send an HTTP response within 100 seconds.
API Request Timed Out (ETIMEDOUT / ReadTimeout / timeout of 30000ms exceeded)
The client gave up waiting — either for the connection to open or for the response to arrive.
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
DDL or a NOWAIT lock couldn’t get the lock because another session holds it.
Terraform: Error: Error acquiring the state lock — ConditionalCheckFailedException / state blob is already locked
Another Terraform run holds the state lock, or a previous run crashed and left the lock behind.
Rails: ActiveRecord::StaleObjectError: Attempted to update a stale object: Order
Two users/processes updated the same record; the second save failed the `lock_version` check.
HTTP 409 Conflict
The request conflicts with the current state of the resource — e.g. a duplicate or an edit based on an outdated version.
java.util.ConcurrentModificationException
A collection was modified while being iterated (even in a single thread).
HTTP 412 Precondition Failed
A conditional request header (If-Match, If-Unmodified-Since) didn’t match the current state of the resource.
java.lang.InterruptedException (sleep interrupted)
A blocked thread (sleep, wait, join, queue take) was interrupted by another thread.
java.util.concurrent.TimeoutException
A Future.get(timeout) or async operation didn’t complete in the allowed time.
Optimistic lock conflict: OptimisticLockException / StaleObjectStateException / version mismatch
Someone else changed the record after you read it, so your update — based on an old version — was rejected to avoid overwriting t…
Query returns far too many rows: accidental Cartesian product (missing JOIN condition)
Two tables were joined without a condition, so every row of one pairs with every row of the other.
CASE expression returns mixed types: conversion failed / types cannot be matched
The branches of a CASE expression produce incompatible data types (text and number, date and string).
COUNT(column) ignores NULLs: counts differ from COUNT(*)
`COUNT(col)` counts only non-NULL values, while `COUNT(*)` counts rows, so totals don't match.
SQL Server Msg 1222: Lock request time out period exceeded
A statement waited longer than `LOCK_TIMEOUT` for a lock held by another session.
ORA-00060: deadlock detected while waiting for resource
Two sessions wait for each other's row locks; Oracle rolled back one statement.
SQLite: database table is locked (SQLITE_LOCKED)
A statement on the same connection (or shared cache) conflicts with another statement that still has an open cursor on that table.
Column reference is ambiguous / Column 'id' in field list is ambiguous (MySQL 1052)
A column name exists in more than one joined table, so the database doesn’t know which one you mean.
MySQL ERROR 1066 (42000): Not unique table/alias: 'x'
The same table or alias appears twice in a FROM/JOIN without distinct aliases.
LEFT JOIN returns fewer rows: a WHERE filter on the right table turns it into an INNER JOIN
A condition on the right-hand table in WHERE removes the NULL-extended rows that a LEFT JOIN was supposed to keep.
Spanner: Session not found / ABORTED: transaction was aborted — retry the transaction
Spanner killed an idle session or aborted a transaction because of lock conflicts, and the client must retry.
Cloud Build trigger doesn't fire or fails: GitHub connection/app not installed or repository not linked
A push or PR doesn't start a build, or the trigger shows a connection error with GitHub.
Firestore: 10 ABORTED: Too much contention on these documents. Please try again.
Many transactions or writes hit the same document, so Firestore aborted yours.
sqlite3.IntegrityError: UNIQUE constraint failed: users.email
An insert/update duplicated a value in a UNIQUE or PRIMARY KEY column in SQLite.
sqlite3.IntegrityError: NOT NULL constraint failed: table.column
A NULL went into a NOT NULL column in SQLite.
sqlite3.IntegrityError: FOREIGN KEY constraint failed
An insert/update/delete violated a foreign key in SQLite (with PRAGMA foreign_keys=ON).
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError