1# Link Enhancement Error Codes 2 3> **NOTE** 4> 5> This topic describes only module-specific error codes. For details about universal error codes, see [Universal Error Codes](../errorcode-universal.md). 6 7## 32390200 Client Connection Timeout 8 9**Error Message** 10 11Connect timeout. 12 13**Description** 14 15This error code is reported if a client connection fails due to a timeout. 16 17**Possible Causes** 18 19The server does not respond before the timeout. 20 21**Solution** 22 23Try again after the timeout. If a connection to the remote device exists, disconnect the connection and try again. 24 25## 32390201 Server Service Not Started 26 27**Error Message** 28 29Peer server is not started. 30 31**Description** 32 33This error code is reported if the corresponding service on the server is not started. 34 35**Possible Causes** 36 37The corresponding service on the server is not started. 38 39**Solution** 40 41Check whether the corresponding service is started on the target device. If not, start the service and then initiate a connection. 42 43## 32390202 Number of Services Exceeding the Limit 44 45**Error Message** 46 47The number of servers exceeds the limit. 48 49**Description** 50 51This error code is reported if the number of services exceeds the limit. 52 53**Possible Causes** 54 55The number of requested services exceeds 10. 56 57**Solution** 58 59Call **close()** to release services that are no longer used. 60 61## 32390203 Duplicate Service Name 62 63**Error Message** 64 65Duplicate server name. 66 67**Description** 68 69This error code is reported if a service with the same name is registered repeatedly. 70 71**Possible Causes** 72 73The name of the service being created already exists. 74 75**Solution** 76 77Check whether a service with the same name already exists. If yes, register the service with a different name. 78 79## 32390204 Number of Connections Exceeding the Limit 80 81**Error Message** 82 83The number of connection exceeds the limit. 84 85**Description** 86 87This error code is reported if the number of connections exceeds the limit. 88 89**Possible Causes** 90 91The number of requested connections exceeds 10. 92 93**Solution** 94 95Call **close()** to release connections that are no longer used. 96 97## 32390205 Connection Unavailable 98 99**Error Message** 100 101Connection is not ready. 102 103**Description** 104 105This error code is reported if a connection is unavailable. 106 107**Possible Causes** 108 109The client or server application is using a connection that has been disconnected. 110 111**Solution** 112 113Check whether the connection is available. If the connection is available, use the connection to perform operations. 114 115## 32390206 Invalid Parameter 116 117**Error Message** 118 119Invalid parameter. Possible causes: 1. Mandatory parameters are left unspecified; 2. Incorrect parameter types; 3. Parameter verification failed. 120 121**Description** 122 123This error code is reported if a parameter is invalid. 124 125**Possible Causes** 126 1271. A mandatory parameter is not passed. 128 1292. A parameter type is incorrect. 130 1313. The number of parameters is incorrect. 132 1334. A parameter is left empty. 134 135**Solution** 136 137Check whether mandatory parameters are passed and whether their types are correct. If the parameter verification fails, rectify the fault based on the possible causes in the API reference. 138 139## 32390300 Internal Error 140 141**Error Message** 142 143Internal error. 144 145**Description** 146 147An internal error occurs. 148 149**Possible Causes** 1501. Invalid input device ID. 151 1522. Invalid input name. 153 1543. Abnormal internal state. 155 1564. Incorrect API usage. 157 1585. System errors, such as null pointer, insufficient memory, unexpected distributed service restart, IPC exception, and JS engine exception. 159 160**Solution** 161 162View the error log to identify the error cause. Take appropriate based on the actual cause: 163 1641. If the device ID passed to the API is the same as that obtained from the Bluetooth system API, check whether the peer device is in the advertising state. 165 1662. If the name passed from the client to the server is the same as that passed from the server to the client, check whether the name is correct by referring to the API reference. 167 1683. Check whether objects are used after being closed. 169 1704. Check whether the API is correctly used by referring to the API reference. 171 1725. If the problem persists, restart or update the application or upgrade the device version. 173