Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 3572 views
  • Users 0 members are here
Options
Suggested
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 to install the SAVXP. MSI has failed

JayJ
At 1653 on 28 Nov, all my client machines reported this error: "Failed to install SAVXP. MSI has failed". They had been updating fine prior to installing the software a week ago. Whats strange, is that the 3 servers on the network have updated fine. I checked group policy settings for Windows Installer and they have not been altered to disallow Installer from working. I experimented on one machine performing MSIExec /unregister, then /regserver and then forcing update, all from client, and this worked fine. I do not, however, think this fix is acceptable on a LAN with over 100 end clients. Does any one know or has come across this and know of any fixes? Logs that have been generated look something like this: SAV MIL: 2012-11-29 13:44:17 Info: Logging started: installing/upgrading Sophos Anti-Virus 2012-11-29 13:44:17 Info: InstallFromPath is: C:\Program Files\Sophos\AutoUpdate\cache\savxp\ 2012-11-29 13:44:17 Info: InstallToPath is: 2012-11-29 13:44:17 Info: Detected version of SAV has major version number: 10 2012-11-29 13:44:17 Info: Detected version of SAV has minor version number: 0 2012-11-29 13:44:17 Info: registryInstallTo [overriding InstallToPath] is: C:\Program Files\Sophos\Sophos Anti-Virus\ 2012-11-29 13:44:17 Info: SetupPlugin: updateProps.m_MajorUpdate = 1 2012-11-29 13:44:17 Info: SetupPlugin: updateProps.m_DataOnlyUpdate = 0 2012-11-29 13:44:17 Info: SetupPlugin: updateProps.m_OnAccessDriverUpdate = 0 2012-11-29 13:44:17 Info: SetupPlugin: updateProps.m_BootDriverUpdate = 0 2012-11-29 13:44:17 Info: SetupPlugin: updateProps.m_ClassFilterUpdate = 0 2012-11-29 13:44:17 Info: SetupPlugin: updateProps.m_KMSDriverUpdate = 0 2012-11-29 13:44:17 Info: Managed install 2012-11-29 13:44:17 Info: Performing major update of Sophos Anti-Virus using msi. 2012-11-29 13:44:17 Info: Update is signalled. 2012-11-29 13:44:17 Info: PutSetupOptionsToRegistry 2012-11-29 13:44:17 Info: Install MSXML 2012-11-29 13:44:17 Info: Check boot driver and kms driver 2012-11-29 13:44:17 Info: upgrading an existing installation of SAV 2012-11-29 13:44:17 Info: Transform file returned: 2012-11-29 13:44:17 Info: SAV Setup plugin: running MsiInstallProduct (C:\Program Files\Sophos\AutoUpdate\cache\savxp\Sophos Anti-Virus.msi, REINSTALLMODE=vmuso REINSTALL=ALL REBOOT=ReallySuppress UPDATEDRIVERS=0 UPDATEBOOTDRIVERS=0 UPDATEKMSDRIVERS=0 UPDATECLASSFILTER=0 SAVIONLY=0 MANAGED=1 DATACONTROL=1 DEVICECONTROL=1 WEBCONTROL=1) === Verbose logging started: 29/11/2012 13:44:17 Build type: SHIP UNICODE 3.01.4001.5512 Calling process: C:\Program Files\Sophos\AutoUpdate\cache\sophos_autoupdate1.dir\alupdate.exe === MSI (c) (A8:50) [13:44:17:412]: Resetting cached policy values MSI (c) (A8:50) [13:44:17:412]: Machine policy value 'Debug' is 0 MSI (c) (A8:50) [13:44:17:412]: ******* RunEngine: ******* Product: C:\Program Files\Sophos\AutoUpdate\cache\savxp\Sophos Anti-Virus.msi ******* Action: ******* CommandLine: ********** MSI (c) (A8:50) [13:44:17:412]: Client-side and UI is none or basic: Running entire install on the server. MSI (c) (A8:50) [13:44:17:412]: Grabbed execution mutex. MSI (c) (A8:50) [13:44:17:443]: Failed to connect to server. Error: 0x80070005 MSI (c) (A8:50) [13:44:17:443]: Failed to connect to server. MSI (c) (A8:50) [13:44:17:443]: MainEngineThread is returning 1601 === Verbose logging stopped: 29/11/2012 13:44:17 === 2012-11-29 13:44:17 ERROR: Installation failed SAV IL: 2012-11-28 10:44:36 Info: Logging started: installing/upgrading Sophos Anti-Virus 2012-11-28 10:44:36 Info: InstallFromPath is: C:\Program Files\Sophos\AutoUpdate\cache\savxp\ 2012-11-28 10:44:36 Info: InstallToPath is: 2012-11-28 10:44:36 Info: Detected version of SAV has major version number: 10 2012-11-28 10:44:36 Info: Detected version of SAV has minor version number: 0 2012-11-28 10:44:36 Info: registryInstallTo [overriding InstallToPath] is: C:\Program Files\Sophos\Sophos Anti-Virus\ 2012-11-28 10:44:36 Info: SetupPlugin: updateProps.m_MajorUpdate = 0 2012-11-28 10:44:36 Info: SetupPlugin: updateProps.m_DataOnlyUpdate = 1 2012-11-28 10:44:36 Info: SetupPlugin: updateProps.m_OnAccessDriverUpdate = 0 2012-11-28 10:44:36 Info: SetupPlugin: updateProps.m_BootDriverUpdate = 0 2012-11-28 10:44:36 Info: SetupPlugin: updateProps.m_ClassFilterUpdate = 0 2012-11-28 10:44:36 Info: SetupPlugin: updateProps.m_KMSDriverUpdate = 0 2012-11-28 10:44:36 Info: Managed install 2012-11-28 10:44:36 Info: Logging started: performing minor update to Sophos Anti-Virus. 2012-11-28 10:44:36 Info: Beginning Shared Custom Actions. Logging will appear in Custom Action log. 2012-11-28 10:44:36 Info: Running Set Update Begin shared custom action. 2012-11-28 10:44:36 Info: Return Value from SetUpdateBegin: 0 2012-11-28 10:44:36 Info: Running DeleteRuleFiles(IDEs) shared custom action. 2012-11-28 10:44:36 Info: Return Value from DeleteRuleFiles(IDEs): 0 2012-11-28 10:44:36 Info: Running DeleteRuleFiles(HIPSConfig) shared custom action. 2012-11-28 10:44:36 Info: Return Value from DeleteRuleFiles(HIPSConfig): 0 2012-11-28 10:44:36 Info: Running DeleteRuleFiles(bdls) shared custom action. 2012-11-28 10:44:36 Info: Return Value from DeleteRuleFiles(bdls): 0 2012-11-28 10:44:36 Info: Running CopyHotUpdateFiles shared custom action. 2012-11-28 10:44:36 Info: Return Value from CopyHotUpdateFiles: 0 2012-11-28 10:44:36 Info: Running UpdateSAVI shared custom action. 2012-11-28 10:44:38 Info: Return Value from UpdateSAVI: 0 2012-11-28 10:44:38 Info: Running SetSavAdminUpdateComplete shared custom action. 2012-11-28 10:44:38 Info: Return Value from SetSavAdminUpdateComplete: 0 2012-11-28 10:44:38 Info: Running ConfigureSAV shared custom action. 2012-11-28 10:44:38 Info: Return Value from ConfigureSAV: 0 2012-11-28 10:44:38 Info: Running CopySAVSyncFile shared custom action. 2012-11-28 10:44:38 Info: Return Value from CopySAVSyncFile: 0 2012-11-28 10:44:38 Info: Running SetUpdateFinished shared custom action. 2012-11-28 10:44:38 Info: Return Value from SetUpdateFinished: 0 2012-11-28 10:44:38 Info: Running RunAfterScripts shared custom action. 2012-11-28 10:44:38 Info: Return Value from RunAfterScripts: 0 2012-11-28 10:44:38 Info: Shared custom actions succeeded. 2012-11-28 10:44:38 Info: Update to Sophos Anti-Virus succeeded. SAV CAL: 2012-11-28 10:44:36 Info: Logging started: installing/upgrading Sophos Anti-Virus 2012-11-28 10:44:36 Info: InstallFromPath is: C:\Program Files\Sophos\AutoUpdate\cache\savxp\ 2012-11-28 10:44:36 Info: InstallToPath is: 2012-11-28 10:44:36 Info: Detected version of SAV has major version number: 10 2012-11-28 10:44:36 Info: Detected version of SAV has minor version number: 0 2012-11-28 10:44:36 Info: registryInstallTo [overriding InstallToPath] is: C:\Program Files\Sophos\Sophos Anti-Virus\ 2012-11-28 10:44:36 Info: SetupPlugin: updateProps.m_MajorUpdate = 0 2012-11-28 10:44:36 Info: SetupPlugin: updateProps.m_DataOnlyUpdate = 1 2012-11-28 10:44:36 Info: SetupPlugin: updateProps.m_OnAccessDriverUpdate = 0 2012-11-28 10:44:36 Info: SetupPlugin: updateProps.m_BootDriverUpdate = 0 2012-11-28 10:44:36 Info: SetupPlugin: updateProps.m_ClassFilterUpdate = 0 2012-11-28 10:44:36 Info: SetupPlugin: updateProps.m_KMSDriverUpdate = 0 2012-11-28 10:44:36 Info: Managed install 2012-11-28 10:44:36 Info: Logging started: performing minor update to Sophos Anti-Virus. 2012-11-28 10:44:36 Info: Beginning Shared Custom Actions. Logging will appear in Custom Action log. 2012-11-28 10:44:36 Info: Running Set Update Begin shared custom action. 2012-11-28 10:44:36 Info: Return Value from SetUpdateBegin: 0 2012-11-28 10:44:36 Info: Running DeleteRuleFiles(IDEs) shared custom action. 2012-11-28 10:44:36 Info: Return Value from DeleteRuleFiles(IDEs): 0 2012-11-28 10:44:36 Info: Running DeleteRuleFiles(HIPSConfig) shared custom action. 2012-11-28 10:44:36 Info: Return Value from DeleteRuleFiles(HIPSConfig): 0 2012-11-28 10:44:36 Info: Running DeleteRuleFiles(bdls) shared custom action. 2012-11-28 10:44:36 Info: Return Value from DeleteRuleFiles(bdls): 0 2012-11-28 10:44:36 Info: Running CopyHotUpdateFiles shared custom action. 2012-11-28 10:44:36 Info: Return Value from CopyHotUpdateFiles: 0 2012-11-28 10:44:36 Info: Running UpdateSAVI shared custom action. 2012-11-28 10:44:38 Info: Return Value from UpdateSAVI: 0 2012-11-28 10:44:38 Info: Running SetSavAdminUpdateComplete shared custom action. 2012-11-28 10:44:38 Info: Return Value from SetSavAdminUpdateComplete: 0 2012-11-28 10:44:38 Info: Running ConfigureSAV shared custom action. 2012-11-28 10:44:38 Info: Return Value from ConfigureSAV: 0 2012-11-28 10:44:38 Info: Running CopySAVSyncFile shared custom action. 2012-11-28 10:44:38 Info: Return Value from CopySAVSyncFile: 0 2012-11-28 10:44:38 Info: Running SetUpdateFinished shared custom action. 2012-11-28 10:44:38 Info: Return Value from SetUpdateFinished: 0 2012-11-28 10:44:38 Info: Running RunAfterScripts shared custom action. 2012-11-28 10:44:38 Info: Return Value from RunAfterScripts: 0 2012-11-28 10:44:38 Info: Shared custom actions succeeded. 2012-11-28 10:44:38 Info: Update to Sophos Anti-Virus succeeded. I dont really know what i'm looking for, so be gentle, my background in IT is limited to date but growing fast due to me being in the deep end. Server is running 2003, client machines XP, all with up to date upates and latest service packs. Please help!!!
:35915


This thread was automatically locked due to age.
  • 0

    Hello JayJ,

    your post isn't very clearly arranged, in the future please make sure the line ends are present :smileyhappy:

    Anyway, this is usually some permissions/configuration error. That it works after unregister/register seems to confirm it and if reregistering works this is normally the recommended action. Do other installs also fail?

    I'd try to find out what (could have) happened between the last successful run (logs are in \Windows\Temp) and 1653. Apart from this there should be one or two events in the Event Viewer (ID 1015 is common) corresponding to the failed install (and perhaps check the events "down to" the successful run).

    SESC is at 10.0, right?

    Christian

    :35939