Exchange 2013 Transport Service is not starting–1067 Error

Exchange 2013 Transport Service doesn’t want to start after server restart.

Windows could not start the Microsoft Exchange Transport service on Local Computer.

Error 1067 The process terminated unexpectedly.”

Tried putting the Transport Service logon to Local account . No Luck
Placed logon back to “Network Service” .No Luck
Tried Running Get-Receiveconnector
Saw two mysterious connectors in the End

Logged in to EAC – Exchange admin center.

Saw that Receive connectors have been created on HubTransport instead of FrontEndTransport

Solution –

Change the Transport role TYPE from HubTransport to FrontendTransport

Set-ReceiveConnector –Identity “EXCH\RELAY” –TransportRole FrontendTransport

Disabled them.

Now able to start Microsoft Exchange Transport Service.

Reference Events –

Log Name: Application
Source: MSExchange Common
Date: 1/24/2015 10:34:29 AM
Event ID: 4999
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: Exch.azure365pro.com
Description:
Watson report about to be sent for process id: 9280, with parameters: E12IIS, c-RTL-AMD64, 15.00.0847.032, MSExchangeTransport, M.Exchange.Net, M.E.P.WorkerProcessManager.HandleWorkerExited, M.E.ProcessManager.WorkerProcessRequestedAbnormalTerminationException, 5e2b, 15.00.0847.030.
ErrorReportingEnabled: False

Log Name: Application
Source: MSExchange TransportService
Date: 1/24/2015 10:34:29 AM
Event ID: 1046
Task Category: ProcessManager
Level: Warning
Keywords: Classic
User: N/A
Computer: Exch.azure365pro.com
Description:
Worker process with process ID 18316 requested the service to terminate with an unhandled exception.

Log Name: Application
Source: MSExchangeTransport
Date: 1/24/2015 10:34:29 AM
Event ID: 1036
Task Category: SmtpReceive
Level: Error
Keywords: Classic
User: N/A
Computer: Exch.azure365pro.com
Description:
Inbound direct trust authentication failed for certificate %1. The source IP address of the server that tried to authenticate to Microsoft Exchange is [%2]. Make sure EdgeSync is running properly.

24 COMMENTS

Alex Samol May 16, 2014 At 11:59 am

Thank you for this post as I was having the same issue. So are all received connectors to be created on the Frontend Transport role?

- Satheshwaran Manoharan June 3, 2014 At 6:50 am
  
  Yes
  
Daniel June 1, 2014 At 8:15 pm

THX for that!

chrisbee July 2, 2014 At 10:52 pm

Had similar problem “Windows could not start the Microsoft Exchange Transport service on Local Computer”
The Transport service would start when rebooting the server, but if you tried to restart it from the Services, it would not.
The issue turned out to be the DNS server address that was not accessible. We’d set one of the network card IP properties “Use the following DNS server addresses” to an external DNS server (8.8.8.8 = google.com) but then had disabled internet access on the server. When the DNS server could not be contacted, the transport service wouldn’t start. Removed the external DNS reference under the IP settings and transport service started.

- Satheshwaran Manoharan July 10, 2014 At 5:17 pm
  
  Thanks for sharing ????
  
Manuel September 14, 2014 At 12:38 pm

Thanks for sharing, I had a similar situation after install some windows updates and pump up the Memory Ram and all I have to was go to the mail flow, receive connectors and disable all HubTransport connector, wait for the service return and then enable those HubTransport connector back

- Satheshwaran Manoharan September 21, 2014 At 8:35 am
  
  Good 🙂
  
Alex October 27, 2014 At 5:02 am

Thanks this worked for me.

- Satheshwaran Manoharan January 7, 2015 At 4:36 am
  
  You are welcome !
  
Hamdy Marzouk November 23, 2014 At 10:59 am

Thank you so much ……………
will done………..

- Satheshwaran Manoharan January 7, 2015 At 4:42 am
  
  Thank you !
  
Jeremy February 20, 2015 At 1:24 pm

Satheshwaran,

You nailed it! Thank you!!! This Solution works!

- Satheshwaran Manoharan March 8, 2015 At 1:17 pm
  
  Thank you for your comments !
  
Rob March 2, 2015 At 7:28 pm

I made a new receive connector and went to restart services, got this error. NOW I cant connect via ECP, Powershell, nothing…

Nelson April 29, 2016 At 4:33 pm

Fit my issue perfectly. Easily followed via command line and the GUI. Well done!

- Satheshwaran Manoharan May 3, 2016 At 9:25 am
  
  Thank you 🙂
  
Dhimant May 24, 2016 At 9:10 am

Hey I am facing the issue which says “‘MSExchangeTransport’ failed to reach status ‘Running’ on this server
I tried the solution of disabling/enabling ipv6 through rgistry also..but still the issue is persisting. And ya this issue is being faced while installing exchange server 2013 on server 2012. Looking at your posts and expertise I think you could help me on this, I am stuck on this for the past 3-4 days. Please help. I could provide you with the screenshot if necessary.Also when i try to start the service from services.msc. It says error 1067: the process terminated unexpectedly. Please help

- Satheshwaran Manoharan July 12, 2016 At 6:36 am
  
  Verify proper connectivity with Active directory.
  
  - Maffix April 27, 2017 At 1:51 am
    
    Satheshwaran, how do I verify proper connectivity with AD?
    
    - Satheshwaran Manoharan May 11, 2017 At 4:29 pm
      
      Ping DNS . Check event viewer
      
mehdi hosseini December 23, 2016 At 1:24 pm

Thanks so much

- Satheshwaran Manoharan January 8, 2017 At 9:33 am
  
  your Welcome
  
Francisco Cuevas March 1, 2017 At 1:46 am

tengo un exchange 2013 y no levanta eMSExchangeTransport error 1053 the service did not respond to the start or control request in a timely y en el status marca como startin y no running

paramesh October 8, 2019 At 5:15 am

Hi,

We have exchange 2013 RTM ver with windows R2.

Every 15 days i got the below issue

Exchange 2013 frontend Transport Service doesn’t want to start.After rebooting the server the service hsa started.
Windows could not start the Microsoft Exchange Transport service on Local Computer.
Error 1067 The process terminated unexpectedly.”

Please any one give me the step by step detailed solution for this issue. Because of long pending for this issue.