Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 16 replies
  • Subscribers 1 subscriber
  • Views 49777 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

An update manager has not updated since 30th May

Gardinia

When looking at the Sophos Enterpise Console it states "an update manager has not updated since 30th May 2014", it also shows the majority of the computers are "out of date" when it comes to protection.

The endpoint computers themselves appear to be able to contact the server and get updates, however the server its self doesn’’’’t look to be updating at all.

I have looked in the Windows event viewer on the server, which is flooded with errors stating: The Sophos Agent service terminated unexpectedly.  It has done this 3849 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.

This is appearing in the Windows Event Viewer on the server every minute, when i try and start the service manually it just fails.

I have attached some screenshots, can anyone advise?

Thank you.

:50658


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

    Hello Gardinia,

    as for msxml4.dll - it's likely not on your system, instead try with msxml6.dll. Dunno if this will resolve the error though.

    Knowing what happened on May 30th might help. The RMS component hasn't been changed with the update from 10.3.1 to 10.3.7 so I'd rule it out (unless it happened on this date). Please check the latest (most recent) Agent log in C:\ProgramData\Sophos\Remote Management System\3\Agent\Logs. - what is the last timestamp in it, perhaps post the last few lines.

    Otherwise I can only suggest to give reprotection another one or two tries as it should do no harm. BTW - is the Endpoint component on the server up-to-date (10.3.7, 430 IDEs)?

    Christian

    :50748
Reply
  • 0

    Hello Gardinia,

    as for msxml4.dll - it's likely not on your system, instead try with msxml6.dll. Dunno if this will resolve the error though.

    Knowing what happened on May 30th might help. The RMS component hasn't been changed with the update from 10.3.1 to 10.3.7 so I'd rule it out (unless it happened on this date). Please check the latest (most recent) Agent log in C:\ProgramData\Sophos\Remote Management System\3\Agent\Logs. - what is the last timestamp in it, perhaps post the last few lines.

    Otherwise I can only suggest to give reprotection another one or two tries as it should do no harm. BTW - is the Endpoint component on the server up-to-date (10.3.7, 430 IDEs)?

    Christian

    :50748
Children
No Data