ESET LAN Update Server 2.7, Installation Manual

Page: 66 / 84

Administration Installation Guide
66
Error messages
As with most reputable software, NOD32 Remote Administrator can return
more detailed information about a problem that has occurred.
The error message is, in many cases, accompanied with its SC error code
and GLE error code.
SC codes mostly contain only internal information for easier orientation in
the problem code, GLE codes (Get Last Error) are more important for the
user. These are classic “Win32 Error Codes” – a list of such codes can be
found on this webpage:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/
system_error_codes.asp
Following are some commonly found errors:
Problem:
During remote installation, the error “Could not set up IPC connection to
target computer (SC error code 6, GLE error code 1326)”
The GLE error means that a wrong or unknown password for the account
(under which remote installation was to take part) was entered.
Problem:
Quite often you can come across this message caused by the
nod32installer.exe: “NOD32 Installer was told to quit by the server XYZ.”
It means that installation on the chosen client workstation was already
performed (successful or not) and RA refuses to repeat it.
Solution:
This message keeps on occurring until the administrator deletes the
message related to the workstation in the Remote Install tab from:
the bottom of the ‘List of pending and failed installations’ panel or
the ‘Successful Installs List’ tab.
You can right click on the specific client and select ‘Clear’.
Problem:
The error message “NOD32 Installer could not connect to server XYZ”
means that RAS is not accessible to the file nod32installer.exe.
Solution:
It is recommended to check, whether XYZ can really be localized in
the network (eg: by ‘pinging’ XYZ), or whether the communication is not
blocked by a firewall.
►
►