User`s guide

445, 135 - 139), or the relevant station is not visible
on the level of network places.
Could not install NOD32 Installer onto target computer (SC
error code 6, GLE error code 67)
- It is not possible to
get to a workstation through share ADMIN$ (or it is a
workstation with Windows XP Home, which does not
support such system sharing)
Could not retrieve required information from target compu-
ter (RES error code 13, GLE error code 997)
- Probably
„Remote registry“ service is not enabled at the sta-
tion. If the RA server works on server with Windows
2003, the system account, under which the service
NOD32 RAS is running, does not have the right to read
registers on a remote system. In this case, it is neces-
sary to dene data of domain administrator‘s account
(name and password) in the properties of NOD32 RAS
service and restart the service (after the execution of
remote installation we recommend to re-setup the
system account).
Could not set up IPC connection to target computer (SC er
-
ror code 6, GLE error code 1327) - The password of ad-
ministrator cannot be empty.
Could not set up IPC connection to target computer (SC error
code 6, GLE error code 1326) - „Use simple le sharing“
function is enabled.
Could not set up IPC connection to target computer (SC er-
ror code 6, GLE error code 51) - „Server“system service
is not enabled on the workstation.
Failure during NOD32 uninstall - exit code: 207
- For unin-
stall it is required to dene a password. In the unin-
stall package it is required to dene a parameter /
PWD=”password”
Possible error messages produced by
the NOD32 workstation
The error messages can be produced directly by the
installer, which is used with all Eset MS Windows based
products (i.e. the installer launched by the le SETUP.EXE,
or after running the installation package downloaded
from the Eset company website).
Error Meaning
101 administration rights required
102 no configuration file specified
103 lack of memory
104 old version of the Operating System
105 cannot create a temporary folder to extract the installation files
106 error extracting files
107 internal program error
108 attempting to overinstall with an older component
109 internal program error
110 internal program error
111 cannot create a file on the disk
112 internal program error
113 internal program error
114 SETUP.XML corrupt or missing
115 the current version not compatible with the old version (you need to uninstall the old version)
116 error writing to the operating system registry
117 upgrade required
118 attempting to overinstall with a different language version (uninstall the previous version first
119 corrupt uninstall file
120 registering service error
121 component installation error
122 cannot install a certain component to the computer
123 attempting to install the trial version again error
124 wrong Operating System, the installer is intended for the Windows NT/2000/XP/2003 Operating System
125 wrong Operating System, the installer is intended for the Windows 95/98/ME Operating System
To nd out the exact reason why the installation
failed, run the install le (i.e.: the SETUP.EXE le) with
the /TEST parameter (i.e.: SETUP.EXE /TEST). The detailed
description of the installation progress will be saved in
the NSETUP.LOG le.