Question : Why won't Exchange Transport service start in Exchange 2007 on our SBS 2008 server ?

Our server was working fine until this afternoon and the Exchange Transport service stopped working.  On examining the Event logs I see in the Application logs the following errors:

MSExchange Common           Id 4999

Watson report about to be sent to dw20.exe for process id: 3316, with parameters: E12, c-RTL-AMD64, 08.01.0240.006, edgetransport, XmonAgent, X.XmonSmtpAgentFactory.ThreadLoadSettings, System.MissingMethodException, 35c8, 04.02.10015.000.  ErrorReportingEnabled: False

MSExchange Common           Id 4999


Watson report about to be sent to dw20.exe for process id: 8544, with parameters: E12, c-RTL-AMD64, 08.01.0240.006, edgetransport, XmonAgent, X.XmonSmtpAgentFactory.ThreadLoadSettings, System.MissingMethodException, 35c8, 04.02.10015.000.  ErrorReportingEnabled: False

MSExchange Common           Id 4999


Watson report about to be sent to dw20.exe for process id: 8596, with parameters: E12, c-RTL-AMD64, 08.01.0240.006, edgetransport, XmonAgent, X.XmonSmtpAgentFactory.ThreadLoadSettings, System.MissingMethodException, 35c8, 04.02.10015.000.  ErrorReportingEnabled: False

Followed by..

MSExchange Transport Service          Event Id 1016

The worker process crashes continuously on startup: C:\Program Files\Microsoft\Exchange Server\Bin\edgetransport.exe. The service will be stopped.

The chain of errors happen every time I try to start up the service.  All the other services are working fine but it is just this one.

I had suspected there was a problen with the hub transport service so tried to reinstall it but that didn't work

Can anyone offer any advice how we can fix this ?

Many thanks in advance

Answer : Why won't Exchange Transport service start in Exchange 2007 on our SBS 2008 server ?

Yes that's correct.  It had left the trasnport agents behind which were making the Transport service stop after approx 30 secs.  We  also didn't stop the Exchange or NOD32 services prior to install.

The server was put in production on the day of the issue which made it even worse.

After the ESET Mail Security was removed and the trasnport agents removed, the Transport Service worked without any issue