Add Dependency to SQL Server for Enterprise Wireless Gateway Server Service

Even with “Automatic (Delayed)” setting on the Enterprise Wireless Gateway Server service, it is possible for this service to attempt to start prior to the SQL service on a server running both the iMonnit Enterprise site and the MS SQL server. Errors in the application Log show SQL communication errors by the service after rebooting. This prevents the service from starting until SQL Server Start sequence specifically has completed.

Note: Adding this dependency means if something stops the SQL server service, it will also Stop the Enterprise Wireless Gateway service.

Adding the SQL Dependency

  • Open the Command Prompt with Administrative privileges (right click > select "Run as Administrator").
  • Enter the following command:
sc config "Enterprise Wireless Gateway Server" depend= MSSQLSERVER
  • Press return.
  • Close the Command Prompt.
  • Restart the server.

Note: It is possible the service has a different name if it was manually adjusted or is from a previous or beta build. You may want to verify that the service names match the installations on your computers. But this should generally work as is for standard installations.

After the configuration is set. You can verify dependencies with this command in a Command Prompt launched as an Administrator:

sc qc "Enterprise Wireless Gateway Server"

You can also confirm this in the Services.msc Windows application under the Dependency tab of Enterprise Wireless Gateway Server service properties window.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.