Error 'could not be synchronised because the synchronise operation failed due to an earlier error'

  • Article ID: 119592
  • Updated: 09 Jul 2013


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.

What To Do

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.

If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent