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 "Failed to create the virus engine while processing message"

I have Exchange 2013 at sites A, B and C. The PureMessage DB is in site A. Everything works in site A, but sites B and C only generate errors and deliver e-mail with the "UNSCANNED" header.

 

The log file is an endless list of the same three errors (EventID 68, 70 and 72):

05.12.2019 14:38:38 Failed to create the virus engine while processing message '<669a88a0-7f76-49b4-aa73-68248c8677f6@northwind.com>' (error: '0x800706BE')
05.12.2019 14:38:38 Failed to create the content engine while processing message '<669a88a0-7f76-49b4-aa73-68248c8677f6@northwind.com>' (error: '0x800706BA')
05.12.2019 14:38:38 Failed to create the spam engine while processing message '<669a88a0-7f76-49b4-aa73-68248c8677f6@northwind.com>' (error: '0x800706BA')
05.12.2019 14:38:50 Failed to create the virus engine while processing message '<5374f3fc35ce457ea93813d877fbc0ca@acme.org>' (error: '0x800706BE')
05.12.2019 14:38:50 Failed to create the content engine while processing message '<5374f3fc35ce457ea93813d877fbc0ca@acme.org>' (error: '0x800706BA')
05.12.2019 14:38:50 Failed to create the spam engine while processing message '<5374f3fc35ce457ea93813d877fbc0ca@acme.org>' (error: '0x800706BA')

 

Unfortunately, there's few to find about this subject ( or about PureMessage, for that matter). This post about Scheduled Tasks not functioning (they do) is the only one actually. More generally, 0x800706BA means the remote procedure server cannot be reached and 0x800706BE means the remote procedure call failed. 

 

Any ideas? I'm thinking of a Windows Firewall issue maybe and am experimenting with that.



This thread was automatically locked due to age.
Parents Reply Children
  • Hello Shweta,

    No, but I am not entirely sure why not. When Sophos looked at the install with me, the problem was gone. Less than 10% of email traffic was not scanned, but that is apparently acceptable. before it was nearly 100% unscanned. The fact that on the main mail server, where most traffic is but also the DB, unscannable objects is nearly 0, makes me think in reality the issue is performance related. I suspect that this error happens if Server B and Server C query the DB in Server A and the reply doesn't come fast enough. I'll see how it goes in January. Right now, because of the holidays, there's few traffic and much bandwidth. 

  • Hi  

    Sure, if you need any help from our side, please let us know. We'll help you to resolve your issue.

    Regards,

    Jasmin
    Community Support Engineer | Sophos Support

    Sophos Support VideosKnowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question use the 'This helped me' link