problems upgrading to NOD32 AV 4.2.40

Marcos - what is unclear about the problem description?

Or are you saying that you are unable to reproduce it?

I'll be able to test this myself in the next day or two, as I'll be upgrading my ERAC/RAS to 4.1.138, and pushing out 4.2.67 to all of the clients...

 

Here are log messages from einstaller.log of a PC where the upgrade was unsuccessful, as the user (not having local admin rights) was logged on during the installation:

Code:

[2010-11-19 17:34:49.131] Status 1100, ID 21: ESET Installer (4.0.138) is preparing to install.
[2010-11-19 17:34:49.162] Status 1451, ID 23: ESET Installer is trying to connect to 'myserver:2224'.
[2010-11-19 17:34:54.740] Status 1400, ID 25: ESET Installer is creating a temporary file.
[2010-11-19 17:35:54.741] Status 1400, ID 27: ESET Installer is downloading an installation package 'ESET NOD32 Antivirus 4.2 BE for Win32 laptop' from server 'myserver:2224'.
[2010-11-19 17:36:05.257] Status 1300, ID 8: ESET Installer is preparing to install the package.
[2010-11-19 17:36:05.257] Status 1550, ID 92: ESET Installer is installing the package.
[2010-11-19 17:37:45.634] Status 1501, ID 96: ESET Installer is trying to reconnect to 'myserver:2224'.
[2010-11-19 17:37:45.634] Status 1500, ID 94: Reconnected to 'myserver:2224'.
[2010-11-19 17:37:45.634] Status 2401, ID 90: Failure during the package install - exit code: 1603, description: Fatal error during installation.
[2010-11-19 17:37:45.634] Status 1600, ID 105: Service stuff cleanup finished with return code 0.

After that I had to restart the machine twice to finish the installation (as I explained earlier in this thread).

I also run the Diagnostic task from the RAC, as you suggested. Here is the log from the task:

Code:

pcxxx.mydomain.local
Diagnostics user context:                                 mydomain\administrator
Operating System:                                         Microsoft Windows XP
Operating System Version:                                 5.1
ESET Security Product Name:                               ESET NOD32 Antivirus
ESET Security Product Version:                            4.2.67.10
ESET Security Product Virus Signature Database:           5634 (20101119)

Push installation simulation steps:
Setting IPC$ Connection:                                  Result Code: 0 (The operation completed successfully.)
Remote Registry Connecting (OS Info):                     Result Code: 0 (The operation completed successfully.)
Remote Registry Opening (OS Info):                        Result Code: 0 (The operation completed successfully.)
Remote Registry Reading (OS Info):                        Result Code: 0 (The operation completed successfully.)
Remote Registry Connecting (ESET Security Product Info):  Result Code: 0 (The operation completed successfully.)
Remote Registry Opening (ESET Security Product Info):     Result Code: 0 (The operation completed successfully.)
Remote Registry Reading (ESET Security Product Info):     Result Code: 0 (The operation completed successfully.)
Setting ADMIN$ Connection:                                Result Code: 0 (The operation completed successfully.)
Copying ESET Installer:                                   Result Code: 0 (The operation completed successfully.)
Setting IPC$ Connection:                                  Result Code: 0 (The operation completed successfully.)
Registering ESET Installer as a Service:                  Result Code: 0 (The operation completed successfully.)
Diagnostics conclusion:                                   Result Code: 0 (The operation completed successfully.)

It seems that it is possible that push installation has errors although the diagnostic task runs fine.

-- rpr.