OverviewWith the introduction of Exchange Server 2013, several features have been upgraded like web-based Exchange Administrative Center (EAC), offline support in Outlook Web Access etc. the blog will be discussing error encountered in Exchange Server 2013 error called Error 1067 and ways to recover from the same error.
Error 1067The Error 1067 is usually found after upgrading the Exchange Server 2013 to Exchange 2013 Service Pack 1. It happens when the Microsoft Exchange Frontend Transport service fails to start in Exchange Server 2013 showing Error 1067: The process terminated unexpectedly.
Possible Cause of Error 1067The Error 1067 in which the Exchange Transport service cannot start in Exchange server 2013 has been identified as a Microsoft Issue introduced in Exchange Server 2013 Service Pack 1. This error may happen when the third party transport agents cannot be loaded or installed correctly while the user upgrades from Exchange Server 2013 to Exchange server 2013 SP1. In addition, the Microsoft Exchange Transport service cannot start automatically and user cannot enable third-party products that rely on transport agents.
How to Resolve Error 1067The error can be resolved by following the steps given:
- Go to Command Prompt and type ‘Get-RecieveConnector’
- Check if there are any unknown or doubtful connectors present
- If there are any unknown connectors, we will login to Exchange Admin Center (EAC)
- After logging to EAC, Click on Mail Flow and go to Receive connectors
- All the connectors will be displayed in the list.
- The unknown connectors have been created on HubTransport instead of FrontEndtransport
- We will change the transport role TYPE from HubTransport to FrontendTransport by Set-RecieveConnector –Identify “EXCH\RELAY” –TransportRole FrontendTransport
- Another option is to disable them.
- Restart the Microsoft Exchange Transport Service.