1 |
The far end closed the socket connection. Check the error logs on the AEVCS Server for more information. |
100 |
The reset aecvcs-link command was used to close the socket connection |
101 |
The AESVCS Interface on the IP Services form was disabled. |
102 |
The AESVCS Interface was removed from the IP Services form. |
103 |
The AE Services Server was disabled on the AE Services Administration page of the IP Services form. |
104 |
The AE Services Server was deleted on the AE Services Administration page of the IP Services form. |
200 |
The socket connection closed due to an internal error. Escalate if the problem persists. |
201 |
The socket connection was unexpectedly closed by Communication Manager. Escalate if the problem persists. |
202 |
Communication Manager detected an error and closed the socket connection. Escalate if the problem persists. |
203 |
Communication Manager detected an error reading from the socket and closed the connection. Escalate if the problem persists. |
204 |
Communication Manager failed to write a complete message and closed the socket connection. Escalate if the problem persists. |
205 |
AE Server established a new connection causing Communication Manager to close the existing one. Escalate if the problem persists. |
206 |
Communication Manager failed to send a heartbeat request and closed the socket connection. Escalate if the problem persists. |
207 |
Communication Manager detected a protocol violation and closed the socket connection. Escalate if the problem persists. |
208 |
Communication Manager detected processing the data from the AESVCS Server and closed the socket connection. Escalate if the problem persists. |
209 |
Communication Manager could not read data from the socket and closed the connection. Escalate if the problem persists. |