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

Could Not Contact Server Problem

andrewj

Hi,

I hope someone can help here. I am having a problem with updates, and I am running out of ideas.

I have had to revert one of my machines to a backup about a month old. Everything else seems to be fine, but I cannot get Sophos updating to work.

I have several machines on the same network, all of which update directly from Sophos using the same credentials. The other machines are updating fine, so it's not a problem with my network or credentials. I have also confirmed that I can ping from the affected machine to addresses like dci.sophosupd.com without problems. 

I did a re-install of Endpoint 10.0.3 which worked without problems (although I had to reboot and retry to get firewall to update cleanly). This hasn't solved the problem. I have also run an up to date Windows Defender scan to see if there's any obvious malware problem but it's clean.

I have attached the log of the latest attempt, to see if anyone can help.

Thanks

Andrew

:57254


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

    Hello Andrew and rsenio,

    @rsenio: <links to articles> [...] Whats the environment? [...] re-install via the Enterprise Console

    in principle good advice, but Andrew did attach (and likely check) the ALUpdate log. In addition not only does the log suggest that it's a stand-alone install - no mention of RMSNT - but Sophos as Primary or only update location is not possible for a managed install.

    I would delete ...

    Yep, looks like a file (HIPSConfig-1-0-65-1.dat in the savxp cache) has corrupted permissions as access is denied and this causes the sync to fail. I've not much no experience with the (rather new) SUL/SDDS update mechanism thus I can't say what exactly  Distribute status failed: 4 signifies. But anyway IMO the error (boost::filesystem::remove: Access is denied:) in the scheduled update cycle points at the "problem area".

    Christian

    :57280
Reply
  • 0

    Hello Andrew and rsenio,

    @rsenio: <links to articles> [...] Whats the environment? [...] re-install via the Enterprise Console

    in principle good advice, but Andrew did attach (and likely check) the ALUpdate log. In addition not only does the log suggest that it's a stand-alone install - no mention of RMSNT - but Sophos as Primary or only update location is not possible for a managed install.

    I would delete ...

    Yep, looks like a file (HIPSConfig-1-0-65-1.dat in the savxp cache) has corrupted permissions as access is denied and this causes the sync to fail. I've not much no experience with the (rather new) SUL/SDDS update mechanism thus I can't say what exactly  Distribute status failed: 4 signifies. But anyway IMO the error (boost::filesystem::remove: Access is denied:) in the scheduled update cycle points at the "problem area".

    Christian

    :57280
Children
No Data
Unfiltered HTML