Installation Errors

Are the error messages documented anywhere? I'm getting these trying to push installs to clients:

- Could not setup IPC connection to target computer (SC error code 6, GLE error code 1203) (a retry sometimes works)

- Could not retrieve required information from target computer (RES error code 14, GLE error code 997)

- Failure during NOD32 install - exit code -3

I've tried rebooting, manually installing from the client, and /FORCEOLD switch, but still can't install the client on some workstations (NT & W2K). What else should I try?

 

GLE errors are Windows error codes - GetLastError() function.
List avaible here

 

Ok, that helps a bit... thanks.

997 = Overlapped I/O operation is in progress.

I would think a reboot would correct this, but that didn't help. Any idea on what this means?

 

Is something running and uses the same way that Nod32 takes for installation (IPC$ share) ?

 

Nothing comes to mind... it's a pretty standard configuration over all of our clients.

The install fails if I run the install package locally too (not RAC). Does it still communicate with the server to complete the install when you run the package from the client?

 

By package you mean the 'nod32installer.exe' file ?
If this, it will communicate to the server as the real package is on it. It is the *.nip file. The way is the same, only the start point (launch from RAC or locally) is different.

 

Yeah, I tried running it from the package folder under C:\program files\eset\RA\Server\packages on the server.

This is what's in the nod32installer.log on the client:

[2005-06-29 19:40:10.411] Status 1: NOD32 Installer is preparing to install.
[2005-06-29 19:40:10.427] Status 1: NOD32 Installer is trying to connect to 'server1:2224'.
[2005-06-29 19:40:11.208] Status 1: NOD32 Installer is sending installation request.
[2005-06-29 19:40:11.208] Status 20000: NOD32 Installer was told to quit by the server 'server1:2224'.

 

Maybe the server refused to send out the installation package because of some leftovers from an unsuccessful installation. I'd try rebooting the workstation and removing installation leftovers using the option in the RA context menu.

 

Tried that too...

I still get "Failure during NOD32 install - exit code: -3" at the server, and the following in the nod32installer.log on the client:

[2005-06-30 10:35:49.078] Status 1: NOD32 Installer is preparing to install.
[2005-06-30 10:35:49.078] Status 1: NOD32 Installer is trying to connect to 'server1:2224'.
[2005-06-30 10:35:49.208] Status 1: NOD32 Installer is creating a temporary file.
[2005-06-30 10:35:49.208] Status 1: NOD32 Installer is downloading an installation package 'mypackage' from server 'server1:2224'.
[2005-06-30 10:35:59.012] Status 1: NOD32 Installer is installing NOD32.
[2005-06-30 10:35:59.363] Status 1012: Failure during NOD32 install - exit code: -3.

 

Hi tp2005:

A normal NOD32 exit code of 3 is virus in memory.

Is the computer in question already infected?

One could share out the computer's C: and perform a remote scan to check.

 

Please send me a PM, I will provide you with further instructions.

PS: Sorry for the delay, I'd been off for 2 days.

 

I ran a remote scan (via mapped drive) of one of the computers I'm getting the "exit code: -3" error on. It came up clean except for the following 3 errors (and the usual file locked messages):

Y:\winnt\system32\t2embed.dll >> GZ >> t2embed.dll - error - unknown compression method
Y:\WINNT\Windows Update Setup Files\IENT_S1.CAB »CAB »IENT_1.CAB »CAB »MSHTML.DLL - next archive volume not found
Y:\WINNT\Windows Update Setup Files\IE_EXTRA.CAB »CAB »t2embed.dll »GZ »t2embed.dll - error - unknown compression method

Do you think this might have something to do with the install failures?

 

No, apparently the GZIP archives were created using a method not supported by NOD32.

 

Hi

I keep getting the same error but only on W2K Workstation and Server! Installations on XP work. Even rebooting doesn't help. Anyone an idea why??

Cheers

Adra

 

Check if the RAS service is run in the account of a specific admin user instead of the local system account.

 

I have also been running into the following error a lot:
"Could not retrieve required information from target computer (RES error code 14, GLE error code 997)"

As a couple others have mentioned, it only seems to occur with W2K remote installs. I have tried everything that has been mentioned in this thread and a few others and nothing seems to work. Can you provide any more suggestions as to what the problem might be? Thanks.

 

This could be that you are running a Win2k3 SP1 server whilst your RAS sevice is not run in the account of a specific admin user, but the local system account (default).

 

I changed the RAS service to run as an admin account, however now I am unable to connect to the server with the console. Any suggestions?

 

Our school board just recieved this product and I must say so far I like but am having deployment problems as well. The push function works ok on most computers but to be sure that every computer in use gets my package I would like to use the login Script option but when installing I get these errors in the log.

Any help would be appreciated.

[2006-05-10 14:05:55.016] Status 1: NOD32 Installer is preparing to install.
[2006-05-10 14:05:55.016] Status 1: NOD32 Installer is trying to connect to 'RSS-FS:2224'.
[2006-05-10 14:05:55.036] Status 1: NOD32 Installer is sending installation request.
[2006-05-10 14:05:55.126] Status 2001: Could not install NOD32 Installer onto target computer (SC error code 11, GLE error code 5)


[2006-05-10 14:57:15.816] Status 1: NOD32 Installer is preparing to install.
[2006-05-10 14:57:15.816] Status 1: NOD32 Installer is trying to connect to 'RSS-FS:2224'.
[2006-05-10 14:57:15.886] Status 1: NOD32 Installer is sending installation request.
[2006-05-10 14:57:15.886] Status 20000: NOD32 Installer was told to quit by the server 'RSS-FS:2224'.

 

I solved it.

I didn't have a default login set in the "Set Default Login..." area of the console.

 

You can find some of the most common errors in this document: http://u4.eset.com/manuals/nod32raman.pdf

GLE Error code is access_denied (zashitas post), indicating that you don't have enogh rights on the workstation to install nod32.


As marcos said, for RAS running on W2K3 SP1 you have to specify an admin (domain admin?) account instead of local system, but you can turn it back as ssoon as all W2K computers are equiped with NOD32.


cheers
Adra

 

I tried connecting to the server from the remote admin. console this morning and everything seems to be working fine. The first Win2K install I tried worked wonderfully. There must have just been a delay in the setting refresh after changing the service logon.

Thanks so much for all your help.