Exchange 2013 Upgrade – Service ‘WMSVC’ failed to reach status ‘Running’ on this server

During Readiness Checks for Microsoft Exchange Server 2013 Cumulative Update 9 (CU9) installator decided that it cannot start a service.

Full error message looks like below:

The following error was generated when “$error.Clear();

          $keyPath = “HKLM:\Software\Microsoft\WebManagement\Server”;

          if (!(Get-Item $keyPath -ErrorAction SilentlyContinue))

          {

            New-Item $keyPath -Force

          }

          Set-ItemProperty -path $keyPath -name “EnableRemoteManagement” -value 0x1 -Type DWORD -Force;

          if (Get-Service WMSVC* | ?{$_.Name -eq ‘WMSVC'})

          {

            Set-Service WMSVC -StartupType Automatic

            Stop-SetupService -ServiceName WMSVC;

            Start-SetupService -ServiceName WMSVC

          }

        ” was run: “Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service ‘WMSVC' 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.b__b()

   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)”.

After a quick look at services console (services.msc) Web Management Service  was indeed down.

Starting it up just brought another, a bit meaningless error

Checking Event Logs / Services shows Event ID 7024 from Service Control Manager with error message:

The Web Management Service service terminated with the following service-specific error: Unspecified error

So how to fix this error? It turns out the service requires an SSL Certificate to be available in IIS. Unfortunately one of the administrators setting up certificates wanted to have “clean” certificates Window, and since certificate in Exchange ECP looks unused there's nothing stopping you to delete it. Quick look at new installation of Exchange 2013 at certificates window shows WMSVC certificate.

And in comparison the supposedly cleaner version without the WMSVC certificate.

Even though the Assigned Services for this certificate are NONE Exchange Administrators should left this certificate as is. Fortunately if you've already deleted the certificate you can quickly fix it.