|
Home Edition/ESET Smart Security/Linux/BSD
GLE error code 997
During a remote (push) installation, the error Could not retrieve required information from target computer (RES error code 14, GLE error code 997) is sometimes encountered.
This problem can occur if the installation of NOD32 takes place from NOD32 Remote Administrator Server on a Windows 2003 Server to a client running the Windows 2000 operating system.
To solve the problem, start the NOD32 RAS service from the Administrator account on the server by following the steps below:
1.
Click Start → Control Panel → Administrative Tools → Services (If you are using Windows XP or Vista, you may need to switch Control Panel to Classic View in order to see the Administrative Tools option).
2.
Right-click on the NOD32 Remote Administrator service, and from the context menu, click Properties.
3.
The NOD32 Remote Administrator Server Properties window will appear. From the Log On tab, select This Account and type Administrator.
4.
Click OK to close the Server Properties window, right-click the NOD32 Remote Administrator service and click Restart from the context menu.
5.
Attempt the remote (push) installation again.
NOTE: If the installation finishes successfully, we recommend switching the NOD32 Remote Administrator service back to the default setting (See step 3, select Local system account).
Push Installation Requirements and Checklist
NOD32 Remote Administrator allows remote installations from the Remote Administrator Console to any workstation on the network with a Windows NT/ 2000/XP/2003/Vista operating system. This function is called a Push installation. The steps in this document describe the main requirements for configuration of this process.
While installation to standardized networking environments is relatively simple, problems can arise due to differences in architecture and configuration from network to network.
The following can be used both as a requirements check list for configuring a push installation as well as a trouble-shooting guide during the remote installation process. Verifying each of the tasks below is strongly recommended before performing the first trial installation on the client's network:
1.
The workstation where you are trying to install NOD32 client remotely must answer a ping from the computer where Remote Administrator Server is installed.
2.
If both the workstation and the server are in a mixed environment of Domain and Work Group (or if the server where Remote Administrator is installed has Windows 2003), the Use simple file sharing (located under the Tools → Folder Options → View) option should be disabled.
3.
Both the server and the workstation must have the TCP/IP protocol installed.
4.
Workstation must have the shared resource ADMIN$ activated (Start → Control Panel → Admin Tools → Computer Mgmnt → Shared Folders → Shares).
5.
The user performing the remote installation must have administrator rights.
6.
The user with administrator rights cannot have a blank password.
7.
The firewall on the network must not block communications or file-sharing between the servers and the workstation.
8.
The (Remote Administrator) server must allow data reception through ports 2222, 2223, and 2224. If the server has any of these ports blocked, communication with the workstations is not possible.
9.
For WinNT/2000/XP/2003 operating systems, verify the following:
-Client workstations are visible in both the server and the workstation connection.
-“File & Print Sharing for Microsoft Networks” must be enabled (Control Panel → Network Connections → Network → Properties)
-The Remote Procedure Call (RPC) service needs to be running on the target.
-The Remote Registry service needs to be running on the target.
-The RPC Locater service should be set to “manual” and need not be running.
10.
IMON should not be enabled on your server. IMON's primary functions are to control HTTP communication (web-browsing) and detect possible infiltrations encountered through using internet email (POP3). Given that the server will not be used as a typical workstation, it's recommended that the module be disabled. NOD32's other modules will provide your server with back-up layers of protection against these threats.
11.
If installing onto WinNT/2000/XP machines via logon script or email, a logon name and password must be defined in the RA console. To set it up, click the Remote Install tab and in the Set Default Logon for E-mail and Logon Script, click the Logon button.
If your network configuration meets these requirements, remote installation will be accomplished without communication problems between the server and the workstations.
Push Installation Errors
NOD32 Remote Administrator allows remote installations from the Remote Administrator Console to any workstation on the network with a Windows NT/ 2000/XP/2003/Vista operating system. This function is called a Push installation. The following list shows the most frequently encountered errors during the Push Installation process.
Error: Could not set up IPC connection to target computer (SC error code 6, GLE error code 53)
Possible Causes:
1. Shared resources are not allowed or installed in the client computer, or on the firewall of the network (ports 445 and 135-139).
2. TCP/IP protocol is not installed on the client machine or the client is not answering the pings from the server.
3. For XP Servers or workstations, the Windows XP system firewall is turned on.
Error: Could not install NOD32 Installer onto target computer (SC error code 6, GLE error code 67)
Cause: Shared resource ADMIN$ is not started or is not on the system hard drive of the client machine.
Error: Access Denied
Cause: The user doesn’t have Administrator rights on the client machine.
Error: NOD32 Installer could not connect to server NAME_OF_SERVER :2224'. (WGLE error code 0)
Cause: Ports 2222, 2223 and/or 2224 are not opened on the server or are not allowed on the network firewall.
Error: Could not set up IPC connection to target computer (SC error code 6, GLE error code 1327)
Cause: Windows Administrator password cannot be blank.
Error: Could not set up IPC connection to target computer (SC error code 6, GLE error code 13
Cause: The option “Use Simple file sharing” is activated in a mixed environment of workgroups and domains.
Error: Could not set up IPC connection to target computer (SC error code 6, GLE error code 51
Cause: The Server service is not being executed on the client machine.
Error: Failure during NOD32 uninstall - exit code: 207
Cause: This error often occurs during uninstall or reinstall of NOD32 in a machine where it was installed previously. The reason for this error is that the NOD32 configuration is locked with a password. To solve this problem, edit the parameters of the command line of the uninstall package, adding the following line:
pwd=setting_password
Where setting_password is the protection password used for the configuration.
Error: Could not retrieve required information from target computer (RES error code 13, GLE
Cause: The Remote Registry Service is not being executed on the client machine.
Error: Install failed (-1022324356)
Cause: Setup.exe file failed or corrupt
To help determine the cause of a failed push installation, run the install file (setup.exe file) with the /TEST parameter. (i.e. setup.exe/test). A detailed description of the installation progress, including any error messages will be saved in the nsetup.txt file. Send the nsetup.txt file to our technical support lab to the address supplied by our support team. Our experts will help you to solve your problem.
For detailed information on running the install file with the /TEST parameter, click here.
To create a new case using our Customer Care Support Form, click here.
Additional Error Codes
If a GLE Error not specified in this document is encountered during the remote installation, please:
Click here
to find the definition of any GLE error code
Click here
for more information and an extensive list of additional error codes
What does that GLE error code mean?
Installing NOD32 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. Click 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.
For more information on GLE error codes, click here.
|
