Share via

Exchange 2016 - 'MSExchangeTransport' failed to reach status 'Running' on this server.

Question

Friday, January 6, 2017 5:19 AM

Hello everyone,

I would like some help installing Microsoft Exchange 2016 on Windows Server 2016.

I am working on a fresh installation of Windows Server 2016 and a fresh install of Exchange 2016. There is no previous version of any Exchange version.

After perform all the pre requirements according to MS documentations and the deployment assistant I am running the setup and the installation is taking much time when copying files at 20%, after this it takes about 20 minutes in the Step 5: Languages and finally takes more trying to install The Transport Service at 98% when it fails with the following error:

Error:
The following error was generated when "$error.Clear(); 
          if ($RoleStartTransportService)
          {
              start-SetupService -ServiceName MSExchangeTransport -MaxWaitTimeForRunningState 0:0:40
          }
        " was run: "Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service 'MSExchangeTransport' failed to reach status 'Running' on this server.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.WaitForServiceStatus(ServiceController serviceController, ServiceControllerStatus status, Unlimited`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService)
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   at Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__c()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

I was able to check the following errors in the Event Viewer:

Log Name:      MSExchange Management
Source:        MSExchange CmdletLogs
Date:          2017-01-05 9:43:20 PM
Event ID:      6
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server.XXXXX.ca
Description:
Cmdlet failed. Cmdlet Install-BridgeheadRole, parameters -DomainController "Server.XXXXXXX.ca" -UpdatesDir $null -LanguagePacksPath "D:\" -StartTransportService "True" -DisableAMFiltering "False".

Log Name:      MSExchange Management
Source:        MSExchange CmdletLogs
Date:          2017-01-05 9:43:20 PM
Event ID:      6
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server.XXXXXXX.ca
Description:
Cmdlet failed. Cmdlet start-SetupService, parameters -ServiceName "MSExchangeTransport" -MaxWaitTimeForRunningState "00:00:40".

Log Name:      MSExchange Management
Source:        MSExchange CmdletLogs
Date:          2017-01-05 12:55:55 PM
Event ID:      6
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server.XXXXXX.ca
Description:
Cmdlet failed. Cmdlet Set-ReceiveConnector, parameters -Identity "Server.XXXXXX.ca\MSExchangeTransport" -TransportRole "FrontendTransport".

Steps tried to solve the issue with not luck:

1) I have tried to Disable IPv6 in the network Adapter + disable in the registry at HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > Tcpip6 > Parameters creating a 32 BIT DWORD value called "DisabledComponents", and set its value to 0xffffffff (Hexadecimal) or 4294967295 (Decimal).

2) Check that the Microsoft Exchange Transport service is installed and using with the Network System account but with the Status "Starting" for ever.

When trying to Start the service I am receiving the error: 

Services

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

Error 1067: The process terminated unexpectedly.

OK   

2) Check that the Administrator Group is member of Exchange Trusted Subsystem group.

Does anyone have a suggestion on how ti fix this?

Thanks you for your help!!!

All replies (4)

Friday, January 6, 2017 7:49 AM âś…Answered | 1 vote

Finally I was able to identify and solve the issue!!!

After so many research I went back to this documentation https://support.microsoft.com/en-ca/kb/2958036

 that says: 

"Cause
This issue occurs if there is a receive connector of Transport type HubTransport that has the binding set to port 25 on the affected Exchange server. Only the FrontendTransport server-type receive connector should have the binding set to port 25."

So, I went to Windows Firewall and I have found that the MDaemon (that is installed and running on this server) was using the Port 25. So I stopped the MDaemon and seconds later the Exchange Transport service was able to start. Running the Exchange setup again the Installation worked without any other the issue.

I am installing Exchange on this server exactly because we are about to migrate from MDaemon to Exchange.

Bottom line: Also check in the firewall or search for any other program that may be using the Port 25!!!! Stop the application and change the port if possible.

Thank you for your help and hope my feedback can help other people as well.

Friday, January 6, 2017 5:35 AM | 1 vote

Here are some points you need to check:

  1. Check Manage auditing and security log Properties

Administative Tools > Local Security Policy > Local Policies > User Rights Assignment > Manage auditing and security

  1. Make your account as local administrator group and perform the installation again
  2. Make sure have enough prerequisites
  3. Check Exchange Trusted Subsystem
  • Open Active Directory Users and Computers
  • Under domain name (For example contoso.com),navigate to the Builtin Container, on the right hand side select the Administrator group,goto the properties
  • Click members tab and add Exchange Trusted Subsystem
  • Click ok twice
  • Reboot the Exchange server
  • Rerun the Exchange setup
  1. Check IPv6 enable ?

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents

and restarting the server and try again.

Check this link to get in detailed. Also check this earlier thread i.e. MSExchangeTransport failed to reach status 'Running' on this server

You may also get help from below links:

Installing Exchange Server 2016 on Windows Server 2016: http://exchangeserverpro.com/installing-exchange-server-2016-on-windows-server-2016/

Guide to Install Exchange Server 2016
Hope this helps!

Migrate mailboxes, Public Folders, Outlook profiles and rules and GAL etc. to-and-fro Exchange Servers and Office 365 with LepideMigrator for Exchange

Friday, January 6, 2017 5:57 AM

Hi Nickclark985,

Thank you for your quick reply.

So, I have already did some steps and this is the situation:

Step 1 - Verified and it's Ok
Step 2 - Verified and it's Ok
Step 3 - Verified and it's Ok (according MS documentation and Deployment guide
Step 4 - Exchange Trusted Subsystem is already there. OK
Step 5 - I have created the a 32 BIT DWORD value called "DisabledComponents", and set its value to4294967295 (Decimal).

Additionaly, Ipv6 is disabled in the NIC properties and I have removed the :::1 from the hosts file

After all this, still presenting the same behaviors: Taking much time when copying files at 20%, after this it takes about 20 minutes in the Step 5: Languages and finally takes more trying to install The Transport Service at 98% when it fails with the error: "Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service 'MSExchangeTransport' failed to reach status 'Running' on this server.

Any other sugfestion?

Thanks again

Friday, January 6, 2017 7:13 AM | 1 vote

Please check the member listed in exchange servers and also listed in exchange domain servers.

Generally this issue occurs due to two different causes:

  • All IPv6 adapters were disabled. Enabling IPV6 on a NIC fixed it

  • The server wasn't in the Exchange Domain Servers group

Make sure both of these are good.

Also refer to this thread:
https://social.technet.microsoft.com/Forums/en-US/b15e5ff7-9185-432f-8ef1-f09385c7c572/mailboxrole-partially-installed-error-service-msexchangetransportlogsearch-failed-to-reach-status?forum=exchangesvrdeploylegacy

Hope this helps!

Migrate mailboxes, Public Folders, Outlook profiles and rules and GAL etc. to-and-fro Exchange Servers and Office 365 with LepideMigrator for Exchange

  • Last updated on