Error: 'SQL database not running' when logging in to VigilEnt Security Manager. (NETIQKB32119)

fact
VigilEnt Security Manager 3.x

fact
VigilEnt Security Manager 4.x

symptom
Error:  'SQL database not running' received when logging into VigilEnt Security Manager.

symptom
Clicking 'Ok' upon receipt of the error closes VigilEnt Security Manager. The error does not occur again if logging on immediately afterward.

cause

This error may have several causes:

• The Microsoft SQL Server service may have been restarted and was in the process of starting back up.  In some cases, the MSSQL Service may take a while to start.
• The machine or laptop where the VigilEnt database resides has gone into suspend or standby mode. When this occurs, each service is suspended or stopped through the Service Control Manager. When SQL server is suspended, no additional connections are allowed.  Therefore, until the Service Control Manager resumes the SQL Server service and it fully reinitializes, connections will not be allowed.
• The SQL Server is stopped in 'pause' mode.  When restarted, SQL server has to start each installed database and perform a start-up routine before any connections can be made to the server.

fix
To resolve the above message, click OK to acknowledge the message then make another attempt to log into VigilEnt Security Manager.

Formerly known as NETIQKB32119