cancel
Showing results for 
Search instead for 
Did you mean: 

Installation of McAfee Agent version 4.5 patch 1 (or older) succeed, version 4.5 patch 2 (or later) fail

Hi all,

we have an infrastructure of ~1200  W2K3 / W2K8 servers, all with McAfee Agent running fine, except on one machine where we can't get it installed.

The installation (from ePO or from the McAfee Agent setup GUI) of MA 4.5 patch 2 and MA 4.6 both fail with the message :

"error 1603: Fatal error during installation" .

The strange thing is that all older versions (including MA 4.5 patch 1, MA 4.0) install and work correctly on this W2K8 machine.

I compared the MSIxxx.log produced in both cases,  and the only real difference I could find is this :

MA 4.5 patch 1 (succeeding)MA 4.5 patch 2 (failing)

...

MSI (s) (38:B4) [14:29:03:438]: Executing op: ActionStart(Name=AddToWindowsFirewall,,)

MSI (s) (38:B4) [14:29:03:438]: Executing op: CustomActionSchedule(Action=AddToWindowsFirewall,ActionType=3073,Source=BinaryData,Target=addToWindowsFirewall,)

MSI (s) (38:14) [14:29:03:469]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI88DE.tmp, Entrypoint: addToWindowsFirewall

CustAct [14:29:3:485] main addToWindowsFirewall START

  

CustAct [14:29:3:500] main addToWindowsFirewall END

...

...

MSI (s) (20:F4) [10:15:54:080]: Executing op: ActionStart(Name=AddToWindowsFirewall,,)

MSI (s) (20:F4) [10:15:54:080]: Executing op: CustomActionSchedule(Action=AddToWindowsFirewall,ActionType=3073,Source=BinaryData,Target=addToWindowsFirewall,)

MSI (s) (20:18) [10:15:54:127]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBF39.tmp, Entrypoint: addToWindowsFirewall

CustAct [10:15:54:174] main addToWindowsFirewall START

CustAct [10:15:54:283] Cmalib Error trace:

CustAct [10:15:54:283] main   [addToWindowsFirewall START]->

CustAct [10:15:54:283] Cmalib   [Add CMA to Windows Firewall]->

CustAct [10:15:54:283] Cmalib    error -2147024891: Access is denied.

CustAct [10:15:54:283] main addToWindowsFirewall END

CustomAction AddToWindowsFirewall returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

...

Of course, I checked the firewall settings of the W2K8 box, as well as the permissions on the different registry hives related to firewall configuration keys, but found no difference between this particular machine and the other machines.

Has anyone already encountered this problem, or does anyone have an idea to track the failing operation of the setup process ?

Thanks in advance !

Michael

on 08/08/11 09:29:57 CEST