The Sophos Community will be offline for scheduled maintenance this Saturday, May 27th, at 13:00 UTC for approximately 1 hour. Apologies for any inconvenience caused.
"Wanna" ransomware outbreak. Please see this Sophos article sophos.com/kb/126733 for advice on how to protect your organization. Immediate action recommended.
The Sophos Update Manager (SUM) trace logs shows an error similar to the following.
2010-02-10 17:10:08 : Cmd-ALL << [E403C][7D48A012-0C64-4F21-BA27-A9CEDF442749][Not attempted.][0.0.0][SOPHOS] Supplements for payload '7D48A012-0C64-4F21-BA27-A9CEDF442749' could not be synchronised because the synchronise operation failed due to an earlier error.
First seen in Sophos Update Manager
A synchronization error indicates that an action or event cannot be completed or run because the data it requires is not present or valid.
To resolve these issues you need to find the core issue which requires finding the first error in the sequence and identifying the cause of that - the error shown above is too late in the chain of events to know what caused it.
Therefore work back through the SUM trace logs and locate the first error. If you need to contact us please run the Sophos Diagnostic Utility of the SUM server first, attach the output file and quote this article.
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. If you need technical support please post a question to our community. Alternatively for licensed products open a support ticket.