This one is driving me nuts!
We have a few of the common VScan errors (Dr Watson using IE etc) that seem to be fixed with the latest superdat.
However on my windows NT computers, I cannot use ME to update to the latest superdat. Everything seem to be OK, but after an update you see
VirusScan 4.5.0 NOT installed OK Error
on the console. Looking at the log further down, everything is OK apart from
Install failed MSIEXEC returned error code "1603"
right at the end of the VScan log. There are no other errors and it does seem to be installed OK, but because ME sees it as a failure, I can't issue remote scans, view scan status etc. It wants me to apply the configuration again (with the same results).
I am using SP1, have tried completely removing McAfee from the target PC (including manually stopping the service and seleting the NTME directory - something the uninstall didn't do!), resinstalling the 4.5 client manually (this goes on fine) then updating but I still get the same results.
Have just done an install on a new Win2K Pc, and it has worked fine. Updated Ok, have just done a remote scan.
Any clues ot suggestions gratefully recieved....
We have a few of the common VScan errors (Dr Watson using IE etc) that seem to be fixed with the latest superdat.
However on my windows NT computers, I cannot use ME to update to the latest superdat. Everything seem to be OK, but after an update you see
VirusScan 4.5.0 NOT installed OK Error
on the console. Looking at the log further down, everything is OK apart from
Install failed MSIEXEC returned error code "1603"
right at the end of the VScan log. There are no other errors and it does seem to be installed OK, but because ME sees it as a failure, I can't issue remote scans, view scan status etc. It wants me to apply the configuration again (with the same results).
I am using SP1, have tried completely removing McAfee from the target PC (including manually stopping the service and seleting the NTME directory - something the uninstall didn't do!), resinstalling the 4.5 client manually (this goes on fine) then updating but I still get the same results.
Have just done an install on a new Win2K Pc, and it has worked fine. Updated Ok, have just done a remote scan.
Any clues ot suggestions gratefully recieved....