Home/ Questions/Q 236381
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T20:20:26+00:00

ServiceController serviceController = new ServiceController(someService); serviceController.Stop(); serviceController.WaitForStopped(); DoSomething(); SomeService works on a sqlserver file.

  • 0
ServiceController serviceController = new ServiceController(someService);
serviceController.Stop();
serviceController.WaitForStopped();
DoSomething();

SomeService works on a sqlserver file. DoSomething() wants to copy that SQL file. If SomeService isn’t closed fully it will throw an error because the database file is still locked. In the aforementioned code, I get past the WaitForStopped() method and yet the service doesn’t release the database file until after DoSomething(), thus I get an error.

Doing some more investigation, I find that before the DoSomething method call I see that the service controller status shows a stopped and yet looking at some ProcMon logs the service releases the database file after I’m thrown an error from DoSomething.

Also, if I put a Thread.Sleep between the WaitForStopped and the DoSomething method for say… 5 seconds, the database file is released and all is well. Not the solution of surety I’m looking for however.

Any ideas?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    ServiceController.WaitForStopped()/WaitForStatus() will return once the service implementation claims it has stopped. This doesn’t necessary mean the process has released all of its resources and has exited. I’ve seen database other than SQL Server do this as well.

    If you really want to be sure the database is fully and truly stopped, you will have to interface with the database itself, get ahold of the process id and wait for it to exit, wait for locks on the files to be released, …

    • 0