Error Codes
This page lists all available error codes and descriptions.
| Code | Description |
|---|---|
| E11 | Could not establish connection to source. This is typically due to an invalid IP address, or a networking problem. It may also be caused by routing or firewall configuration. Double check IP settings or consult your IT group to verify network setup. |
| E12 | Time out attempting to establish connection. This generally indicates the source is down or unavailable. It may also be caused by routing or firewall configuration. Double check IP settings or consult your IT group to verify network setup. |
| E13 | A connection was established, but timed out before receiving a response. This is generally a networking problem. Verify correct IP address and port number. And check that the remote device is up and functioning as expected. If problems persist, consult your IT group to verify network health and rule out routing or firewall related issues. |
| E14 | You do not have permission to access this resource. Check your credentials for the external system, and verify they have the proper permissions. If a TLS certifcate is required, verify proper certificate(s) are installed under the Certificates tab. |
| E15 | A secure connection could not be established due to an invalid or missing certificate. Verify proper certificate(s) are installed under the Certificates tab. |
| E16 | The request was rejected because the client exceeded the allowed rate limit. Reduce polling frequency to stay within limits. |
| E17 | The connection to the remote system was closed while the request was in progress. This may be caused by a network interruption, timeout, or the remote system terminating the connection. Retrying the request may succeed. |
| E18 | An operation did not complete within its expected time. Contact support for additional information. |
| E101 | Reject-Message-To-Network response with reason code 0: Other error. Refer to source vendor or BMS network maintainer for more information. |
| E102 | The router is not directly connected to DNET and cannot find a router to DNET on any directly connected network using Who-Is-Router-To-Network messages. Refer to source vendor or BMS network maintainer for more information. |
| E31 | Cannot read point value since remote source is reporting a fault condition. Check the diagnostics or logs on the remote source for root cause. |
| E32 | Remote system is reporting point value as NaN. Check the diagnostics or logs on the remote source for root cause. |
| E33 | Remote system is reporting point does not exist or cannot be found. Verify the point address or check diagnostics or logs on the remote source for root cause. |
| E34 | Remote system is reporting point does not supported write operations. |
| E35 | The formula for this point could not be evaluated. Review the formula definition in the corresponding source map. |
| E36 | The remote point is known but has not yet reported a value. This typically occurs on startup before the device has completed its first scan, or if the point has never been written to. |
| E37 | A write was issued but the remote device never confirmed the commanded value within the expected window. The write may or may not have been applied. Verify the current value on the remote device, and check that the node is online and the source is polling normally. Re-issue the write to retry. |
| E301 | Releasing a commanded value is not supported by this device or point. Write a new value to update the current value. |