This document provides a detailed list of error codes from both clients and the server that may be encountered when using TDengine TSDB, as well as the corresponding actions to take.
TSDB error codes include those from the taosc client and the server. Connectors for all programming languages may return these error codes to the caller, regardless of whether they use native connections or WebSocket connections. **When WebSocket connections return error codes, only the last four digits are retained.**
| TDengine TSDB Business Error | 0x8000 | Custom business logic error codes defined by the TDengine TSDB engine; see the error code descriptions for each module below for details. |
| Linux System Call Error | 0x80FF | The last 4 digits correspond to the `errno` returned by Linux system APIs; refer to [Linux Error Codes](https://www.chromium.org/chromium-os/developer-library/reference/linux-constants/errnos/). |
| Windows API System Error | 0x81FF | The last 4 digits correspond to error codes returned by Windows APIs; refer to [Windows Error Codes](https://learn.microsoft.com/en-us/windows/win32/debug/system-error-codes#system-error-codes). |
| Windows Socket System Error | 0x82FF | The last 4 digits correspond to error codes returned by Windows Socket APIs; refer to [Windows Sockets Error Codes](https://learn.microsoft.com/en-us/windows/win32/winsock/windows-sockets-error-codes-2). |
| 0x8000000B | Unable to establish connection | 1. Network is unreachable 2. Multiple retries, still unable to perform request | 1. Check network 2. Analyze logs, specific reasons are more complex |
| 0x80000013 | Client and server's time is not synchronized | 1. Client and server are not in the same time zone 2. Client and server are in the same time zone, but their times are not synchronized, differing by more than 900 seconds | 1. Adjust to the same time zone 2. Calibrate client and server time |
| 0x80000015 | Unable to resolve FQDN | Invalid fqdn set | Check fqdn settings |
| 0x80000017 | Port already in use | The port is already occupied by some service, and the newly started service still tries to bind to that port | 1. Change the server port of the new service 2. Kill the service that previously occupied the port |
| 0x80000018 | Conn is broken | Due to network jitter or request time being too long (over 900 seconds), the system actively disconnects | 1. Set the system's maximum timeout duration 2. Check request duration |
| 0x80000019 | Conn read timeout | 1. The request processing time is too long 2. The server is overwhelmed 3. The server is deadlocked | 1. Explicitly configure the readTimeout parameter 2. Analyze the stack on taos |
| 0x80000020 | some vnode/qnode/mnode(s) out of service | After multiple retries, still unable to connect to the cluster, possibly all nodes have crashed, or the surviving nodes are not Leader nodes | 1. Check the status of taosd, analyze the reasons for taosd crash 2. Analyze why the surviving taosd cannot elect a Leader |
| 0x80000021 | some vnode/qnode/mnode(s) conn is broken | After multiple retries, still unable to connect to the cluster, possibly due to network issues, request time too long, server deadlock, etc. | 1. Check network 2. Request execution time |
| 0x80000022 | rpc open too many session | 1. High concurrency causing the number of occupied connections to reach the limit 2. Server BUG, causing connections not to be released | 1. Adjust configuration parameter numOfRpcSessions 2. Adjust configuration parameter timeToGetAvailableConn 3. Analyze reasons for server not releasing connections |
| 0x80000023 | RPC network error | 1. Network issues, possibly intermittent 2. Server crash | 1. Check the network 2. Check if the server has restarted |
| 0x80000024 | RPC network bus | 1. When pulling data between clusters, no available connections are obtained, or the number of connections has reached the limit | 1. Check if the concurrency is too high 2. Check if there are any anomalies in the cluster nodes, such as deadlocks |
| 0x80000025 | HTTP-report already quit | 1. Issues with HTTP reporting | Internal issue, can be ignored |
| 0x80000026 | RPC module already quit | 1. The client instance has already exited, but still uses the instance for queries | Check the business code to see if there is a mistake in usage |
| 0x80000027 | RPC async module already quit | 1. Engine error, can be ignored, this error code will not be returned to the user side | If returned to the user side, the engine side needs to investigate the issue |
| 0x80000028 | RPC async in process | 1. Engine error, can be ignored, this error code will not be returned to the user side | If returned to the user side, the engine side needs to investigate the issue |
| 0x80000029 | RPC no state | 1. Engine error, can be ignored, this error code will not be returned to the user side | If returned to the user side, the engine side needs to investigate the issue |
| 0x8000002A | RPC state already dropped | 1. Engine error, can be ignored, this error code will not be returned to the user side | If returned to the user side, the engine side needs to investigate the issue |
| 0x8000002B | RPC msg exceed limit | 1. Single RPC message exceeds the limit, this error code will not be returned to the user side | If returned to the user side, the engine side needs to investigate the issue |
| 0x80000100 | Operation not supported | Operation not supported, disallowed scenarios | Check if the operation is incorrect, confirm if the feature is supported |
| 0x80000102 | Out of Memory | Client or server memory allocation failure scenarios | Check if client, server memory is sufficient |
| 0x80000104 | Data file corrupted | 1. Storage data file damaged 2. udf file cannot be created | 1. Contact Taos customer support 2. Confirm server has read/write/create file permissions for the temporary directory |
| 0x80000106 | too many Ref Objs | No available ref resources | Preserve the scene and logs, report issue on github |
| 0x80000107 | Ref ID is removed | The referenced ref resource has been released | Preserve the scene and logs, report issue on github |
| 0x80000108 | Invalid Ref ID | Invalid ref ID | Preserve the scene and logs, report issue on github |
| 0x8000010A | Ref is not there | ref information does not exist | Preserve the scene and logs, report issue on github |
| 0x8000010B | Driver was not loaded | libtaosnative.so or libtaosws.so was not found in the system path | Reinstall the client driver |
| 0x8000010C | Function was not loaded from the driver | some function defined in libtaos.so are not implemented in libtaosnative.so or libtaosws.so | Reinstall the client driver |
| 0x80000110 | Unexpected generic error | System internal error | Preserve the scene and logs, report issue on github |
| 0x80000111 | Action in progress | Operation in progress | 1. Wait for the operation to complete 2. Cancel the operation if necessary 3. If it exceeds a reasonable time and still not completed, preserve the scene and logs, or contact customer support |
| 0x80000112 | Out of range | Configuration parameter exceeds allowed value range | Change the parameter |
| 0x80000115 | Invalid message | Incorrect message | 1. Check for version inconsistency between nodes 2. Preserve the scene and logs, report issue on github |
| 0x80000116 | Invalid message len | Incorrect message length | 1. Check for version inconsistency between nodes 2. Preserve the scene and logs, report issue on github |
| 0x80000117 | Invalid pointer | Invalid pointer | Preserve the scene and logs, report issue on github |
| 0x80000118 | Invalid parameters | Invalid parameters | Preserve the scene and logs, report issue on github |
| 0x80000119 | Invalid config option | Invalid configuration | Preserve the scene and logs, report issue on github |
| 0x8000011A | Invalid option | Invalid option | Preserve the scene and logs, report issue on github |
| 0x8000011B | Invalid json format | JSON format error | Preserve the scene and logs, report issue on github |
| 0x8000011C | Invalid version number | Invalid version format | Preserve the scene and logs, report issue on github |
| 0x8000011D | Invalid version string | Invalid version format | Preserve the scene and logs, report issue on github |
| 0x8000011E | Version not compatible | Version incompatibility between nodes | Check versions of all nodes (including server and client), ensure node versions are consistent or compatible |
| 0x8000011F | Checksum error | File checksum verification failed | Preserve the scene and logs, report issue on github |
| 0x80000120 | Failed to compress msg | Compression failed | Preserve the scene and logs, report issue on github |
| 0x80000121 | Message not processed | Message not correctly processed | Preserve the scene and logs, report issue on github |
| 0x80000122 | Config not found | Configuration item not found | Preserve the scene and logs, report issue on github |
| 0x80000123 | Repeat initialization | Repeated initialization | Preserve the scene and logs, report issue on github |
| 0x80000124 | Cannot add duplicate keys to hash | Adding duplicate key data to hash table | Preserve the scene and logs, report issue on github |
| 0x80000125 | Retry needed | Application needs to retry | Application should retry according to API usage specifications |
| 0x80000126 | Out of memory in rpc queue | rpc message queue memory usage reached limit | 1. Check and confirm if system load is too high 2. (If necessary) Increase rpc message queue memory limit through configuration rpcQueueMemoryAllowed 3. If the problem persists, preserve the scene and logs, report issue on github |
| 0x80000127 | Invalid timestamp format | Incorrect timestamp format | Check and confirm the input timestamp format is correct |
| 0x80000128 | Msg decode error | Message decode error | Preserve the scene and logs, report issue on github |
| 0x8000012A | Not found | Internal cache information not found | Preserve the scene and logs, report issue on github |
| 0x8000012B | Out of disk space | Insufficient disk space | 1. Check and ensure data directory, temporary file folder directory have sufficient disk space 2. Regularly check and maintain the above directories to ensure enough space |
| 0x80000130 | Database is starting up | Database is starting up, unable to provide service | Check database status, wait for the system to finish starting up or retry |
| 0x80000131 | Database is closing down | Database is closing down or has closed, unable to provide service | Check database status, ensure the system is working in normal state |
| 0x80000132 | Invalid data format | Incorrect data format | 1. Preserve the scene and logs, report issue on github 2. Contact Taos customer support |
| 0x80000133 | Invalid operation | Invalid or unsupported operation | 1. Modify to confirm the current operation is legal and supported, check parameter validity 2. If the problem persists, preserve the scene and logs, report issue on github |
| 0x80000134 | Invalid value | Invalid value | Preserve the scene and logs, report issue on github |
| 0x80000135 | Invalid fqdn | Invalid FQDN | Check if the configured or input FQDN value is correct |
| 0x8000013C | Invalid disk id | Invalid disk id | Check users whether the mounted disk is invalid or use the parameter diskIDCheckEnabled to skip the disk check. |
| 0x80000207 | Invalid user name | Invalid database username | Check if the database username is correct |
| 0x80000208 | Invalid password | Invalid database password | Check if the database password is correct |
| 0x80000209 | Database name too long | Invalid database name | Check if the database name is correct |
| 0x8000020A | Table name too long | Invalid table name | Check if the table name is correct |
| 0x8000020F | Query terminated | Query was terminated | Check if the query was terminated by a user |
| 0x80000213 | Disconnected from server | Connection was interrupted | Check if the connection was interrupted by someone or if the client is exiting |
| 0x80000216 | Syntax error in SQL | SQL syntax error | Check and correct the SQL statement |
| 0x80000219 | SQL statement too long | SQL length exceeds limit | Check and correct the SQL statement |
| 0x8000021A | File is empty | File content is empty | Check the content of the input file |
| 0x8000021F | Invalid column length | Incorrect column length | Preserve the scene and logs, report issue on GitHub |
| 0x80000222 | Invalid JSON data type | Incorrect JSON data type | Check the JSON content input |
| 0x80000224 | Value out of range | Data size exceeds type range | Check the data value input |
| 0x80000229 | Invalid tsc input | API input error | Check the parameters passed when calling the API from the application |
| 0x8000022A | Stmt API usage error | Incorrect usage of STMT/STMT2 API | Check the order of STMT/STMT2 API calls, applicable scenarios, and error handling |
| 0x8000022B | Stmt table name not set correctly | STMT/STMT2 table name not set correctly | Check if the STMT/STMT2 tbname bind is legal |
| 0x8000022D | Query killed | Query was terminated | Check if the query was terminated by a user |
| 0x8000022E | No available execution node | No available query execution node | Check the current query policy configuration, ensure available Qnode if needed |
| 0x8000022F | Table is not a supertable | Table name in the statement is not a supertable | Check if the table name used in the statement is a supertable |
| 0x80000230 | Stmt cache error | STMT/STMT2 internal cache error | Preserve the scene and logs, report issue on GitHub |
| 0x80000231 | Tsc internal error | TSC internal error | Preserve the scene and logs, report issue on GitHub |
| 0x80000331 | Dnode does not exist | Internal error | Report issue |
| 0x80000332 | Vgroup does not exist | Internal error | Report issue |
| 0x80000333 | Cannot drop mnode which is leader | Operating node is leader | Confirm if the operation is correct |
| 0x80000334 | Out of dnodes | Insufficient dnode nodes | Increase dnode nodes |
| 0x80000335 | Cluster cfg inconsistent | Configuration inconsistency | Check if the configuration of dnode and mnode nodes is consistent. Check method: 1. Output in logs when nodes start 2. Use show variables |
| 0x8000033B | Cluster id not match | Node configuration data inconsistency | Check the clusterid in each node's data/dnode/dnodes.json file |
| 0x80000353 | Invalid password format | The password must be between 8 and 16 characters long and include at least three types of characters from the following: uppercase letters, lowercase letters, numbers, and special characters. | Confirm the format of the password string |
| 0x8000039F | No VGroup's leader need to be balanced | Perform balance leader operation on VGroup | There is no VGroup's leader needs to be balanced |
| 0x800003C3 | STable option unchanged | No change in operation | Confirm if the operation is correct |
| 0x800003C4 | Field used by topic | Being used | Confirm if the operation is correct |
| 0x800003C5 | Database is single stable mode | Internal error | Report issue |
| 0x800003C6 | Invalid schema version while alter stb | Internal error | Report issue |
| 0x800003C7 | Invalid stable uid while alter stb | Internal error | Report issue |
| 0x800003C8 | Field used by tsma | Being used | Confirm if the operation is correct |
| 0x800003D1 | Transaction not exists | Does not exist | Confirm if the operation is correct |
| 0x800003D2 | Invalid stage to kill | Transaction is at a stage that cannot be killed (e.g., during commit) | Wait for the transaction to end, if it does not end for a long time, report issue |
| 0x800003D3 | Conflict transaction not completed | Transaction conflict, cannot perform this operation | Use the show transactions command to view the conflicting transaction, wait for the conflicting transaction to end, if it does not end for a long time, report issue |
| 0x800003D5 | Unable to establish connection While execute transaction and will continue in the background | Network error | Check if the network is normal |
| 0x800003D6 | Last Transaction not finished | Internal error | Report issue |
| 0x800003D7 | Sync timeout While execute transaction and will continue in the background | Internal error | Report issue |
| 0x80000700 | Invalid query handle | Current query handle does not exist | Preserve the scene and logs, report issue on GitHub |
| 0x80000709 | Multiple retrieval of this query | Current subquery is already in progress | Preserve the scene and logs, report issue on GitHub |
| 0x8000070A | Too many groups/time window in query | Number of groups or windows in query results exceeds the limit | Adjust the query statement to ensure the number of groups and windows does not exceed the limit |
| 0x8000070D | System error | Error returned by underlying system API | Preserve the scene and logs, report issue on GitHub |
| 0x80000720 | Scheduler not exist | Client information for the current subquery does not exist | Preserve the scene and logs, report issue on GitHub |
| 0x80000721 | Task not exist | Subquery does not exist | Preserve the scene and logs, report issue on GitHub |
| 0x80000722 | Task already exist | Subquery already exists | Preserve the scene and logs, report issue on GitHub |
| 0x80000729 | Task message error | Query message error | Preserve the scene and logs, report issue on GitHub |
| 0x8000072B | Task status error | Subquery status error | Preserve the scene and logs, report issue on GitHub |
| 0x8000072F | Job not exist | Query JOB no longer exists | Preserve the scene and logs, report issue on GitHub |
| 0x8000073C | Memory pool not initialized | Memory pool not initialized in dnode | Confirm if the switch queryUseMemoryPool is enabled; if queryUseMemoryPool is already enabled, check if the server meets the basic conditions for enabling the memory pool: 1. The total available system memory is not less than 5GB; 2. The available system memory after deducting the reserved portion is not less than 4GB. |
| 0x8000073D | Alter minReservedMemorySize failed since no enough system available memory | Failed to update minReservedMemorySize | Check current system memory: 1. Total available system memory should not be less than 5G; 2. Available system memory after deducting reserved portion should not be less than 4G |
| 0x80000903 | Sync timeout | Scenario 1: Leader switch occurred, old leader node started negotiation but not yet agreed, leading to timeout. Scenario 2: Follower node response timeout, causing negotiation timeout. | Check cluster status, e.g., `show vgroups`. Check server logs and network conditions between server nodes. |
| 0x8000090C | Sync leader is unreachable | Scenario 1: During leader election. Scenario 2: Client request routed to follower node, and redirection failed. Scenario 3: Client or server network configuration error. | Check cluster status, network configuration, application access status, etc. Check server logs and network conditions between server nodes. |
| 0x8000090F | Sync new config error | Member configuration change error | Internal error, user cannot intervene |
| 0x80000911 | Sync not ready to propose | Scenario 1: Recovery not completed | Check cluster status, e.g., `show vgroups`. Check server logs and network conditions between server nodes. |
| 0x80000914 | Sync leader is restoring | Scenario 1: Leader switch occurred, leader is replaying logs | Check cluster status, e.g., `show vgroups`. Check server logs and observe recovery progress. |
| 0x80000916 | Sync buffer is full | Scenario 1: High concurrency of client requests, exceeding server's processing capacity, or due to severe lack of network and CPU resources, or network connection issues. | Check cluster status, system resource usage (e.g., disk IO, CPU, network), and network connections between nodes. |
| 0x80000917 | Sync write stall | Scenario 1: State machine execution blocked, e.g., due to system busyness, severe lack of disk IO resources, or write failures. | Check cluster status, system resource usage (e.g., disk IO and CPU), and whether there were write failures. |
| 0x80000918 | Sync negotiation win is full | Scenario 1: High concurrency of client requests, exceeding server's processing capacity, or due to severe lack of network and CPU resources, or network connection issues. | Check cluster status, system resource usage (e.g., disk IO, CPU, network), and network connections between nodes. |
| 0x80000A0C | TQ table schema not found | The table does not exist when consuming data | Internal error, not passed to users |
| 0x80000A0D | TQ no committed offset | Consuming with offset reset = none, and no previous offset on server | Set offset reset to earliest or latest |
| 0x80002201 | TFS invalid configuration | Incorrect multi-tier storage configuration | Check if the configuration is correct |
| 0x80002202 | TFS too many disks on one level | Incorrect multi-tier storage configuration | Check if the number of disks on one level exceeds the maximum limit |
| 0x80002203 | TFS duplicate primary mount disk | Incorrect multi-tier storage configuration | Check if the configuration is correct |
| 0x80002204 | TFS no primary mount disk | Incorrect multi-tier storage configuration | Check if the configuration is correct |
| 0x80002205 | TFS no disk mount on tire | Incorrect multi-tier storage configuration | Check if the configuration is correct |
| 0x80002208 | No disk available on a tier. | TFS internal error, often occurs when disks are full | Add more disks to expand capacity |
| 0x80002600 | syntax error near | SQL syntax error | Check and correct the SQL statement |
| 0x80002601 | Incomplete SQL statement | Incomplete SQL statement | Check and correct the SQL statement |
| 0x80002602 | Invalid column name | Illegal or non-existent column name | Check and correct the SQL statement |
| 0x80002603 | Table does not exist | Table does not exist | Check and confirm the existence of the table in the SQL statement |
| 0x80002604 | Column ambiguously defined | Column (alias) redefined | Check and correct the SQL statement |
| 0x80002605 | Invalid value type | Illegal constant value | Check and correct the SQL statement |
| 0x80002608 | There mustn't be aggregation | Aggregation function used in illegal clause | Check and correct the SQL statement |
| 0x80002609 | ORDER BY item must be the number of a SELECT-list expression | Illegal position specified in Order by | Check and correct the SQL statement |
| 0x8000260A | Not a GROUP BY expression | Illegal group by statement | Check and correct the SQL statement |
| 0x8000260B | Not SELECTed expression | Illegal expression | Check and correct the SQL statement |
| 0x8000260C | Not a single-group group function | Illegal use of column and function | Check and correct the SQL statement |
| 0x8000260D | Tags number not matched | Mismatched number of tag columns | Check and correct the SQL statement |
| 0x8000260E | Invalid tag name | Invalid or non-existent tag name | Check and correct the SQL statement |
| 0x80002610 | Value is too long | Value length exceeds limit | Check and correct the SQL statement or API parameters |
| 0x80002611 | Password too short or empty | Password is empty or less than 8 chars | Use a valid password |
| 0x80002612 | Port should be an integer that is less than 65535 and greater than 0 | Illegal port number | Check and correct the port number |
| 0x80002613 | Endpoint should be in the format of 'fqdn:port' | Incorrect address format | Check and correct the address information |
| 0x80002614 | This statement is no longer supported | Feature has been deprecated | Refer to the feature documentation |
| 0x80002615 | Interval too small | Interval value exceeds the allowed minimum | Change the INTERVAL value |
| 0x80002616 | Database not specified | Database not specified | Specify the database for the current operation |
| 0x80002617 | Invalid identifier name | Illegal or invalid length ID | Check the names of related libraries, tables, columns, TAGs, etc. in the statement |
| 0x80002618 | Corresponding supertable not in this db | Supertable does not exist | Check if the corresponding supertable exists in the database |
| 0x80002619 | Invalid database option | Illegal database option value | Check and correct the database option values |
| 0x8000261A | Invalid table option | Illegal table option value | Check and correct the table option values |
| 0x80002624 | GROUP BY and WINDOW-clause can't be used together | Group by and window cannot be used together | Check and correct the SQL statement |
| 0x80002627 | Aggregate functions do not support nesting | Functions do not support nested use | Check and correct the SQL statement |
| 0x80002628 | Only support STATE_WINDOW on integer/bool/varchar column | Unsupported STATE_WINDOW data type | Check and correct the SQL statement |
| 0x80002629 | Not support STATE_WINDOW on tag column | STATE_WINDOW not supported on tag column | Check and correct the SQL statement |
| 0x8000262A | STATE_WINDOW not support for supertable query | STATE_WINDOW not supported for supertable | Check and correct the SQL statement |
| 0x8000262B | SESSION gap should be fixed time window, and greater than 0 | Illegal SESSION window value | Check and correct the SQL statement |
| 0x8000262C | Only support SESSION on primary timestamp column | Illegal SESSION window column | Check and correct the SQL statement |
| 0x8000262D | Interval offset cannot be negative | Illegal INTERVAL offset value | Check and correct the SQL statement |
| 0x8000262E | Cannot use 'year' as offset when interval is 'month' | Illegal INTERVAL offset unit | Check and correct the SQL statement |
| 0x8000262F | Interval offset should be shorter than interval | Illegal INTERVAL offset value | Check and correct the SQL statement |
| 0x80002630 | Does not support sliding when interval is natural month/year | Illegal sliding unit | Check and correct the SQL statement |
| 0x80002631 | sliding value no larger than the interval value | Illegal sliding value | Check and correct the SQL statement |
| 0x80002632 | sliding value can not less than 1%% of interval value | Illegal sliding value | Check and correct the SQL statement |
| 0x80002633 | Only one tag if there is a json tag | Only single JSON tag column supported | Check and correct the SQL statement |
| 0x80002634 | Query block has incorrect number of result columns | Mismatched number of columns | Check and correct the SQL statement |
| 0x80002635 | Incorrect TIMESTAMP value | Illegal primary timestamp column value | Check and correct the SQL statement |
| 0x80002637 | soffset/offset can not be less than 0 | Illegal soffset/offset value | Check and correct the SQL statement |
| 0x80002638 | slimit/soffset only available for PARTITION/GROUP BY query | slimit/soffset only supported for PARTITION BY/GROUP BY statements | Check and correct the SQL statement |
| 0x8000264B | Only binary/nchar column length could be modified, and the length can only be increased, not decreased | Illegal column modification | Check and correct the SQL statement |
| 0x8000264C | Invalid tbname pseudocolumn | Illegal use of tbname column | Check and correct the SQL statement |
| 0x8000264D | Invalid function name | Illegal function name | Check and correct the function name |
| 0x8000264E | Comment too long | Comment length exceeds limit | Check and correct the SQL statement |
| 0x8000264F | Function(s) only allowed in SELECT list, cannot mixed with non scalar functions or columns | Illegal mixing of functions | Check and correct the SQL statement |
| 0x80002650 | Window query not supported, since no valid timestamp column included in the result of subquery | Window query depends on non-existent primary timestamp column | Check and correct the SQL statement |
| 0x80002651 | No columns can be dropped | Essential columns cannot be deleted | Check and correct the SQL statement |
| 0x80002652 | Only tag can be json type | Normal columns do not support JSON type | Check and correct the SQL statement |
| 0x80002655 | The DELETE statement must have a definite time window range | Illegal WHERE condition in DELETE statement | Check and correct the SQL statement |
| 0x80002656 | The REDISTRIBUTE VGROUP statement only support 1 to 3 dnodes | Illegal number of DNODEs specified in REDISTRIBUTE VGROUP | Check and correct the SQL statement |
| 0x80002657 | Fill now allowed | Function does not allow FILL feature | Check and correct the SQL statement |
| 0x80002658 | Invalid windows pc | Illegal use of window pseudocolumn | Check and correct the SQL statement |
| 0x80002659 | Window not allowed | Function cannot be used in window | Check and correct the SQL statement |
| 0x8000265A | Stream not allowed | Function cannot be used in stream computation | Check and correct the SQL statement |
| 0x8000265B | Group by not allowed | Function cannot be used in grouping | Check and correct the SQL statement |
| 0x8000265D | Invalid interp clause | Illegal INTERP or related statement | Check and correct the SQL statement |
| 0x8000265E | Not valid function ion window | Illegal window statement | Check and correct the SQL statement |
| 0x8000265F | Only support single table | Function only supported in single table queries | Check and correct the SQL statement |
| 0x80002660 | Invalid sma index | Illegal creation of SMA statement | Check and correct the SQL statement |
| 0x80002661 | Invalid SELECTed expression | Invalid query statement | Check and correct the SQL statement |
| 0x80002662 | Fail to get table info | Failed to retrieve table metadata information | Preserve the scene and logs, report issue on GitHub |
| 0x80002663 | Not unique table/alias | Table name (alias) conflict | Check and correct the SQL statement |
| 0x80002664 | Join requires valid time-series input | Unsupported JOIN query without primary timestamp column output in subquery | Check and correct the SQL statement |
| 0x80002665 | The _TAGS pseudocolumn can only be used for subtable and supertable queries | Illegal tag column query | Check and correct the SQL statement |
| 0x80002666 | Subquery does not output primary timestamp column | Check and correct the SQL statement | |
| 0x80002667 | Invalid usage of expr: %s | Illegal expression | Check and correct the SQL statement |
| 0x80002687 | True_for duration cannot be negative | Use negative value as true_for duration | Check and correct the SQL statement |
| 0x80002688 | Cannot use 'year' or 'month' as true_for duration | Use year or month as true_for_duration | Check and correct the SQL statement |
| 0x80002689 | Invalid using cols function | Illegal using cols function | Check and correct the SQL statement |
| 0x8000268A | Cols function's first param must be a select function that output a single row | The first parameter of the cols function should be a selection function | Check and correct the SQL statement |
| 0x8000268B | Invalid using alias for cols function | Illegal cols function alias | Check and correct the SQL statement |
| 0x8000268C | Join primary key col must be timestamp type | Join primary key data type error | Check and correct the SQL statement |
| 0x8000268D | Invalid virtual table's ref column | Create/Update Virtual table using incorrect data source column | Check and correct the SQL statement |
| 0x8000268E | Invalid table type | Incorrect Table type | Check and correct the SQL statement |
| 0x8000268F | Invalid ref column type | Virtual table's column type and data source column's type are different | Check and correct the SQL statement |
| 0x80002690 | Create child table using virtual super table | Create non-virtual child table using virtual super table | Check and correct the SQL statement |
| 0x800026FF | Parser internal error | Internal error in parser | Preserve the scene and logs, report issue on GitHub |
| 0x80002700 | Planner internal error | Internal error in planner | Preserve the scene and logs, report issue on GitHub |
| 0x80002701 | Expect ts equal | JOIN condition validation failed | Preserve the scene and logs, report issue on GitHub |
| 0x80002702 | Cross join not support | CROSS JOIN not supported | Check and correct the SQL statement |
| 0x80002704 | Planner slot key not found | Planner cannot find slotId during making physic plan | Preserve the scene and logs, report issue on GitHub |
| 0x80002705 | Planner invalid table type | Planner get invalid table type | Preserve the scene and logs, report issue on GitHub |
| 0x80002706 | Planner invalid query control plan type | Planner get invalid query control plan type during making physic plan | Preserve the scene and logs, report issue on GitHub |
| 0x80002800 | Function internal error | Errors caused by unreasonable function parameter inputs, with specific error descriptions returned with the error code. For example, when specifying the algorithm for the APERCENTILE function, only the string "default" can be used. Using other inputs like "t-digest" will cause this error. Or, if the second parameter of the TO_ISO8601 function specifies a timezone, and the string does not conform to timezone format standards. | Adjust the function inputs according to the specific error description. |
| 0x80002801 | Invalid function parameter number | Incorrect number of input parameters for the function. The function requires n parameters, but the number of parameters provided by the user is not n. For example, COUNT(col1, col2). | Adjust the number of input parameters to the correct number. |
| 0x80002802 | Invalid function parameter type | Incorrect type of input parameters for the function. The function requires numeric type parameters, but the parameters provided by the user are strings. For example, SUM("abc"). | Adjust the function parameter inputs to the correct type. |
| 0x80002803 | Invalid function parameter value | Incorrect value of input parameters for the function. The range of input parameters is incorrect. For example, the SAMPLE function's second parameter specifies a sampling number range of [1, 1000], and it will report an error if it is not within this range. | Adjust the function parameter inputs to the correct value. |
| 0x80002804 | Not a built-in function | The function is not a built-in function. Errors will occur if the built-in function is not in the hash table. Users should rarely encounter this problem, otherwise, it indicates an error during the initialization of the internal built-in function hash or corruption. | Customers should not encounter this; if they do, it indicates a bug in the program, consult the developers. |
| 0x80002805 | Duplicate timestamps not allowed in function | Duplicate timestamps in the function's input primary key column. When querying supertables with certain time-order dependent functions, all subtable data will be sorted by timestamp and merged into one timeline for calculation, which may result in duplicate timestamps, causing errors in some calculations. Functions involved include: CSUM, DERIVATIVE, DIFF, IRATE, MAVG, STATECOUNT, STATEDURATION, TWA | Ensure there are no duplicate timestamp data in subtables when querying supertables using these time-order dependent functions. |
| 0x80002902 | udf pipe read error | Error occurred when taosd reads from taosudf pipe | taosudf unexpectedly exits, 1) C udf crash 2) taosudf crash |
| 0x80002903 | udf pipe connect error | Error establishing pipe connection to taosudf in taosd | 1) Corresponding taosudf not started in taosd. Restart taosd |
| 0x80002904 | udf pipe not exist | Connection error occurs between two phases of udf setup, call, and teardown, causing the connection to disappear, subsequent phases continue | taosudf unexpectedly exits, 1) C udf crash 2) taosudf crash |
| 0x80002905 | udf load failure | Error loading udf in taosudf | 1) udf does not exist in mnode 2) Error in udf loading. Check logs |
| 0x80002906 | udf invalid function input | udf input check | udf function does not accept input, such as wrong column type |
| 0x80002907 | udf invalid bufsize | Intermediate result in udf aggregation function exceeds specified bufsize | Increase bufsize, or reduce intermediate result size |
| 0x80002908 | udf invalid output type | udf output type differs from the type specified when creating udf | Modify udf, or the type when creating udf, to match the result |
| 0x80002909 | udf program language not supported | udf programming language not supported | Use supported languages, currently supports C, Python |
| 0x8000290A | udf function execution failure | udf function execution error, e.g., returning incorrect number of rows | Refer to specific error logs |
| 0x80003000 | Invalid line protocol type | Illegal protocol passed to schemaless interface | Check if the protocol passed is one of the three defined in taos.h TSDB_SML_PROTOCOL_TYPE |
| 0x80003001 | Invalid timestamp precision type | Illegal timestamp precision passed to schemaless interface | Check if the protocol passed is one of the seven defined in taos.h TSDB_SML_TIMESTAMP_TYPE |
| 0x80003002 | Invalid data format | Illegal data format passed to schemaless interface | Refer to client-side error log hints |
| 0x80003004 | Not the same type as before | Inconsistent column types within the same batch of schemaless data | Ensure the data type of the same column in each row is consistent |
| 0x80003005 | Internal error | General internal logic error in schemaless, typically should not occur | Refer to client-side error log hints |
| 0x80003102 | Invalid tsma env | TSMA runtime environment is abnormal | Check error logs, contact development for handling |
| 0x80003103 | Invalid tsma state | The vgroup of the stream computing result is inconsistent with the vgroup that created the TSMA index | Check error logs, contact development for handling |
| 0x80003104 | Invalid tsma pointer | Processing the results issued by stream computing, the message body is a null pointer. | Check error logs, contact development for handling |
| 0x80003105 | Invalid tsma parameters | Processing the results issued by stream computing, the result count is 0. | Check error logs, contact development for handling |
| 0x80003113 | Tsma optimization cannot be applied with INTERVAL AUTO offset. | Tsma optimization cannot be enabled with INTERVAL AUTO OFFSET under the current query conditions. | Use SKIP_TSMA Hint or specify a manual INTERVAL OFFSET. |
| 0x80003200 | INDEX being rebuilt | 1. Writing too fast, causing the index merge thread to lag 2. Index file is damaged, being rebuilt | Check error logs, contact development for handling |
| 0x80003201 | Index file damaged | File damaged | Check error logs, contact development for handling |
| 0x80004001 | Consumer mismatch | The vnode requested for subscription and the reassigned vnode are inconsistent, usually occurs when new consumers join the same consumer group | Internal error |
| 0x80000440 | Analysis service response is NULL | The response content is empty | Check the taosanode.app.log for detailed response information |
| 0x80000441 | Analysis service can't access | Service is not work correctly, or network is broken | Check the status of taosanode and network status |
| 0x80000442 | Analysis algorithm is missing | Algorithm used in analysis is not specified | Add the "algo" parameter in forecast function or anomaly_window clause |
| 0x80000443 | Analysis algorithm not loaded | The specified algorithm is not available | Check for the specified algorithm |
| 0x80000444 | Analysis invalid buffer type | The buffered data type is invalid | Check the taosanode.app.log for more details |
| 0x80000445 | Analysis failed since anode return error | The responses from anode with error message | Check the taosanode.app.log for more details |
| 0x80000446 | Analysis failed since too many input rows for anode | Input data is too many | Reduce the rows of input data to below than the threshold |
| 0x80000447 | white-noise data not processed | white noise data is not processed | Ignore the white noise check or use another input data |
| 0x80000448 | Analysis internal error, not processed | Internal error occurs | Check the taosanode.app.log for more details |
| 0x80000449 | Analysis failed since not enough rows | Input data for forecasting are not enough | Increase the number of input rows (10 rows for forecasting at least) |
| 0x8000044A | Not support co-variate/multi-variate forecast | The algorithm not support co-variate/multi-variate forecasting | Change the specified algorithm |
| 0x80006200 | Virtual table scan internal error | virtual table scan operator internal error, generally does not occur | Check error logs, contact development for handling |
| 0x80006201 | Virtual table scan invalid downstream operator type | The incorrect execution plan generated causes the downstream operator type of the virtual table scan operator to be incorrect. | Check error logs, contact development for handling |
| 0x80006202 | Virtual table prim timestamp column should not has ref | The timestamp primary key column of a virtual table should not have a data source. If it does, this error will occur during subsequent queries on the virtual table. | Check error logs, contact development for handling |
| 0x80006203 | Create virtual child table must use virtual super table | Create virtual child table using non-virtual super table | create virtual child table using virtual super table |
| 0x80006204 | Virtual table not support decimal type | Create virtual table using decimal type | create virtual table without using decimal type |
| 0x80006205 | Virtual table not support in STMT query and STMT insert | Use virtual table in stmt query and stmt insert | do not use virtual table in stmt query and insert |
| 0x80006206 | Virtual table not support in Topic | Use virtual table in topic | do not use virtual table in topic |
| 0x80006207 | Virtual super table query not support origin table from different databases | Virtual super table's child table's origin table from different databases | make sure virtual super table's child table's origin table from same database |
| 0x80007007 | Snode still in use with streams | SNode is in use and cannot be deleted | Check the stream usage of SNode and confirm whether to proceed with deletion |
| 0x8000700E | Db used by stream | SNode is in use and cannot be deleted | Check the stream's usage of the database |
| 0x80007014 | Stream output table name too long | Output table name exceeds length limit | Check if the output table name rules in the stream creation statement are correct and if the result is too long |
| 0x80007016 | Stream output table name calc failed | Output table name calculation failed | Check if the output table name rules in the stream creation statement are correct and if NULL values exist |
| 0x80007017 | Stream vtable calculate need redeploy | Stream vtable calculate need redeploy | Stream will handle this error automatically |
Below are the error codes specific to connectors for various programming languages. In addition to returning their own error codes, connectors also return the TSDB error codes mentioned above.
### C
In the design of the C interface, error codes are represented as integers, and each error code corresponds to a specific error state. Unless otherwise specified:
- When an API returns an integer, **0** indicates success, and other values are error codes representing the cause of failure.
- When an API returns a pointer, **NULL** indicates failure.
The C connector has two types of error codes:
- General Error Codes
All error codes and their corresponding descriptions are in the `taoserror.h` file.
For detailed error code explanations, refer to: [TSDB Error Codes](./#tsdb)
- WebSocket Connection Error Codes
In addition to general error codes, WebSocket connections use the following error codes:
| Error Code | Error Description | Possible Error Scenarios or Reasons | Recommended User Actions |
| 0x2301 | Connection already closed | The connection has been closed | Check connection status or recreate the connection to execute related commands. |
| 0x2302 | This operation is NOT supported currently! | Called an unsupported interface | The currently used interface is not supported; switch to another connection method. |
| 0x2303 | Invalid variables | Illegal parameters | Check the corresponding interface specifications and adjust parameter types and sizes. |
| 0x2304 | Statement is closed | The statement has been closed | Check if the statement is used after being closed, or verify connection status. |
| 0x2305 | ResultSet is closed | The ResultSet has been released | Check if the ResultSet is used after being released. |
| 0x2306 | Batch is empty! | No parameters bound to prepareStatement | Add parameters to prepareStatement before executing `executeBatch`. |
| 0x2307 | Can not issue data manipulation statements with executeQuery() | Incorrect API call | Use `executeUpdate()` (not `executeQuery()`) for update operations. |
| 0x2308 | Can not issue SELECT via executeUpdate() | Incorrect API call | Use `executeQuery()` (not `executeUpdate()`) for query operations. |
| 0x230D | Parameter index out of range | Parameter out of bounds | Check the valid range of parameters. |
| 0x230E | Connection already closed | The connection has been closed | Check if the Connection is used after being closed, or verify connection status. |
| 0x230F | Unknown SQL type in TDengine | Unsupported data type | Check the data types supported by TDengine TSDB. |
| 0x2310 | Can't register JDBC-JNI driver | Failed to register the JNI driver | Check if the URL is filled in correctly. |
| 0x2314 | Numeric value out of range | Numeric type exceeds the allowable range | Check if the correct interface is used for numeric types in the ResultSet. |
| 0x2315 | Unknown Taos type in TDengine | Incorrect parameter passing | Verify that the correct TDengine TSDB data type is specified when converting between TDengine TSDB and JDBC data types. |
| 0x2319 | User is required | Missing username parameter | Add username information when creating the connection. |
| 0x231A | Password is required | Missing password parameter | Add password information when creating the connection. |
| 0x231D | Can't create connection with server within | Connection failure | Check the connection to taosAdapter. |
| 0x231E | Failed to complete the task within the specified time | Request processing timeout | Extend execution time by increasing the `messageWaitTimeout` parameter, or check the connection to taosAdapter. |
| 0x2320 | Type convert exception | Type conversion error | Verify that the correct data type is used. |
| 0x2321 | TDengine TSDB version incompatible | Native connection used, and client driver version does not match the server | TDengine TSDB versions are incompatible; upgrade to the corresponding version or use a WebSocket connection. |
| 0x2322 | Resource has been freed | Resource has been released | Confirm the operation is correct. |
| 0x2323 | BLOB is unsupported on the server | Outdated server version | The server does not support BLOB type; an upgrade is required. |
| 0x2324 | Line bind mode is unsupported on the server | Outdated server version | The server does not support line binding mode; an upgrade is required. |
| 0x2350 | Unknown error | Unknown exception | Report the issue to developers on GitHub. |
| 0x2352 | Unsupported encoding | Unsupported character set | An unsupported character encoding set was specified for the local connection. |
| 0x2353 | Internal error of database, please see taoslog for more details | Error occurred while executing prepareStatement in local connection | Check taos logs for troubleshooting. |
| 0x2354 | JNI connection is NULL | The connection has been closed | When executing commands via local connection, the Connection is already closed; check the connection to TDengine TSDB. |
| 0x2355 | JNI result set is NULL | The ResultSet has been closed | When retrieving ResultSet via local connection, the ResultSet is abnormal; check connection status and retry. |
| 0x2356 | Invalid num of fields | Mismatched ResultSet columns | Mismatched meta information for the ResultSet retrieved via local connection. |
| 0x2357 | Empty SQL string | Empty SQL statement | Fill in a valid SQL statement for execution. |
| 0x2359 | JNI alloc memory failed, please see taoslog for more details | Insufficient memory | Memory allocation error in local connection; check taos logs for troubleshooting. |
| 0x2371 | Consumer properties must not be null! | Empty subscription parameters | Parameters are empty when creating a subscription; fill in valid parameters. |
| 0x2372 | Configs contain empty key, failed to set consumer property | Empty value in parameter key | The parameter key contains empty values; fill in valid parameters. |
| 0x2373 | Failed to set consumer property, | Empty value in parameter value | The parameter value contains empty values; fill in valid parameters. |
| 0x2375 | Topic reference has been destroyed | Invalid topic reference | During data subscription creation, the topic reference was released; check the connection to TDengine TSDB. |
| 0x2376 | Failed to set consumer topic, topic name is empty | Empty topic name | During data subscription creation, the subscribed topic name is empty; verify the specified topic name is correct. |
| 0x2377 | Consumer reference has been destroyed | Invalid consumer reference | The data transmission channel for the subscription is closed; check the connection to TDengine TSDB. |
| 0x2378 | Consumer create error | Failed to create data subscription | Troubleshoot using error information and taos logs. |
| 0x2379 | Seek offset must not be a negative number | Incorrect parameter | The parameter for the seek interface cannot be negative; use valid parameters. |
| 0x237A | VGroup not found in result set | VGroup not assigned to the current consumer | The Rebalance mechanism causes the consumer and VGroup to be unbound. |
| 0x2390 | Background thread write error in Efficient Writing | Write error in efficient write background thread | Stop writing and rebuild the connection. |
| 100 | Invalid variables | Illegal parameters | Check the corresponding interface specifications and adjust parameter types and sizes. |
| 101 | Invalid URL | Incorrect URL | Verify the URL is filled in correctly. |
| 102 | Received server data but did not find a callback for processing | Server data received but no upper-layer callback found | Check the network environment. |
| 103 | Invalid message type | Unrecognizable received message type | Verify the server is functioning properly. |
| 105 | WebSocket request timeout | Request timeout | Check network status and verify the taosAdapter service is running. |
| 106 | Authentication fail | Incorrect authentication parameters | Verify the username and password are correct. |
| 107 | Unknown SQL type in TDengine | Unsupported data type | Check the data types supported by TDengine TSDB. |
| 108 | Connection has been closed | The connection has been closed | Check if the Connection is used after being closed, or verify connection status. |
| 109 | Fetch block data parse fail | Data parsing exception | Parsing of fetched query data failed; confirm the connector version matches the TDengine server version. |
| 110 | WebSocket connection has reached its maximum limit | Maximum number of WebSocket connections reached | Report an issue on GitHub. |
| 111 | Topic partitions and positions are not equal in length | Mismatch between offset data for given partitions and topic partitions | Re-subscribe. |
| 112 | Version mismatch. The minimum required TDengine TSDB version is 3.3.2.0 | Version mismatch | TDengine TSDB versions lower than 3.3.2.0 are not supported; upgrade to version 3.3.2.0 or higher. |
| 0xF001 | WebSocket Reconnection Failed | Reconnection failed due to the exit of the connected taosAdapter | Check the status of taosAdapter and retry after a period of time. |
| 0xF002 | WebSocket Message Mismatch | Duplicate request IDs generated | Close the current connection, wait for a period, then reconnect; do not pass duplicate request IDs. |
| 0xF003 | WebSocket Connection Closed | Using a closed WebSocket connection | Close the current connection and retry with a new connection. |
| 0xF004 | WebSocket Write Timeout | WebSocket write request timeout | Check for network issues, increase the write timeout parameter, then close the current connection and retry with a new one. |
| 0xF005 | WebSocket Connection Failed | The connected taosAdapter exited | Check the status of taosAdapter and retry after a period of time. |
| 0xF006 | WebSocket Close Message Received | taosAdapter closed the connection due to heartbeat timeout caused by network issues | Check for network issues and retry after a period of time. |
| 0xFFFF | taosAdapter request parameter or process error | taosAdapter request parameter or process error | Check the error cause based on the error message |
| 0xFFFE | taosAdapter query request exceeded the limit | taosAdapter query request exceeded the limit | Reduce the concurrency of query requests |
