Exchange 2010 MSExchangeTransport (edgetransport process) keeps crashing and replaying logfiles
On an Exchange 2010 server with the Cas / Hub transport role installed the edgetransport process keeps crashing and replaying log files and again crashing with the following evened error:
Event ID 4999:
Watson report about to be sent for process id: 1240, with parameters: E12, c-RTL-AMD64, 14.01.0270.001, edgetransport, mscorlib, S.I.__Error.WinIOError, System.TypeInitializationException, c11a, 02.00.50727.4959.
ErrorReportingEnabled: False
After these messages it comes with the follwing messages:
edgetransport (1240) Transport Mail Database: The database engine (14.01.0270.0001) is starting a new instance (0). edgetransport (1240) Transport Mail Database: The database engine is initiating recovery steps. A configuration update for Microsoft.Exchange.Transport.TransportServerConfiguration has successfully completed. A configuration update for Microsoft.Exchange.Transport.RemoteDomainTable has successfully completed. A configuration update for Microsoft.Exchange.Transport.X400AuthoritativeDomainTable has successfully completed. A configuration update for Microsoft.Exchange.Transport.AcceptedDomainTable has successfully completed. A configuration update for Microsoft.Exchange.Transport.ReceiveConnectorConfiguration has successfully completed. A configuration update for Microsoft.Exchange.Transport.TransportSettingsConfiguration has successfully completed. edgetransport (1240) Transport Mail Database: The database engine has begun replaying logfile C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue\trn.log. edgetransport (1240) Transport Mail Database: The database engine has successfully completed recovery steps. edgetransport (1240) Transport Mail Database: The database engine started a new instance (0). (Time=2 seconds) edgetransport (1240) Transport Mail Database: The database engine attached a database (0, C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue\mail.que). (Time=0 seconds) edgetransport (1240) IP Filtering Database: The database engine (14.01.0270.0001) is starting a new instance (1). edgetransport (1240) IP Filtering Database: The database engine is initiating recovery steps. edgetransport (1240) IP Filtering Database: The database engine has begun replaying logfile C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\IpFilter\trn.log. edgetransport (1240) IP Filtering Database: The database engine has successfully completed recovery steps. edgetransport (1240) IP Filtering Database: The database engine started a new instance (1). (Time=1 seconds) edgetransport (1240) IP Filtering Database: The database engine attached a database (2, C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\IpFilter\IpFiltering.edb). (Time=0 seconds)
And after that the edgetransport crashes again and the loop continues every 30 to 60 seconds.
Upgrading Exchange 2010 to SP1 and later rollup 2 didn’t resolve anything.
Solution: After having had contact with Microsoft support on this issue, the problem was caused by a third party exchange virusscanner. But you can perform the following steps to throubleshoot if you have a similar issue:
Open Exchange Management Shell,
Do a Get-TransportAgent it gives a list of all transport agents, you will see which additional programs have plugged into the sequense.
Do a Get-TransportAgent | Disable-TransportAgent , now all transport agents are disabled
Restart the Microsoft Exchange Transport service.
View the eventlog to see if the error returns , in my case the transport services was stable now (wait some time to be sure it won’t return it could take about 5 till 10 minutes till it cames back).
Allright after you have seen everything is stable now we can enable the transport agents one by one to see when it will crash again.
Use Enable-TransportAgent -Identity “transportagent name” (you can copy the exact name from the Get-TransportAgent list you did before) note some programs have more than one transport agent enable those together. After enabling a transport agent you have to restart the Microsoft Exchange Transport service again and see if the process keeps to be stable (Keep in mind to give it some time).
If you have found the problematic transport agent you can use Disable-TransportAgent -identity “transportagentname” to disable on this transport agent again.
In my case I have removed the problematic software and downloaded the latest version of the product and installed it the problem haven’t come back.
