This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Failed Upgrade 9.5 to 9.7 - error 00000067 (and 80041f02)

When I switched to 9.7 I found that several computers failed to update/upgrade with message: 00000067  Failed to install SAVXP: A product could not be installed because another product with the same function is already installed . 

Following the link in SEC (or searching the knowledgebase for 00000067) you end with a number of articles and the applicable is hard to spot. Searching for "product with the same function" gives better results and leads to article 33554. Although it mentions W2k3 SBS as OS it applies to all Windows versions.

I had a long exchange with Support (case 2861234 ) and the results are not completely satisfactory . Code 80041f02 indicates a competitor product which prevents the installation. This was somewhat surprising as no such software has been installed on the clients for more than a year. Also the 9.5 updates worked without problems. In several cases the offending product has been on the machine since at least 5 (five!) years.

While CRT runs before the initial install and can remove most of the competitor products there is another "internal" check which runs whenever and upgrade install is done (the reason is obvious: detect new installs of possibly conflicting software) - but it doesn't remove the detected products. It seems that with 9.7 quite a number of items have been added to this list - and some of them for rather old versions so that products are flagged (and prevent the upgrade) which co-existed with SESC/SAV literally for years (since at least 7.6).

If you can use Protect Computers (or script an install) CRT will probably remove these products. As this is not always feasible (e.g. remote computers) you have to provide a 9.5 CID for them until you can resolve the issue. Note that when the upgrade fails threat detection data is also not updated.

Can't say if this is really a problem for most of you though - OTOH after many years now, with 9.7, this is the first time I've encountered this issue.

Christian

:15811


This thread was automatically locked due to age.
Parents

  • QC wrote:

    Searching for "product with the same function" gives better results and leads to article 33554. Although it mentions W2k3 SBS as OS it applies to all Windows versions.



    I've updated the article and removed the OS limitation - you're right that this code can be seen on several Windows platforms.


    QC wrote:

    I had a long exchange with Support (case 2861234 ) and the results are not completely satisfactory . Code 80041f02 indicates a competitor product which prevents the installation. This was somewhat surprising as no such software has been installed on the clients for more than a year. Also the 9.5 updates worked without problems. In several cases the offending product has been on the machine since at least 5 (five!) years.


    I've also (tried) to read through your support case (the english parts :smileywink:) and can see that the cause is somewhat unexplained.

    Interestingly... just today I installed a new VMWare machine (using VMWare Fusion for Mac).  It offered to install a free copy of McAfee VirusScan.  The machine already had Sophos 9.5 on it but I thought, hey why not, I'd run the install and see what happens.  The result was McAfee did not notice another AV was already on the machine and happily installed.

    I mention this only to highlight that it is possible to install two anti-virus products side-by-side *if* the second one isn't on the look out for existing AV software.  Since Sophos AutoUpdate doesn't want to degrade the machine's performance by letting two anti-virus products run on the same computer we designed our installer to error out (stop, roll back, alert to the console so you are aware and can decide what to do and NOT just cripple the machine) rather than silently succeed...for now...but there will be trouble ahead.  Hence our product can look like the one behaving in an unexpected way.

    My thoughts on how the issue occurred:  (1) McAfee was installed after Sophos and the two have been running for a while before the 9.7 upgrade occurred or (2) The CRT did not run on these computers or (3) We added a new detection into the CRT to remove the currently installed version of McAfee or (4) The Sophos AutoUpdate check was manually bypassed (as can be done with a couple of registry keys).

    If you can find out when the McAfee product was installed (filter System event logs for MSI installer entries?) and see how long it's been on there that would help.

    :15823
Reply

  • QC wrote:

    Searching for "product with the same function" gives better results and leads to article 33554. Although it mentions W2k3 SBS as OS it applies to all Windows versions.



    I've updated the article and removed the OS limitation - you're right that this code can be seen on several Windows platforms.


    QC wrote:

    I had a long exchange with Support (case 2861234 ) and the results are not completely satisfactory . Code 80041f02 indicates a competitor product which prevents the installation. This was somewhat surprising as no such software has been installed on the clients for more than a year. Also the 9.5 updates worked without problems. In several cases the offending product has been on the machine since at least 5 (five!) years.


    I've also (tried) to read through your support case (the english parts :smileywink:) and can see that the cause is somewhat unexplained.

    Interestingly... just today I installed a new VMWare machine (using VMWare Fusion for Mac).  It offered to install a free copy of McAfee VirusScan.  The machine already had Sophos 9.5 on it but I thought, hey why not, I'd run the install and see what happens.  The result was McAfee did not notice another AV was already on the machine and happily installed.

    I mention this only to highlight that it is possible to install two anti-virus products side-by-side *if* the second one isn't on the look out for existing AV software.  Since Sophos AutoUpdate doesn't want to degrade the machine's performance by letting two anti-virus products run on the same computer we designed our installer to error out (stop, roll back, alert to the console so you are aware and can decide what to do and NOT just cripple the machine) rather than silently succeed...for now...but there will be trouble ahead.  Hence our product can look like the one behaving in an unexpected way.

    My thoughts on how the issue occurred:  (1) McAfee was installed after Sophos and the two have been running for a while before the 9.7 upgrade occurred or (2) The CRT did not run on these computers or (3) We added a new detection into the CRT to remove the currently installed version of McAfee or (4) The Sophos AutoUpdate check was manually bypassed (as can be done with a couple of registry keys).

    If you can find out when the McAfee product was installed (filter System event logs for MSI installer entries?) and see how long it's been on there that would help.

    :15823
Children
No Data