Info: Unofficial List of Agent Error codes and messages

This list is not supported or guaranteed to be accurate. The actual list of Agent error codes has not been compiled or published by Venafi, but this is the beginning of a user supported list for reference and research assistance only. The errors have been gleaned from actual agent logs as opposed to looking at the code. Therefore, there may be differences depending on what version of the product you are using.

1701 Unable to connect to server:XXXXX\vedclient\authorize...
1705 Unable to acquire session key from: XXXX\vedclient\...
1714 Unexpected protocol response, server XXXX code: "500" msg: HTTP/1.1 500 Internal Server Error
1705 Unable to acquire session key from: HTTPS://XXXX/vedclient
1715 CURL transport failure from server: XXXX, error: curl: (60) SSL certificate problem, verify that the CA cert is OK.
1801 Unable to acquire authorization requirements document.
1805 Unable to authenticate with server, response: curl: (0) No error
1806 Unable to open Agent SSL peer verification trust store
1808 Agent SSL peer verification trust store not found and OU match failure
1824 URL authorize/register failed with HTTP status: 401, Bad registration code or no matching rules. Registration failed.
1825 URL authorize/register failed, received HTTP status (500) without any JSON data"
1831 Failed to register with the TPP REST server: "vam_client_op_register()"
1832 Failed to acquire a session key from the TPP REST server: vam_client_op_session()
1835 URL authorize/newsession, could not connect to server, CURL code: 7, error: Couldn't connect to server"
1844 URL authorize/newsession, received "Unauthorized (401) - Not authorized for Client+Default:11:2"
1862 SSL OU failed validity test
1881 SSL Certificate is revoked 
1894 SSL CRL download, unable to download all required CRL files"


Troubleshooting Comment:

These error messages "point" to possible problems in the configuration of either the agent, the network, or the Venafi platform. Troubleshooting agent connectivity tends to lean back to ensuring the agent is configured correctly to communicate with the server, looking for recent changes (e.g. security) and ensuring there are no communication blocks. Therefore, no specific "troubleshooting steps" have been attached to each error.

Was this article helpful?
0 out of 0 found this helpful