86
10.2.2 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 HTML 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 proxy server in the 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.
10.3 How to diagnose problems with ERAS?
If you suspect that there is something wrong with ERAS or if it is not functioning correctly, we recommend that you
follow these steps:
1) Check the ERAS log: Click
Tools
>
Server Options
from the ERAC main menu. From the
Server Options
window,
click the
Logging
tab and then click
View log
.
2) If you see no error messages, increase the
Log verbosity
level in the
Server Options
window to Level 5. After you
have tracked down the problem, we recommend switching back to the default value.
3) You may also be able to troubleshoot problems by turning on the database debug log in the same tab – see section
Debug Log
. We recommend that you only activate the
Debug log
when attempting to duplicate the problem.
4) If you see any error codes other than those mentioned in this documentation, please contact ESET Customer Care.
Please describe the behavior of the program, how to replicate the problem or how to avoid it. It is very important to
include the program version of all ESET security products involved (i.e., ERAS, ERAC, ESET Smart Security, ESET
NOD32 Antivirus).
