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

Runtime error pushing Sophos to workstation from Enterprise Console

Hi, I have a problem installing Sophos to Workstation that I cannot understand.

I'm using Enterprise Console 5.1 and want to use "Protect Computers" to install the Workstation.

When I run that I get the error in Enterprise Console: 00000062 Runtime Error

On the Workstation I see the logs avremove.log without error and Sophos ES Setup with the error:

ERROR,An unexpected error occurred, no translation available: Unexpected product state 2 for product with code  {15C418EB-7675-42be-B2B3-281952DA014D},

Anybody familiar with this message?

:26703


This thread was automatically locked due to age.
Parents
  • Exactly the same problem here, (after the recent False Positive fun).  However this fix didn't work for me until I also

    a) performed a local pull of Sophos AutoUpdate only

    b) uninstalled that using local Add/Remove Programs

    c) pushed all again from the Enterprise Console.

    Until I performed step a) the Console push was still failing with same error, however searching the registry didn't find the referenced key anymore.

    After step a) only, the MSI log looked fine, but the Console reported the workstation was still unmanaged and was waiting for it to report back, which it never did as updating had already failed.

    This may help somebody.  BTW the only reason this workstation became problematic at all stemmed from someone (else) deleting the contents of Quarantine after Shh/Updater-B... our policy was Deny Access only but deleting the AutoUpdate DLLs didn't help.

    :33821
Reply
  • Exactly the same problem here, (after the recent False Positive fun).  However this fix didn't work for me until I also

    a) performed a local pull of Sophos AutoUpdate only

    b) uninstalled that using local Add/Remove Programs

    c) pushed all again from the Enterprise Console.

    Until I performed step a) the Console push was still failing with same error, however searching the registry didn't find the referenced key anymore.

    After step a) only, the MSI log looked fine, but the Console reported the workstation was still unmanaged and was waiting for it to report back, which it never did as updating had already failed.

    This may help somebody.  BTW the only reason this workstation became problematic at all stemmed from someone (else) deleting the contents of Quarantine after Shh/Updater-B... our policy was Deny Access only but deleting the AutoUpdate DLLs didn't help.

    :33821
Children
No Data