Microsoft Exchange 2013 Mailbox Transport Delivery Service Won’t Start After A Reboot
I am coming across this issue again and again in the lab! Whenever the Exchange 2013 mailbox server is rebooted, the Microsoft Exchange Mailbox Transport Delivery service won’t start automatically. If I start the service manually, it works fine until the next reboot. IPv6 is enabled and the service is set to automatic. Anyone else…
I am coming across this issue again and again in the lab!
Whenever the Exchange 2013 mailbox server is rebooted, the Microsoft Exchange Mailbox Transport Delivery service won’t start automatically. If I start the service manually, it works fine until the next reboot.
IPv6 is enabled and the service is set to automatic. Anyone else seeing the same issue?
Give “Network Service” Full access to:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\WorkerTaskFramework\IdStore
Thanks, setting it to ‘automatic (delayed start)’ just takes one minute or so extra and now it works reliably.
Thanks Guido
I have the same issue but its nearly all the exchange services, it can be random sometimes they all start then other times only some start. The issue is related to hardware and VM performance. Up-ing the RAM, CPU, pagefile and setting the services to delayed start will help. Unfortunately if your vCPU on your hypervisor or VMware host is over utilised then the exchange vm may not be getting cpu cycles to complete the operation of starting the services another issue that could affect this is Disk IO performance. My set up is a lab environment so not critical, but best to place a exchange vm on a more powerful host
Rajith,
Any followup with the ServicesPipeTimeout setting? If so, what did you set it to and did it fix your problem. I’m having the same issue with EX2013 – so frustrating!!
The Exchange Active Directory Topology service can be slow to start (even slower in VM). The Exchange Transport service (as well as other Exchange services) are dependent on the Exchange Active Directory Topology service.
In the Services MMC “services.msc”, configure the Exchange Transport service to “Automatic (Delayed Start)” should correct the problem.
Thanks Tim.
I would like Exchange to behave properly, without deplayed start;)
May have to increase the ServicesPipeTimeout.
Raj il see if i can replicate in my lab. But as Horace responded he is very correct in that Exchange 2013 is certainly resource hungry. I noticed a big difference in performance once i started fine tuning and up’ing the spec of the VM.
Thanks Shawn. Let me know how it goes.
i had similar issues(not with this specific product) and it was just happening inside vm’s(maybe lack of enough power or something and only with 2008+ os with more then one net card)
i “solved” it by changing to delayed start…
Thanks TurboMCP
Hi Rajith,
Can you try giving the VM running Exchange 2013 more memory and increasing the page file size?
Some say that the memory requirements for Exchange 2013 have been understated.
I was thinking of doing that Horace. Will let you know.