Put the scanning service in debug mode

Lansweeper Classic uses a service called Lansweeper Server to scan your network, trigger deployments, and send emails. This service writes its start events and errors to Program Files (x86)\Lansweeper\Service\Errorlog.txt on your scanning server.

In debug mode, the Lansweeper Server service writes more detailed information to Errorlog.txt. This helps identify database and other installation issues that can cause scanning failures, for example missing database tables, fields, or constraints. Lansweeper support may ask you to enable debug mode when you submit a support ticket.

Turn on debug mode

1. On the scanning server you want to put in debug mode, stop the Lansweeper Server service in Windows Services.
2. If your current Errorlog.txt is too large to send to Lansweeper support, rename it or move it to a different folder. The service creates a new log file when it starts.
3. Run Program Files (x86)\Lansweeper\Tools\ConfigEditor.exe on the scanning server.
4. In the Service tab, select the debug line, select Edit, and change the Value from 0 to 1.
5. Select Save configs and restart service.

When debug mode is active, the service adds a start event with a debug message to Errorlog.txt. From then on, the service writes detailed error messages to the log as errors occur.

Turn off debug mode

When you or Lansweeper support finish troubleshooting, turn off debug mode. If you leave it on, Errorlog.txt keeps growing rapidly.

1. Stop the Lansweeper Server service in Windows Services.
2. Run Program Files (x86)\Lansweeper\Tools\ConfigEditor.exe.
3. In the Service tab, select the debug line, select Edit, and change the Value from 1 to 0.
4. Select Save configs and restart service.