[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7446
  • Last Modified:

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.
1 Solution
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.
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 ElebuteCommented:
no files or folders found under c:\windows\system!!

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now