Categories
How-To Software Technical

Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.

Aparently, this normally happens when you disable IPv6 in Local Area Connection.
This is due to the behavior of IPv6 in Windows Server 2008, when you disable IPv6 in Local Area Connection on Windows 2008 server.

The following error was generated when: “$error.Clear(); if ($RoleStartTransportService) { start-SetupService -ServiceName MSExchangeTransport }”, generated the following error: “Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.”


After doing lot of troubleshooting and searching on the net, found that this is happening due to IPV6, and installation needs IPv6 to be disabled in your local area connection on the system. After disabling my setup went smoothly, follow the below instructions to disable IPv6 from your system.
To completely disable IPv6 on a Windows Server 2008-based system, follow these steps:
1. Open Registry Editor.
2. Locate the following registry subkey:HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpip6Parameters
3. In the details pane, click New, and then click DWORD (32-bit) Value.
4. Type DisabledComponents, and then press ENTER.
5. Double-click DisabledComponents, and then type 0xffffffff in Hexadecimal or 4294967295 in Decimal.

4 replies on “Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.”

I am trying to installing exchange 2016 on server 2012. But when process 8 going on then transport give the error. Please find the error message .

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. —> System.InvalidOperationException: Cannot start service MSExchangeTransport on computer ‘.’. —> System.ComponentModel.Win32Exception: The service did not respond to the start or control request in a timely fashion
— End of inner exception stack trace —
at System.ServiceProcess.ServiceController.Start(String[] args)
at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartServiceWorker(ServiceController serviceController, String[] serviceParameters)
— End of inner exception stack trace —
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
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.b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)”.

Leave a Reply to Anonymous Cancel reply

Your email address will not be published. Required fields are marked *