Troubleshooting; Faq; Windows Server 2000/2003; What Is The Meaning Of The Gle Error Code - ESET REMOTE ADMINISTRATOR - ANNEXE 636 Installation Manual

Table of Contents

Advertisement

9. Troubleshooting

9.1

FAQ

This chapter contains solutions to the most frequently asked questions and problems related to installation and
operation of ERA.
9.1.1
Problems installing ESET Remote Administrator to Windows server 2000/2003
Cause:
One of the possible causes may be the Terminal Server running on the system in the execution mode.
Solution:
Microsoft advises switching the Terminal Server to "install" mode while installing programs to a system with
Terminal Server service running. This can be done either through Control Panel > Add/Remove programs, or
by opening a command prompt and issuing the change user /install command. After installation, type change user /
execute to return to the Terminal Server to execution mode. For step‑by‑step instructions on this process, see the
following article:
http://support.microsoft.com/kb/320185.

9.1.2 What is the meaning of the GLE error code?

Installing ESET Smart Security or ESET NOD32 Antivirus via the Remote Administrator Console can occasionally
generate a GLE error. To find the meaning of any GLE error number, follow the steps below:
1) Open a command prompt by clicking Start → Run. Type cmd and click OK.
2) At the command prompt, type: net helpmsg error_number
Example: "net helpmsg 55"
Result: The specified network resource or device is no longer available.
9.2

Frequently encountered error codes

During the operation of ERA, you may encounter error messages which contain error codes indicating a problem
with some feature or operation. Section 8.2.1 below outlines the most frequently encountered error codes when
performing push installs, as well as errors that can be found in the ERAS log.
9.2.1 Error messages displayed when using ESET Remote Administrator to remotely install ESET Smart Security or
ESET NOD32 Antivirus
SC error code 6, GLE error code 53 Could not set up IPC connection to target computer
To set up an IPC connection, these requirements should be met:
1. TCP/IP stack installed on the computer where ERAS is installed, as well as on the target computer.
2. File and Printer Sharing for Microsoft Network must be installed.
3. File sharing ports must be open (135−139, 445).
4. The target computer must answer ping requests.
SC error code 6, GLE error code 67 Could not install ESET installer on target computer
The administrative share ADMIN$ must be accessible on the client's system drive.
SC error code 6, GLE error code 1326 Could not set up IPC connection to target computer, probably due to
a wrong username or password
Administrator's username and password have not been typed incorrectly or has not been entered at all.
SC error code 6, GLE error code 1327 Could not set up IPC connection to target computer
Administrator's password field is blank. A remote push installation cannot work with a blank password field.
SC error code 11, GLE error code 5 Could not install ESET installer on target computer
The installer cannot access the client computer due to insufficient access rights (Access Denied).
SC error code 11, GLE error code 1726 Could not install NOD32 Installer onto target computer
This error code displays after a repeated attempt to install, if the Push Installation window was not closed after the
first attempt.
69

Advertisement

Table of Contents
loading

This manual is also suitable for:

Remote administrator

Table of Contents