This page provides troubleshooting steps for resolving issues with the Lansweeper scanning service connecting to the database.
When you install Lansweeper, a service called Lansweeper Server is added to Windows Services on the machine hosting your installation. This service is mostly responsible for scanning your network and sending data back to your Lansweeper database. It also pushes configured deployments to Windows computers and processes emails.
The Lansweeper Server service is referred to as the scanning service and the machine hosting the service as a scanning server. A Lansweeper installation has at least one scanning server, though multiple scanning servers can be configured as well. By default, the scanning service is configured to automatically start, as the service needs to be running to be able to scan your network.
However, you may at some point notice that the service is marked as "scanserver unavailable" or that a secondary scanning server you're trying to connect to your installation doesn't show up in the web console. If a scanning server is marked as down or unavailable or if a secondary scanning server doesn't have its own configuration tab in the web console, this means the server isn't connecting to your Lansweeper database. Even if a secondary scanning service installed successfully, it could still fail to connect to the database, as our installer adds a random username and password to the server's configuration file.
To resolve this issue and have your scanning server successfully connect to the database:
Program Files (x86)\Lansweeper\Tools\ConfigEditor.exe on the problem scanning server.
Program Files (x86)\Lansweeper\Service\Errorlog.txt on the problem scanning server.