Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 0 subscribers
  • Views 54725 views
  • Users 0 members are here
Options
Suggested
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

BloodBaz

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.
  • 0

    It's possible that the agents may need to be reordered based on what you're experiencing, though it would be worthwhile to find out when this problem started and if there were any other events that may have triggered this behaviour.

    The solution may depend on the version of PureMessage and Exchange you're running, so if you haven't already contacted Sophos Support, I would recommend doing so in case your configuration needs to be closely inspected.

    :23765
  • 0

    I also have this problem after upgrading to 3.1.2 - As soon as I Disable-TransportAgent PmE12Transport and restart the Transport Service the queue diminishes very quickly. As soon as I Enable-TransportAgent and restart the Transport Service it is not long and the queue starts to fill up.

    Mmmmm, the transport service, so:

    I have noticed that if I DO NOT restart the MicrosoftExchangeTransport service as recommended there is no problems, PureMesage runs perfectly and no submission queues form...??

    Fun hey! :)

    Sadly, not much information in either Event logs (System, Application) to troubleshoot.

    :28809
  • 0

    There's nothing better than a thread that goes dead with no real solution! :-)

    I too am having this problem. 

    I am running:

    Exchange Server 2007 (v08.01.0436.000) on Windows Server 2008 Std SP2.

    with

    PureMessage for Exchange v3.1.2

    As previous posts, if I disable PureMessage services, the submission queue goes down and messages go through. 

    If I disable the Transport Agent but DON'T RESTART the MSTransport service, then messages are filtered and continue to go through - only until services are refreshed though. Then it backs up again. And this wouldn't be an ideal solution anyway.

    Currently, I'm uninstalling PureMessage to attempt a fresh install, but the last twice I did that - it never worked.

    No help anywhere about this on PureMessage website. Can't tell me it's a one off?

    :35047
  • 0

    That doesn't exactly help others who come across this thread who may have the same issue.

    For those in the same position, I had tried Uninstalling and Re-installing PureMessage on two occasions, to no avail. However...

    I've since removed Sophos from the system entierly. Uninstalling all Sophos and PureMessage products and cleaning the Program Files folder for anything left over. I then restart, installed Sophos and then installed PureMessage (the latest version from the website). 

    I had to setup PureMessage again, which was a pain! - BUT, it seems to be working efficiently again.

    :35127
  • 0

    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
  • 0

    I have exact the same problem as FogLifter55 describes. I have SBS2011 server with PM v 311 and just recently we got this problem mainly in the morning when people start to work. They can't send emails, outlook gives temporary freeze when sending or replying messages.
    After that I have upgraded Exchange to SP3 with Rollup 1 and PM to latest version 313 but the problem persists.
    The only crazy thing is that it solves itself after an our or so. But the issue repeats itself every morning.

    :41437
  • 0

    Is this issue resolved?

    How?

    :45045
  • 0

    Hi all,

    This problem is not yet solved. (MX2010, SP3-RU4 and PM-3.1.3)

    We have a ticket to open since July 2013, unfortunately no solution by Sophos......

    Six months have passed and now we are looking for an alternative solution.

    :46293
  • 0

    Hi StefanS,

    I understand I have located your case and the latest status appears to be an email we sent to you on 20th November without reply.

    Did you receive the 20th November mail? (If not we can resend it of course). If you received it, did you meet any issues following the steps provided? If you met issues then please reply in the case, we can then update this posting later with results.

    Regards,

    Reginald

    :46379
Unfiltered HTML