Interesting error during the installation of Exchange 2013 on a Server 2012 R2. The readiness check of the installation hangs at 90 % and then aborts after a long time with the following error message:
The exact wording somewhat shortened:
Error:
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
}
“ ausgeführt wurde: „Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Der Status ‚Running‘ konnte vom Dienst ‚WMSVC‘ nicht auf diesem Server erreicht werden.
The last part of the error message is probably the most important:
Der Status ‚Running‘ konnte vom Dienst ‚WMSVC‘ nicht auf diesem Server erreicht werden.
„WMSVC“ ist der Webverwaltungsdienst des IIS, welcher die Remoteserververwaltung benötigt wird:
The web administration service would not start on my server:
There are also a few errors in the event log, including this one, which put me on the right track:
Der Arbeitsprozess für Anwendungspool „WMSvcAppPool“, PID=“4056″, konnte für die Verarbeitung von HTTP-Anforderungen keine http.sys-Kommunikation initialisieren. Er wird daher von W3SVC als fehlerhaft eingestuft und beendet. Das Datenfeld enthält die Fehlernummer.
When checking the settings, I noticed that no certificate was assigned to the management service:
Normally, a self-signed certificate is assigned to the web administration service during installation. Apparently there was a problem in my case, because the certificate is not available, which was confirmed by a look at the certificate MMC:
In my case, I made it easy for myself and simply removed the service once via the server manager and added it again:
After reinstalling the service, the certificate was created:
And the service can also be restarted:
The correct certificate is then also displayed in the IIS Manager:
It is also sufficient to create an appropriate certificate, for example via the internal PKI, and assign it to the web administration service. In my case, reinstalling the service was quicker.
Now the installation works and the Exchange readiness check runs smoothly.