The Events2HVAC Windows service relies on several systems and services to be operational prior to startup. It is critical that the following services are running prior to Events2HVAC starting. As an example, if SQL server isn't running when Events2HVAC is attempting to log in to its SQL database, a fatal error can occur, shutting down the application and the service.
Microsoft Message Queueing - This is the background queuing mechanism required for handling commands in Events2HVAC. The Events2HVAC Windows service requires this service to be running without exception.
This is the local default instance of SQL server. Since Events2HVAC can reference SQL server from any PC or server, a built-in dependency is not established in Events2HVAC. In most cases this is fine, but if you find that you receive a fatal error from Events2HVAC during a reboot of your PC, you may need to add this dependency manually.
If your PC has multiple versions or instances of SQL, you will have to determine which service you are connecting to with Events2HVAC. Determine this by looking for the SQL instance names proceeding the $ in the services list.
Adding a depencency to your Events2HVAC service
Note: This procedure requires that you modify the Windows registry. You should always backup your registry prior to making any modifications. Incorrect registry modifications can cause serious problems.
See the Microsoft reference below for more info:
- Run RegEdit from the command prompt in Windows
- Go to the following registry key:
- Double-click on the DependsOnService key. This will open a pop-up window where the entry "MSMQ" will appear.
- In the pop-up window, below MSMQ, add a new entry with the name of the service dependency. For example, if you wanted MSSQLSERVER to be running first, enter the name of the service on which Events2HVAC should depend.
- Restart the PC and confirm that the service starts up in the correct order.