# Microsoft Exchange 2013 CU11 Readiness Checks Error

During a Readiness Checks of Exchange Server 2013 CU 11 installation, just about 90% into Configuring Prerequisites an error is displayed. One of the…

blog

14 Jan 2016 fr

![Microsoft Exchange 2013 CU11 Readiness Checks Error](/wp-content/uploads/2016/01/MicrosoftExchange.png)

[Voir les images (6)](#pf-content-image-1-0)

During a **Readiness Checks **of Exchange Server 2013 CU 11 installation, just about 90% into **Configuring Prerequisites **an error is displayed. One of the crucial services for Microsoft Exchange **WMSVC** cannot be started. “Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service ‘WMSVC' failed to reach status ‘Running' on this server.

Nothing comes easy when it comes to Exchange…

### ❗ Problem Description

Microsoft Exchange Server 2013 Cumulative Update GUI reports an error just before finalization of the checking process.

[!\[Microsoft Exchange 2013 CU11 Readiness Checks Error 1\](/wp-content/uploads/2016/01/img_569803283c077a.png)](/wp-content/uploads/2016/01/img_569803283c077a.png)

Error:

> The following error was generated when “$error.Clear(); $keyPath = “HKLM:SoftwareMicrosoftWebManagementServer”; 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)”.

Additionally an error in **Application Event Log **from IIS-ISSManager is visible.

[!\[Microsoft Exchange 2013 CU11 Readiness Checks Error\](/wp-content/uploads/2016/01/img_569806325380b.png)](/wp-content/uploads/2016/01/img_569806325380b.png)

Error in event log: EVENT ID: 1007, SOURCE: IIS-ISSManager, Level: Error

> IISWMSVC_STARTUP_UNABLE_TO_READ_CERTIFICATE Unable to read the certificate with thumbprint ‘0efba9399f2d1bc978b9761a19002806cc823778'. Please make sure the SSL certificate exists and that is correctly configured in the Management Service page. Process:WMSvc User=NT AUTHORITYLOCAL SERVICE

### 📧 Solution

A common cause of this problem is that the **WMSVC** **certificate** has been deleted from the **certificate store** on the server so now **Management Service** has no certificate assigned causing a problem.

Open **IIS (Internet Information Services) Manager** and find **Management Service**

[!\[Microsoft Exchange 2013 CU11 Readiness Checks Error\](/wp-content/uploads/2016/01/img_56980aefcf232.png)](/wp-content/uploads/2016/01/img_56980aefcf232.png)

Open up **Management Service** option and as predicted **SSL Certificate** field is empty.

[!\[Microsoft Exchange 2013 CU11 Readiness Checks Error\](/wp-content/uploads/2016/01/img_56980b5075590.png)](/wp-content/uploads/2016/01/img_56980b5075590.png)

Simply **choose** a new certificate in it's place, **Apply** the change and **Start** the service.

[!\[Microsoft Exchange 2013 CU11 Readiness Checks Error\](/wp-content/uploads/2016/01/img_569810fec4be3.png)](/wp-content/uploads/2016/01/img_569810fec4be3.png)

After applying the certificate **Readiness Checks of Microsoft Exchange Server 2013 Cumulative Update 11 Setup** goes thru and installation of **CU11** can be started without further problems.

[!\[Microsoft Exchange 2013 CU11 Readiness Checks Error\](/wp-content/uploads/2016/01/img_56980cf66224e.png)](/wp-content/uploads/2016/01/img_56980cf66224e.png)

## Projets associés

Projets liés aux tags, catégories et au contenu de cet article.

[Tous les projets](/fr/projets/)

Recherche des projets associés...

[Retour au blog](/blog)

## Articles associés

- [Exchange 2013 – TooManyMissingItems or TooManyBadItems](/fr/blog/exchange-2013-too-many-missing-items-permanent-exception-or-too-many-bad-items-permanent-exception-solution/)
- [Exchange 2013 integration with SharePoint doesn’t work](/fr/blog/exchange-2013-integration-with-sharepoint-doesnt-work/)
- [Microsoft Exchange – OU picker is empty when creating new user](/fr/blog/microsoft-exchange-ou-picker-empty-creating-new-user/)

<!-- PowerForge markdown artifact sha256:9F826FC8B95C1BE70C9D6204B0ED088906047532289D4F1DF567968AF58C38FC -->
