How to clear the IsAutoUpdateFetcher webconsole error

[#1]

You fire up your computer ready to take on the day but then you hit a sharp error when launching the Lansweeper web console. The message is short, but the impact feels heavy. This article explains what this error means and how to clear it fast.

IsAutoUpdateFetcher

What is happening?

You may see the message: webserver Error, Column 'IsAutoUpdateFetcher' does not belong to table. This stops the web console from loading and blocks your normal workflow. The issue appears most often in environments with more than one scanning server. 

This error happens when scanning servers in the same Lansweeper installation run different versions of the product. Each new Lansweeper release can add database fields. When one server updates the database and the other still uses an older version, the schema falls out of sync. The web console then tries to read a column that the older server does not know about. This mismatch triggers the IsAutoUpdateFetcher error.

How can I fix this?

The fix is simple: update every scanning server to the same Lansweeper version.

Follow these steps:

1. Verify your version on each scanning server. If the versions do not match, the system will continue to throw errors.

2. Update all scanning servers to the latest Lansweeper release. The update guide gives clear steps for each scenario. You can follow the instructions here:
   https://www.lansweeper.com/knowledgebase/updating-your-installation/

3. Download the most recent installer from:
   https://www.lansweeper.com/update-lansweeper/

4. After the update, restart your scanning services. Then launch the web console again. The database schema should now match across servers.

5. If you want to confirm what changed in the release, check the changelog:
   https://www.lansweeper.com/changelog

Once every scanning server runs the same version, the error disappears. Your environment becomes stable again, and your scans run with crisp reliability.