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

Transport Agent PmE12transport causing Messages to back up in Submission Queue

Yesterday we found that Microsoft Exchange stopped routing any messages (incoming, outgoing, internal, external).

Upon investigation, Exchange's Queue Viewer shows that the Submission Queue had 100s of emails sitting in it and the number continued to rise as more incoming email continued to come in.

Google search suggested that the submission queue backing up is usually the result of AV/AntiSpam components.  So I started to consider PureMessage as the source of the problem.

I ran the Get-TransportAgent commandlet in the Exchange Shell which showed:

Identity                                           Enabled         Priority
--------                                           -------         --------
PmE12Transport                                     True            1
Transport Rule Agent                               True            2
Journaling Agent                                   True            3
AD RMS Prelicensing Agent                          False           4
PmE12Protocol                                      True            5

I then ran disable-transportagent PmE12Transport commandlet and restarted Exchange Transport Service and all the backed up messages pushed through and the queue dropped down to 0.  This suggests that PmE12Transport Transport Agent was causing the block.


Re-enabling the transport agent (followed by a Exchange Transport Service restart ) causes messages to back up again after about a minute.

Opening up PureMessage doesn't show up anything out of the ordinary.

I need advise as to how I can interrogate the PmE12Transport Transport Agent (sophos logs, Events etc.) to find out what it's beef is.  Any useful information will be appreciated.

Thanks,


Chris

:23711


This thread was automatically locked due to age.
Parents
  • Using version 3.1.0.0 and Exchange 2010.

    I saw the same thing in the evening, our queue was really high, I didn't do anything and the transport service finally caught up.

    I saw the event log:

    The execution time of agent ‘‘‘‘PmE12Protocol’’’’ exceeded 90000 milliseconds while handling event ‘‘‘‘OnConnectEvent’’’’ 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.

    And this was correct as the transport agent did continue processing. Has sophos fixed this at all? I see there is version 3.1.3 out now, but I don't see this fix in the release notes, I also am getting a number of warning event logs "Reporting data could not be written to the database at this time(error: 0x80040E14). Additional attempts will be made for 3 days." has this been fixed?

    :40631
Reply
  • Using version 3.1.0.0 and Exchange 2010.

    I saw the same thing in the evening, our queue was really high, I didn't do anything and the transport service finally caught up.

    I saw the event log:

    The execution time of agent ‘‘‘‘PmE12Protocol’’’’ exceeded 90000 milliseconds while handling event ‘‘‘‘OnConnectEvent’’’’ 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.

    And this was correct as the transport agent did continue processing. Has sophos fixed this at all? I see there is version 3.1.3 out now, but I don't see this fix in the release notes, I also am getting a number of warning event logs "Reporting data could not be written to the database at this time(error: 0x80040E14). Additional attempts will be made for 3 days." has this been fixed?

    :40631
Children
No Data