Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 1611 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

Sophos Update Manager No Longer Working After Update to Version 1.2.1.161

Gutenberg

A few weeks ago there was an automatic upgrade to our Update Manager running under Enterprise Console 4.7.0.13. Since then the Update Manager no longer works.

I can see that the manager is running but it takes up +95% of the CPU. I've stopped and started the service several times to no effect. It has to be stopped manually or it will bog down the server. I even let it run for 24 hours or so to see what would happen before stopping the service. It just kept running.

The only error message that appears in the event log is: Source: SQL Browser The configuration of the AdminConnection\TCP protocol in the SQL instance SOPHOS is not valid." There are no errors or codes show in the Update Manager Detail.

I'm getting nowhere with Sophos support. I've been going back and for with them for over 2 weeks and opened two support tickets on this, one asking for help getting the Update Manager working and the other asking if I can manually push AV updates to the clients.

I should also mention that this server is a VM configured with two drives one with 1.04 GB free and the other with 1.29 GB free. Should I try freeing up some space for the updates? Unfortunately I wasn't the person who configured and deployed this system or Sophos.

Any suggestions or advice would be welcomed.

:18725


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

    Hi Jak,

    Thanks for the advice.

    The SophosUpdateMgr.exe process was the one consuming CPU. When I checked the RMS Agent logs I didn't see any of the SDDMA messages you referenced.

    I finally managed to set up a remote session with a Sophos support tech who ended up reinstalling the update manager.

    He wasn't able to determine an exact cause of the problem, but the reinstall fixed it.

    It could have been an unsuccessful update or some kind of file corruptiion issue.

    All is well once again.

    :18977
Reply
  • 0

    Hi Jak,

    Thanks for the advice.

    The SophosUpdateMgr.exe process was the one consuming CPU. When I checked the RMS Agent logs I didn't see any of the SDDMA messages you referenced.

    I finally managed to set up a remote session with a Sophos support tech who ended up reinstalling the update manager.

    He wasn't able to determine an exact cause of the problem, but the reinstall fixed it.

    It could have been an unsuccessful update or some kind of file corruptiion issue.

    All is well once again.

    :18977
Children
No Data