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

Comparison Failure / Failed to install SAVXP

Initially the error on client's pc  was 'Could not obtain an impersonation token for a resource shielding' and comparison failure, so I reinstalled Sophos.

But now error is 'Failed to install SAVXP: The MSI has failed' and comparison failure. The install log has registered below two errors:

1. 

MSI (s) (38:08) [10:04:31:964]: Machine policy value 'DisableRollback' is 0
Action ended 10:04:31: InstallFinalize. Return value 3.

2.

MSI (s) (38:08) [10:05:05:480]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Action ended 10:05:05: INSTALL. Return value 3.

I can't find solutions for these in knowledgebase. 

Thanks. 



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

    the cause for impersonation token related errors (please see the linked article)  is usually a resource shortage on the endpoint - thus a reinstall won't help.

    Anyway, the install error is another issue. I can't find solutions for these as Return value 3 is just a generic failure indicator, the second one even only a summary. The 'DisableRollback' message preceding the first occurrence is already a response to the (actual) error which is a few lines above (often a four-digit error code and an error message). (actual) parenthesised because it could have been a CustomAction (they have their own log) which failed. The relevant part of the log(s) should be in one of these places.

    Christian

Reply
  • Hello Akash Sangani,

    the cause for impersonation token related errors (please see the linked article)  is usually a resource shortage on the endpoint - thus a reinstall won't help.

    Anyway, the install error is another issue. I can't find solutions for these as Return value 3 is just a generic failure indicator, the second one even only a summary. The 'DisableRollback' message preceding the first occurrence is already a response to the (actual) error which is a few lines above (often a four-digit error code and an error message). (actual) parenthesised because it could have been a CustomAction (they have their own log) which failed. The relevant part of the log(s) should be in one of these places.

    Christian

Children
No Data