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

auto update from 7.6 to 9.5 clients failing

Hello All,

I've been migrating our old 7.6 client to 9.5x and some have been failing as the process has been unable to uninstall one of install components. Usually this is the AV but sometimes its autoupdate or worse the RMS which can't be uninstalled. In this situation i use the 7.6uninstall tool which cleans most of it out but if the RMS fails this tool won't clear it. Usually it requires a  hack of the registry to remove. Once all removed the update works as you'd expect.

Here is part of the AV uninstall log which shows that there is a problem with the original source of the install and it is missing something. Luckly of the 4,200 Pc's I'm only talking about 4 or 5% which have this issue.

MSI (s) (78:F0) [12:24:19:501]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (78:F0) [12:24:19:501]: Warning: Local cached package 'C:\WINDOWS\Installer\19358.msi' is missing.
MSI (s) (78:F0) [12:24:19:501]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (78:F0) [12:24:19:501]: User policy value 'DisableMedia' is 0
MSI (s) (78:F0) [12:24:19:501]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (78:F0) [12:24:19:501]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (78:F0) [12:24:19:501]: SOURCEMGMT: Looking for sourcelist for product {034759DA-E21A-4795-BFB3-C66D17FAD183}
MSI (s) (78:F0) [12:24:19:501]: SOURCEMGMT: Adding {034759DA-E21A-4795-BFB3-C66D17FAD183}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (78:F0) [12:24:19:501]: SOURCEMGMT: Now checking product {034759DA-E21A-4795-BFB3-C66D17FAD183}
MSI (s) (78:F0) [12:24:19:501]: SOURCEMGMT: Media is enabled for product.
MSI (s) (78:F0) [12:24:19:501]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (78:F0) [12:24:19:501]: SOURCEMGMT: Trying source C:\Program Files\Sophos\AutoUpdate\cache\savxp\.
MSI (s) (78:F0) [12:24:19:517]: SOURCEMGMT: Source is invalid due to invalid package code (product code doesn't match).
MSI (s) (78:F0) [12:24:19:517]: Note: 1: 1706 2: -2147483646 3: sophos anti-virus.msi
MSI (s) (78:F0) [12:24:19:517]: SOURCEMGMT: Processing net source list.
MSI (s) (78:F0) [12:24:19:517]: Note: 1: 1706 2: -2147483647 3: sophos anti-virus.msi
MSI (s) (78:F0) [12:24:19:517]: SOURCEMGMT: Processing media source list.
MSI (s) (78:F0) [12:24:19:517]: Note: 1: 2203 2:  3: -2147287037
MSI (s) (78:F0) [12:24:19:517]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (78:F0) [12:24:19:517]: Note: 1: 1706 2: -2147483647 3: sophos anti-virus.msi
MSI (s) (78:F0) [12:24:19:517]: SOURCEMGMT: Processing URL source list.
MSI (s) (78:F0) [12:24:19:517]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (78:F0) [12:24:19:517]: Note: 1: 1706 2: -2147483647 3: sophos anti-virus.msi
MSI (s) (78:F0) [12:24:19:517]: Note: 1: 1706 2:  3: sophos anti-virus.msi
MSI (s) (78:F0) [12:24:19:517]: SOURCEMGMT: Failed to resolve source
MSI (s) (78:F0) [12:24:19:517]: MainEngineThread is returning 1612
MSI (c) (E0:F0) [12:24:19:517]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (E0:F0) [12:24:19:517]: MainEngineThread is returning 1612
=== Verbose logging stopped: 23/02/2011  12:24:19 ===

My question is why this might have occoured in the first place, all machines with the problem talk to SEC without issue, just wonder if what I'm doing is the quickest and most efficent way to fix these troublesome clients?

Regards.

:9497


This thread was automatically locked due to age.
Parents
  • Hello,

    That looks very odd, I assume that the file under: "\windows\installer\19358.msi" (in this case) is actually not there rather than maybe permissions and the error doesn't distinguish between the two?

    If it isn't there I guess someone or some application deleted it, maybe they or it thought they were tidying up and save space?

    So once it fails with the file in "\windows\installer\", it seems to go through the list of potential install sources "LastUsedSource", etc..  You can find these under:

    HKEY_CLASSES_ROOT\Installer\Products for the various applications.

    I wonder if, given the correct MSI in the list of sources it tries it would just work?

    I see it complains with:

    "Source is invalid due to invalid package code (product code doesn't match)"

    when it tries the cache directory of SAV.  I assume the cache of SAU now has the updated msi of 9 and that's why?  It would makes sense.

    So how about finding the right version of the msi for version 7and then running the following VBScript on a test client to add another source location:

    Dim wiInstaller : Set wiInstaller = CreateObject("WindowsInstaller.Installer")
    wiInstaller.AddSource "{9ACB414D-9347-40B6-A453-5EFB2DB59DFA}", "", "\\server\share\rightmsi.msi"

     You would need to update the GUID to that of SAV 7 and then add a path to the correct MSI.  You can find the GUID looking through:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

    searching for "savxp".

    I've not tested any of this so I'm not even sure it would work but maybe it's something to try on one machine.

    I hope it offers something,

    Regards,

    Jak

    :9507
Reply
  • Hello,

    That looks very odd, I assume that the file under: "\windows\installer\19358.msi" (in this case) is actually not there rather than maybe permissions and the error doesn't distinguish between the two?

    If it isn't there I guess someone or some application deleted it, maybe they or it thought they were tidying up and save space?

    So once it fails with the file in "\windows\installer\", it seems to go through the list of potential install sources "LastUsedSource", etc..  You can find these under:

    HKEY_CLASSES_ROOT\Installer\Products for the various applications.

    I wonder if, given the correct MSI in the list of sources it tries it would just work?

    I see it complains with:

    "Source is invalid due to invalid package code (product code doesn't match)"

    when it tries the cache directory of SAV.  I assume the cache of SAU now has the updated msi of 9 and that's why?  It would makes sense.

    So how about finding the right version of the msi for version 7and then running the following VBScript on a test client to add another source location:

    Dim wiInstaller : Set wiInstaller = CreateObject("WindowsInstaller.Installer")
    wiInstaller.AddSource "{9ACB414D-9347-40B6-A453-5EFB2DB59DFA}", "", "\\server\share\rightmsi.msi"

     You would need to update the GUID to that of SAV 7 and then add a path to the correct MSI.  You can find the GUID looking through:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

    searching for "savxp".

    I've not tested any of this so I'm not even sure it would work but maybe it's something to try on one machine.

    I hope it offers something,

    Regards,

    Jak

    :9507
Children
No Data