Sophos Protection Updating Failed
- I been having some struggle trying to know why I can have the spam filter of sophos to update after I changed the credentials of the secondary server for updates on the SEC. Before of that all of the PC were unable to get the updates but changing the credentials all PC are up to date but the spam filter no, It used to be updated before that change.
- Past few days i've noticed that my sophos icon in tray on bottom right beside clock (system tray?) is showing a red dot with a cross in it. Hovering over the 'shield' icon shows the message 'Protected by Sophos Sophos protection update has failed' When I right-click and try and update, software runs (3 steps) and then updates (2 steps).
The ' computername Sophos' library update task has failed. INDEX 0x80040701 Could not access the EM library. Either there is no valid library or the path is not accessible. Check that there is a shared directory for the library (by default the directory is 'Program Files Sophos Enterprise Manager library' and is shared as 'SophosEM') and that.
Sophos Not Updating
There are the following types of alerts for issues that affect installation of Sophos agents,updating of Sophos agents, or policy compliance: HighFailed to protect computer or serverA computer has started installation of the agent software but has not become protected forone hour. The installer that has been run on the affected computer may provide moreinformation about the reason of the failure.
MediumComputer or server out of dateA computer that has not been updated in the last 24 hours has been communicating withSophos Central in the last 6 hours, and did not update inthe following 2 hours. Normally, a computer will attempt to update about 5 minutes after ithas been started, and then regularly every 60 minutes. If re-applying the policy failsrepeatedly, it may be due to a more serious problem.
Sophos Protection Updating Failed Error
In those cases, re-installation maysolve the problem.Reboot requiredThe reboot of a computer is needed to complete an update of the agent software, but thecomputer has not been restarted for 2 weeks. Sometimes, after installing/updating the agentsoftware, a restart is needed to fully enable the capabilities of the new/updated version ofthe software. Although an update does not need to be performed immediately, it is advisableto perform it as soon as possible.Policy non-complianceA device may not comply with a policy for various reasons, for example because the settingshave been changed on the device itself. In that case, after two hours of non-compliance, thesystem will raise an alert and will try to re-apply the corresponding policy. When thedevice is back in compliance, the alert will be automatically cleared. If re-applying failsrepeatedly, it may be due to a more serious problem. In those cases, re-installation maysolve the problem.Peripheral detectedA removable media or peripheral device has been detected on a device monitored by Sophos Central.Duplicate device detectionA duplicate device has been detected.
If devices have been cloned from an image they havethe same ID. Duplicate IDs can cause management issues. Duplicate devices are re-registeredwith a new ID.For more information, see.Notes:. Computers running Windows XP/Vista or Server 2003/2008 are not detected as duplicates.However, if they have the same ID as the one running a supported OS (e.g.
Windows 10),they are detected as duplicates but not re-registered. Any Windows servers with the server lockdown product installed and locked are notre-registered if they are detected as duplicates. We don't support duplicate device detection on VDI style environments such as VMwareHorizon or Citrix PVS or Citrix MCS.