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

0000006b - Sophos AutoUpdate failed from server \\server\\SophosUpdate\...

heath

Server is running SEC 5.2.2, clients are running 10.3 Endpoint Security and Control 10.3, and the error I'm getting is:

"Sophos AutoUpdate failed from server \\server\\SophosUpdate\CIDs\S000\SAVSCFXP\" (Code 0000006b)

My issue started when I noticed that the Update Manager itself hadn't updated for almost three weeks. I fixed this by finding an error using the LogViewer, Decode operation failed when decoding product release 'Windows Endpoint Security and Control' someone suggested backing up the CIDs and Warehouse folders and restarting the Sophos Update Manager service rectified this issue, and it did. However, clients were still not updating, even after a couple of days.

I then thought it might be the SophosUpdateMgr user not working so I followed a guide on resetting it properly using the ObfuscationUtil. This didn't appear to work, at least for UNC updating. I was quickly able to get clients updating using the secondary update server, using the username and password supplied by Sophos, but I'm still left with a list -- 600-long -- of computers displaying an error warning because they can't update from the SophosUpdate UNC share. I've checked permissions, even going a bit lax on the share's security, and it's still not playing ball.

Any help will be much appreciated!!

:55497


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

    Bookmarked the msdn link for future reference - thanks :smileytongue:

    I created a new Updating Policy, ensuring that my SophosUpdateMgr password was entered without error, and had all of my groups comply with it. Voila! Clients are now updating from the share :smileyvery-happy:

    I'm not sure how necessary creating an entirely new policy was, though, but I just wanted to rule out the Default policy as the culprit. For sure I could have tested this beforehand by re-entering the password in the Default policy, but it took just a couple of minutes to get a new policy set up.

    Thank you so much, Christian!

    :55518
Reply
  • 0

    Bookmarked the msdn link for future reference - thanks :smileytongue:

    I created a new Updating Policy, ensuring that my SophosUpdateMgr password was entered without error, and had all of my groups comply with it. Voila! Clients are now updating from the share :smileyvery-happy:

    I'm not sure how necessary creating an entirely new policy was, though, but I just wanted to rule out the Default policy as the culprit. For sure I could have tested this beforehand by re-entering the password in the Default policy, but it took just a couple of minutes to get a new policy set up.

    Thank you so much, Christian!

    :55518
Children
No Data