Hey Folks,
after updateing a customers’ Exchange 2010 SP3 Server to SP3 Rollup 1 we got massive Problems with the ExchangeTransport Service.
The serivce crashed repeatedly and generated several Event log entries with the following IDs:
4999,10001,10002,10003,12028
The Exchange poison quee was filled up with normal mail traffic.
After uninstalling SP3 Rollup 1 from the HT servers the problem disappeared.
Cheers,
Chris
UPDATE:
My colleague Michael Miklis pointed out to me, that this behaviour is referred in the SP§ RU1 release article:
Known Issue
After this update is applied, there is an issue in which messages stick in a poison queue and the transport service crashes.
This issue is caused by a transport rule (disclaimer) that tries to append the disclaimer to the end of HTML-Formatted messages. When this occurs, messages are put in the poison queue and the transport service crashes with an exception. We are investing resources to develop a code fix. To work around this issue, you can disable or reconfigure the disclaimer transport rule.
