We help IT Professionals succeed at work.

Exchange 2013 CU19 Error - Step 1 of 17: Stopping Services

Justin Bechard
on
1,461 Views
Last Modified: 2018-02-25
Good day Expert's Exchange,

I am trying to Install Exchange Server 2013 Cumulative Update 19 on my Server 2012 R2 server. It is throwing this error code.

Error:
The following error was generated when "$error.Clear();
          & $RoleBinPath\ServiceControl.ps1 -Operation:DisableServices -Roles:($RoleRoles.Replace('Role','').Split(',')) -SetupScriptsDirectory:$RoleBinPath;
          & $RoleBinPath\ServiceControl.ps1 Stop $RoleRoles.Replace('Role','').Split(',')
        " was run: "Microsoft.Exchange.Configuration.Tasks.ServiceStopFailureException: Service 'FMS' failed to stop due to error:'Cannot stop FMS service on computer '.'.'. ---> System.InvalidOperationException: Cannot stop FMS service on computer '.'. ---> System.ComponentModel.Win32Exception: The service has not been started
   --- End of inner exception stack trace ---
   at System.ServiceProcess.ServiceController.Stop()
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StopService(ServiceController serviceController, Boolean ignoreServiceStopTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime)
   --- End of inner exception stack trace ---
   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.StopService(ServiceController serviceController, Boolean ignoreServiceStopTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime)
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StopService(String serviceName, Boolean ignoreServiceStopTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime)
   at Microsoft.Exchange.Management.Tasks.StopSetupService.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".


I have confirmed that this service is indeed stopped and set to disabled state.

Your advise is appreciate!
Comment
Watch Question

Valentina PerezExchange Servers
CERTIFIED EXPERT

Commented:
HI Justin,

After checking that the service is stopped. Have you run again the setup?

Have you the same error? In which step do you have this error?

Regards
Valentina
Justin BechardSenior Support Analyst

Author

Commented:
Hi Valentina,

Thank you for the response. I have tried rebooting and running the setup after confirming and receive same error message.

I receive this error when I go to run setup.exe from the Exchange2013-x64-cu19.exe extracted package, it is 'Step 1 of 17' when this happens.

Thanks,
Justin
Valentina PerezExchange Servers
CERTIFIED EXPERT

Commented:
Hi justin

Which CU do you have now?

From which CU are you upgrading?

Regards
Valentina
Justin BechardSenior Support Analyst

Author

Commented:
Hi Valentina,

I failed to check which CU they are running currently as their mail became broken when I started this. To my knowledge and advise from client they haven't updated since installation.

I checked the CU19 prerequisites prior to installation and it states no such minimum requirements to apply this.

Thanks,
Justin
Valentina PerezExchange Servers
CERTIFIED EXPERT

Commented:
Hi Justin,

You need to verify which Net framework.

Do you have Net framework 6.2?


Regards
Valentina
Justin BechardSenior Support Analyst

Author

Commented:
Hi Valentina,

I have checked and it is not listed in programs and features. It only have '.NET Framework 4 Client ...'

I will install this and run the setup again and post feedback afterwards.

Thanks,
Justin
Seth SimmonsLead Systems Administrator
CERTIFIED EXPERT

Commented:
...as their mail became broken when I started this

what is broken?
i personally would not try installing a CU on a broken system

I will install this and run the setup again and post feedback afterwards.

you need to check the installed exchange build before you do that
4.6 is only supported starting with CU16

you should also be running any CU elevated.  i have had CU installations fail on 2010 because of forgetting to run elevated
Senior Support Analyst
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
Seth SimmonsLead Systems Administrator
CERTIFIED EXPERT

Commented:
then the last comment should be the only one selected; the other one asked a question about a windows component that proved irrelevant to the root cause
Justin BechardSenior Support Analyst

Author

Commented:
Reached resolution myself
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.