Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 6 subscribers
  • Views 2739 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

fail to update>fail to install

northof53

Sophos installed and run uneventfully

Fail to contact server during update

Reinstall attempt.

Remove initial with uninstaller

Download and re install

Tells me it is OK to run , followed by 'failure: contact manufacturer'

MD5 checksum "no such file or directory

Info on disc image savos_73_he.dmg is a download of 90.7Mb ;so it is there

thoughts/advice greatly appreciated. (including how to contact manufacturer as directed)

thanks

north of 53

:1004387


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

    I just experienced a similar issue on my own home computer... for me, the problem was resolved when I isolated another process that was using one of the OS's cryptography libraries, but was sitting waiting for a prompt.  As it was a faceless application, this wasn't very obvious.  Since it started up and restored prior to Sophos AutoUpdate kicking in during the boot process, a reboot didn't fix anything.  Once I had terminated the process using Activity Monitor, Sophos AutoUpdate immediately updated.

    So, it appears the updater relies on something that can be locked by another process.

    :1004535
Reply
  • 0

    I just experienced a similar issue on my own home computer... for me, the problem was resolved when I isolated another process that was using one of the OS's cryptography libraries, but was sitting waiting for a prompt.  As it was a faceless application, this wasn't very obvious.  Since it started up and restored prior to Sophos AutoUpdate kicking in during the boot process, a reboot didn't fix anything.  Once I had terminated the process using Activity Monitor, Sophos AutoUpdate immediately updated.

    So, it appears the updater relies on something that can be locked by another process.

    :1004535
Children
No Data