Error 1105 appears when MySQL encounters an unmapped internal failure and falls back to the generic “Unknown error” message.
MySQL Error 1105: ER_UNKNOWN_ERROR signals that the server hit an unexpected internal problem and could not map it to a specific code. Read the MySQL error log, correct the underlying issue—often a plugin crash, corrupt table, or bad configuration—and rerun the query to fix it.
Unknown error
MySQL error 1105, condition ER_UNKNOWN_ERROR, is a generic fallback raised when the server cannot match an internal failure to a specific error code. The full message reads: "Error 1105 (HY000): Unknown error".
Because the label is generic, the true root cause hides in the server or InnoDB error log.
Diagnosing it quickly is important because the same code can indicate anything from permission problems to corrupted data files.
The server throws error 1105 when it encounters an unexpected condition during statement execution, startup, or replication. Missing error mappings, plugin crashes, or failed system calls bubble up as ER_UNKNOWN_ERROR.
Most occurrences happen after recent configuration changes, engine plugin upgrades, or complex DDL and DML statements that touch large data sets.
Replication and stored routines can also surface the code when they trigger unsupported operations.
Start by checking the MySQL error log with SHOW VARIABLES LIKE 'log_error'; then tail the referenced file.
The detailed stack trace pinpoints the failing component.
Next, reproduce the error in a test environment, narrow it to a single query or setting, and apply a targeted fix such as reverting a parameter, repairing a table, or reinstalling a plugin.
Replicating servers may stop with 1105 when a row event references a dropped column.
Skipping the event with SET GLOBAL sql_slave_skip_counter = 1; followed by START SLAVE clears the blockage.
After upgrading MySQL, an outdated UDF or storage engine may crash and surface 1105.
Removing or recompiling the offending plugin resolves the failure.
Apply configuration changes in staged environments first, enable error logging at WARNING level, and keep plugins in sync with the server version to avoid unmapped failures.
Automate backups and use CHECK TABLE regularly so that if corruption causes 1105 you can restore or repair quickly.
Error 1815 (HY000): Internal error on CREATE TABLE may show similar symptoms but specifically targets failed table creation.
Error 2013 (HY000): Lost connection indicates network or server crashes rather than an unmapped issue.
.
A storage engine, UDF, or authentication plugin crashes while running a query. Lacking a dedicated error code, MySQL surfaces 1105.
InnoDB or MyISAM detects page corruption and aborts the statement.
If the corruption is not mapped, ER_UNKNOWN_ERROR appears.
Setting an unsupported value for a global variable at runtime can trigger an undefined branch in the source code that returns 1105.
A replica processes an event that references a schema object that no longer exists. It fails with the generic 1105 message.
Mixing old plugins with a new server binary leads to symbol mismatch and an unknown error during initialization.
.
Authentication failure due to wrong credentials, not an internal crash.
Transaction deadlock, resolved by retry logic, unlike 1105 which signals an unexpected bug.
Specific to table creation, often corruption or missing partition handler, more descriptive than generic 1105.
Indicates network or server crash.
1105 may precede 2013 in logs if the crash was internal.
.
The server hit an issue without a predefined mapping in errmsg-utf8.txt, so it falls back to error 1105.
Not always. It can be a plugin crash, bad configuration, or replication mismatch. Check logs to confirm corruption.
No. Even intermittent 1105 errors signal instability that can escalate. Investigate root causes promptly.
Galaxy's editor surfaces server logs beside your query, lets you rerun statements, and share reproduction steps with teammates, speeding resolution.
.avif)
.avif){kind=logo}
