Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 1 subscriber
  • Views 5193 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 SAVXP: The MSI has failed

Phil-UQ

Got this happening on a few machine, so unable to install Sophos on them.

We're tried everything on the knowledge base, but no fix yet. We're able to install other MSI files on the machine.

Anyone else been able to solve this ?

:3187


This thread was automatically locked due to age.
Parents
  • 0

    This still the problem you posted in February?

    Anyone else been able to solve this ?

    Depends on what you mean by this. If it's solve a The MSI has failed error then yes. If it's the specific problem you encounter then no one will be able to seriously answer your question without knowing any details. 

    I've always started by inspecting the logs to determine where it failed. Sometimes it's quite easy to determine the cause of the failure by just looking at the error message logged, sometimes I had to dig a little bit deeper (keep in mind that error codes are often generic). Several weeks ago I had a case where a client "suddenly" refused to update. Turned out that a "leftover" SAV installation could be found in Add or Remove Programs (whatever version and for whatever reason - didn't grill the user, also did not find out why didn't cause problems before). Funny thing was that Uninstall from there did work.

    Trial and error is the last resort (and I had to use it only on machines which had been deliberately "mishandled") - so far I've always succeeded.

    Christian

    :3194
Reply
  • 0

    This still the problem you posted in February?

    Anyone else been able to solve this ?

    Depends on what you mean by this. If it's solve a The MSI has failed error then yes. If it's the specific problem you encounter then no one will be able to seriously answer your question without knowing any details. 

    I've always started by inspecting the logs to determine where it failed. Sometimes it's quite easy to determine the cause of the failure by just looking at the error message logged, sometimes I had to dig a little bit deeper (keep in mind that error codes are often generic). Several weeks ago I had a case where a client "suddenly" refused to update. Turned out that a "leftover" SAV installation could be found in Add or Remove Programs (whatever version and for whatever reason - didn't grill the user, also did not find out why didn't cause problems before). Funny thing was that Uninstall from there did work.

    Trial and error is the last resort (and I had to use it only on machines which had been deliberately "mishandled") - so far I've always succeeded.

    Christian

    :3194
Children
No Data
Unfiltered HTML