Transport service hangs at "starting" and does not start after a reboot of the Exchange server.

After a weekly reboot of my Exchange Server, the Transport service hangs at "starting" and I'm getting the below error in the event log.

Source: MSExchangeTransport.
ID: 14001
The process is not responding, and will be forced to shut down.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It  could be because of a build up of log files in the Queue directory caused by back pressure problems. When the Transport service starts it starts to replay all the log files but because there could be so many it couldn't finish within 5 minutes which is when the service times out and this error appears. You may need to create a new queue to allow the service to start and then recover the emails in the old queue.
tomlsiAuthor Commented:

Would you please provide me instructions on how to create a new queue?
tomlsiAuthor Commented:
I found the solution to my problem after one week of working with Microsoft Support. The Edgetransport service hangs trying to read a 1MB host file located in c:\windows\system\drivers\etc named hosts.ntlm. After removing the file from that directory, the transport service starts successfully.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Tomlsi, that corrected my problem with Transport not starting on my Exchange 2010 server.

The hosts file on my server was located in c:\windows\system32\drivers\etc

As soon as I removed this file, the service started right up!    Thank you for sharing this!
David ElebuteSystems ConsultantCommented:
no files or folders found under c:\windows\system!!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.