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

SEC. Clear error messages 00000071

slamjl

I'm sure there must be a simple answer to this but I can't find it!

After a recent server reboot some PCs are showing error messages, with 00000071 "Could not find a source for updated packages".  The error has since been resolved, as they update after the server reboot had completed.  However they still show an error in SEC and I can't clear the message with "resolve alerts and errors".  What am I missing, please?

Thanks

:50514


This thread was automatically locked due to age.
  • 0

    Hello slamjl,

    these messages can't be acknowledged but should eventually get cleared when the endpoints report a successful update. Please check the endpoints' Last message time whether it's recent. The 00000071 will be shown in View computer details under History - Sophos AutoUpdate status, a subsequent report of a successful update causes a line with <date/time> 00000000 Updated successfully to be written. You might be able to expedite this by right-clicking and requesting Update Computers Now.

    Christian

    :50516
  • 0

    Hello.

    Thank you for the reply.

    Yes, if I go into the computer details from SEC it shows a subsequent update, shortly after completion of the server reboot.  However the issue remains that SEC still reports that the computer (ostensibly) has an error!

    Regards.

    :50520
  • 0

    Hello slamjl,

    messages shouldn't get lost - neither on their way to SEC nor internally. Apparently the successful update has been transmitted by and recorded for the endpoint but somehow the error condition hasn't been cleared. It seems that it affected endpoints which failed to update while the server/share was unavailable but succeeded shortly after reboot. This could be a minor error in the console logic - are the clients otherwise listed as being up to date?

    Did you try Update Computers Now?

    Christian

    :50524
  • 0

    Hello.

    Thank you.  No, I hadn't run try Update Computers Now.  Having done that it's cleared the list of those that hadn't had the error message cleared.

    I said there was probably a simple answer!  I had looked on the user forum, tried various options but hadn’’’’t considered that I had to update manually, expecting instead that the normal updating routine was effective – which it is.  It just doesn’’’’t clear the error messages!

    Thank you again.  We’’’’re only small users.  I normally check SEC regularly and this problem had niggled for a while.  Now I know what to do in future.  Pity it doesn’’’’t clear the message with the normal updates, though…

    :50526
  • 0

    Hello slamjl,

    Pity it doesn’’’’t clear the message with the normal updates, though…

    it's definitely not necessary to manually request an update for the error to get cleared. Thinking about it, I assume it requires an actual update though, i.e. that not only the check for update is considered successful just because the local catalog matches the one from the CID and there is nothing to be downloaded, but that there's at least one file to download and all files are downloaded successfully. This could explain the behaviour you've observed. An Update now request causes the client to respond not only with a failure/success message but its update status details - and it seems these are needed for the error to be cleared.

    Christian     

    :50534
  • 0

    Hello.

    Thank you.

    I wonder if the manual update just coincided with an actual update?  However having said that I imagine there must have been updates over the last 48 hours (the error messages were showing at the weekend).

    Anyway, now I know that I can run an update and it will clear the error messages that gives me peace of mind.

    :50538