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

PureMessage wont download spam updates & failed to create spam engine errors

Hi,

I have an issue with PureMessage that I am having no luck being able to resolve.  The Spam signatures themselves will not update, I get the following message in the update log:

Time: 16/06/2018 16:52:53
Message: ERROR:   Download of PMSR Data failed from server pmw-dynamic.sophos.com/.../
Module: ChannelUpdate
Process ID: 24952
Thread ID: 16904

Not only that but the Spam engine itself is failing, all messages are being tagged as "UNSCANNED" and delivered through to all my users.  When I watch the activity monitor every spam mail that comes through produces the following message:

"Failed to create the spam engine while processing message <message> (error 0x80004005)"

 

I have followed all the steps on the link below and still have the same errors

https://community.sophos.com/kb/en-us/29452

 

I opened a web browser on the Sophos/PureMessage server and can access the above http://pmw-dynamic.sophos.com/pmw/charlie/ ftp site fine,  so the internet access is definitely there I dont understand why the update wont pull this files down and install.

 

Product is Pure Message version 3.1.3.0 this also runs as part of Sophos Endpoint and Security Control Version 10.8.   All the sophos antivirus signatures download fine as part of the same update when the spam signatures are supposed to download as well but it is just the spam signatures that fail to download every time.

 

I have run out of things to try and my bosses and very unhappy with the level of spam currently hitting their mailboxes pretty much constantly, I need to try and resolve this as quickly as I can.  Can anyone help? 

Thanks,

Paul



This thread was automatically locked due to age.
  • Hello Paul,

    sorry, I've noticed this post just today.
    Is the issue still present or did you perhaps contact Support in the meantime? The more verbose ALUpdate log in %ProgramData%\Sophos\AutoUpdate\Logs\ should have the error details.

    Christian