Lansweeper wrote:
I'm not sure that I need to fix this because "sql server" is a dependent service for Lansweeper to run.
If for example someone is monitoring their services to see if they are started, it would appear that Lansweeper is functioning properly, while it is not because SQL server is not running.
in my opinion having lansweeper to simply stop is not a correct option.
it should be considered that the sql server may be hosted on a different physical server, like ours.
lansweeper should somehow alert that the sql service is down (but not by killing itself!), and periodically try to reach the sql server, so that an outage of, let's say, 1 hour of the sql server would not leave lansweeper dead.
But definitely not having lansweeper to autorecover is not efficient at all.