Frequently encountered error codes in era.log

0x1203 – UPD_RETVAL_BAD_URL
Update module error – incorrectly entered update server name.

0x1204 – UPD_RETVAL_CANT_DOWNLOAD
This error can appear:

when updating through HTTP
- update server returns an HTTP error code between 400−500 except for 401, 403, 404, and 407
- if updates are downloaded from a CISCO based server and the HTTP authentication response format has been changed

when updating from a shared folder:
- returned error does not fall into the categories bad authentication or file not found (e.g., connection interrupted or non existing server, etc.)

both update methods
- if all of the servers listed in the file upd.ver could not be found (the file is located in %ALLUSERSPROFILE%\Application Data\ESET\ESET Remote Administrator\Server\updfiles)
- failed to contact the failsafe server (probably due to deletion of the corresponding ESET entries in the registry)

incorrect proxy server configuration in ERAS
- The administrator must specify the proxy server in the proper format.

0x2001 – UPD_RETVAL_AUTHORIZATION_FAILED
Authentication to update server failed, incorrect username or password.

0x2102 – UPD_RETVAL_BAD_REPLY
This update module error can be encountered if a proxy server is used to mediate Internet connection – namely Webwasher proxy.

0x2104 – UPD_RETVAL_SERVER_ERROR
Update module error indicating an HTTP error code higher than 500. If the ESET HTTP server is being used, error 500 indicates a problem with memory allocation.

0x2105 – UPD_RETVAL_INTERRUPTED
This update module error can be encountered if a proxy server is used to mediate the Internet connection – namely Webwasher proxy.