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 Ex 2010 SP2 - Warnings/Errors Event ID 55, 64

Hello,

We have an issue related to repeated warnings we see in the Event Log in regards to PureMessage and we would like to know what are the implications and resolutions to this.

The environement we talk about is a Win Server 2008 R2 with Exchange 2010 SP2 (mailbox, client access and transport roles) and PureMessage 3.1.0. We are seeing repeated warnings in Application Event Log with the Event ID 55 as following:

 - Reporting data could not be written to the database at this time (error: 0x80040E14). Additional attempts will be made for 3 days.

 - Reporting data could not be written to the database at this time (error: -3). Additional attempts will be made for 3 days.

Also, besides of these warnings, we had an issue with Error Event ID 64 "Unexpected error while processing message '<internal_message_refferal>' (error: '0x800706BA')" and right after Warning ID 1050 with the message "The execution time of agent 'PmE12Transport' exceeded 90000 milliseconds while handling event 'OnSubmittedMessage' for message with InternetMessageId: 'Not Available'. This is an unusual amount of time for an agent to process a single event. However, Transport will continue processing this message." At that time, our outgoing e-mails gathered in the submission queue without leaving and the quickest solution to this was to restart the exchange server after all came back to normal.

As a short notice, we had SP2 applied to our Exchange server 2 or 3 weeks ago and until this moment we didn't had any issues before with Exchange or PureMessage. So one of my questions is if the PureMessage has any incompatibilities with Microsoft Exchange SP2 and if so, what would be the solution to this.

Thanks in advance for any answer that might clear the situation.

:22689


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

    Currently, PureMessage for Exchange 3.1.0 isn't supported on Exchange 2010 SP2, so the behaviour you're reporting could be tied to an untested platform version. Had you seen this error happen prior to upgrading Exchange?

    The good news is that an upgraded version of PureMessage is due shortly that will support that version. For now, if you haven't already contacted Sophos Support, you should to see if there are any other options available to you specific to your environment.

    :23035
Reply
  • Hello,

    Currently, PureMessage for Exchange 3.1.0 isn't supported on Exchange 2010 SP2, so the behaviour you're reporting could be tied to an untested platform version. Had you seen this error happen prior to upgrading Exchange?

    The good news is that an upgraded version of PureMessage is due shortly that will support that version. For now, if you haven't already contacted Sophos Support, you should to see if there are any other options available to you specific to your environment.

    :23035
Children
No Data