Shulou(Shulou.com)06/02 Report--

Recently, a friend asked me that he reported an error when installing Exchange 2013. I don't know what happened. He asked me if I had encountered it.

I took a look, hehe, it seems that it is really time to find a temple to worship the Buddha this year. This is the fourth time I have encountered this problem. I have encountered it three times in 17 years. Hey, today I will share with you the solution to this problem. Let's not talk too much nonsense. Let's look at the problem.

Problem description:

During the Exchange Server 2013 prerequisite check, approximately 90%, an error is displayed. One of the key services of Microsoft Exchange WMSVC could not be started. "Microsoft Exchange WMSVC cannot be started." Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service 'WMSVC' failed to reach status' Running' on this server. "

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, Unlimited1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService)

At Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService (ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited1 maximumWaitTime, String [] serviceParameters)

At Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService (String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Uncovered `1 maximumWaitTime, String [] serviceParameters)

At Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProce***ecord ()

At Microsoft.Exchange.Configuration.Tasks.Task.b__b ()

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

Another error in the event log: EVENT ID:1007,SOURCE:IIS-ISSManager

Solution:

A common cause of this problem is that the WMSVC certificate has been removed from the certificate store on the server, so the management service does not now assign the certificate that is causing the problem.

Open the IIS (Internet Information Services) manager and find the management service

Open the administrative services option and the certificate is displayed as empty

Simply select a new certificate at its location, apply the changes, and start the service.

Check the application certificate readiness check Microsoft Exchange Server 2013 Cumulative Update 11 installer through and CU11 installation can be started without further problems.

I hope the above content can help you all.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.