FastClose Server comes up before SQL Server

A rare problem that has been seen, is where the FastClose Server service starts before the SQL Server service does.

In this scenario FastClose will attempt to connect to its repository before SQL Server can service the request. FastClose then gets into an unconnected state.

This can be resolved by restarting the FastClose Service - or by going to the Admin page, going to the repository connection settings, and clicking "Save".

However having to do this, every time the server is rebooted is annoying. Luckily it is possible to tell Windows that the FastCloser Service requires the SQL Server service to be up, before starting it.

To do this, start a command line prompt as an Administrator.

Then type the following:

sc config FastCloseServer start=auto depend="mssqlserver"

which will create the desired service dependency.