Quantcast
Channel: Small Business Server forum
Viewing all articles
Browse latest Browse all 8539

Transport Service keeps freezing, possible PoisonMessage issue?

$
0
0

Hello, all.  I could really use some help with this.  Our client is running SBS 2011 and the Exchange Transport service keeps crapping out.  It continues to run but all email flow stops, both internal and external (inbound and outbound). 

When the Transport failure happens, restarting the Exchange Transport service will start the messages flowing again.  The problem here is that the service cannot be stopped from the Services applet.  It will hang on stopping.  Instead, I have to use the Task Manager to stop the MSExchangeTransport.exe service.  Once I do that, the service will restart by itself (i.e.: I do not initiate this) within 30 seconds.
 
We have AVG Email Server Edition 2012 on this server.  I've disabled the services and it does not seem to make a difference.
 
An error I keep seeing in the Application Event Log is as follows:

********************
Log Name:      Application
Source:        MSExchangeTransport
Date:          12/5/2012 9:07:56 AM
Event ID:      10001
Task Category: PoisonMessage
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      TTESBS.tte.local
Description:
 3 messages have reached or exceeded the configured poison threshold of 2. After the Microsoft Exchange Transport service restarted, these messages were moved to the poison message queue.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeTransport" />
    <EventID Qualifiers="32772">10001</EventID>
    <Level>3</Level>
    <Task>10</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-12-05T15:07:56.000000000Z" />
    <EventRecordID>70559</EventRecordID>
    <Channel>Application</Channel>
    <Computer>TTESBS.tte.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>3</Data>
    <Data>2</Data>
  </EventData>
</Event>
********************

I have already looked at MS KBA 2616444, searched the registry, and found no trace of the referenced [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework]\"OnlyUseLatestCLR"=dword:00000001.  I even did a full search of the registry for OnlyUseLatestCLR and found nothing.  Also, running "Get-Message -Queue "Poison"" at the Exchange Management Shell returns no results -- it just goes right back to the PS command prompt.
 
I have looked through http://technet.microsoft.com/en-us/library/ff359794(v=exchg.140).aspx and it recommends that I "report the potentially harmful message that Exchange detected", but I'm unable to find a place from which to submit the message without opening a support case.
 
The server is mostly updated.  It's missing a security update for Visual C++ and a couple of optional Kernal-Mode Driver updates (this is checking for updates online).  On that note, the beginning of the problems do not seem to neatly coincide with any updates.

Running the Microsoft Exchange Troubleshooting Assistant to test outbound mail flow times out ("Mail submission failed:  Error Message:  The operation has timed out..").
 
The Queue Viewer simply spins away but never seems to load anything -- no queues, no messages.
 
I'm at a loss.  Any help would be appreciated.

Jaymen


Viewing all articles
Browse latest Browse all 8539

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>