Microsoft Exchange is one of the most popular mail servers with organizations of all sizes, as it helps simplify various administrative tasks; such as mailbox archiving and generating delivery reports. When an error occurs in the Exchange Server it is in the best interests of the organization to resolve the issue as quickly as possible in order to minimize potential downtime.

In this blog, we will discuss how to resolve one particular Exchange 2013 error message that you may come across – 1067.

Error 1067 usually occurs when you upgrade Exchange Server 2013 to Exchange Server 2013 Service Pack 1. When migrating to Exchange 2013 SP1, you will see error 1067 if third-party transport agents are not loaded and installed correctly. As a result, the Microsoft Exchange Transport Service may refuse to start automatically, and will display the following error:

Error 1067: The process terminated unexpectedly

How to resolve error 1067

Use the following method to resolve error 1067:

  1. Open command prompt and type ‘Get-RecieveConnector’.
  2. Look for any unidentified or unsure connectors in the displayed configuration information.
  3. If any unknown connector is there, logon to Exchange Admin Center (EAC).
  4. In EAC, go to Mail Flow and click on Receive connectors. This will show the list of all the connectors.
  5. In the list you will see that, Instead of Frontend Transport, the unidentified connectors are created on Hub Transport.
  6. To change the transport role type from Hub Transport to Frontend Transport, run the following command:
    Set-RecieveConnector –Identify “EXCH\RELAY” –TransportRole FrontendTransport
  7. If you don’t want to change the transport role type, then you can also disable the unknown connectors.
  8. Restart the Microsoft Exchange Transport Service.