“Login failed for user lansweeperuser”

Lansweeper data, reports and settings are stored in a database, which is hosted in either SQL Compact or SQL Server. If you install Lansweeper under SQL Server, by performing an Advanced Install, the installer automatically creates a SQL user called lansweeperuser. This user is used by the Lansweeper scanning service and web console to connect to the database.

If lansweeperuser gets corrupted, or has its password changed without an accompanying update of the Lansweeper configuration files, the service and console will no longer be able to connect to the database and you may see errors like the one below. The error below indicates that, even though Lansweeper is able to find the SQL Server instance hosting the lansweeperdb database, it is unable to access the database with the lansweeperuser account. It's important to note that this does not point to database corruption or an issue with the database itself. It simply indicates that the database cannot be accessed to read or write information. To resolve this issue, lansweeperuser needs to be reset.

To reset lansweeperuser and have the service and console successfully connect to the database again, do the following:

1. Stop the Lansweeper Server service in Windows Services
   
2. Stop your web server service in Windows Services. Your web server service is either World Wide Web Publishing Service (IIS) or IIS Express.
   
3. Make sure your SQL instance is configured for mixed (Windows and SQL) authentication. You can enable mixed authentication in SQL Server Management Studio. If SQL Server Management Studio isn't installed on your Lansweeper server, we recommend downloading it online. (You will need to perform a search for the Management Studio that's compatible with your particular edition and version of SQL Server.)
   
   
   
   - Right-click your SQL instance name in SQL Server Management Studio.
   - Select the Properties menu item.
   - Select the Security tab in the resulting popup.
   - Tick SQL Server and Windows Authentication mode
   - Right-click your SQL instance name and select Restart.
4. Execute the script below in SQL Server Management Studio to reset the lansweeperuser SQL user used by the Lansweeper service and web console to connect to the database. Replace what's marked in bold with the password you'd like to use for the lansweeperuser database user, leaving the single quotes in the script.
   /* Makes sure there are no objects in the lansweeperuser schema, so the lansweeperuser SQL user can be reset */
   USE lansweeperdb
   GO
   DECLARE c_ALTSCHEMA CURSOR FOR
   SELECT 'ALTER SCHEMA dbo TRANSFER lansweeperuser.'+name +';'
   FROM sys.objects
   WHERE SCHEMA_NAME(SCHEMA_ID) = 'lansweeperuser'
   DECLARE @SQLStmt NVARCHAR(200)
   OPEN c_ALTSCHEMA
   FETCH NEXT FROM c_ALTSCHEMA INTO @SQLStmt
   WHILE @@FETCH_STATUS = 0
   BEGIN
   EXEC(@SQLStmt)
   FETCH NEXT FROM c_ALTSCHEMA INTO @SQLStmt
   END
   CLOSE c_ALTSCHEMA
   DEALLOCATE c_ALTSCHEMA
   GO

   /* Resets the lansweeperuser SQL user */
   USE lansweeperdb
   GO
   DROP SCHEMA lansweeperuser
   GO
   DROP USER lansweeperuser
   GO
   EXECUTE sp_droplogin lansweeperuser
   GO
   USE MASTER
   GO
   EXEC sp_addlogin 'lansweeperuser', 'lansweeperuserpassword', 'lansweeperdb', [English]
   GO

   USE lansweeperdb
   GO
   EXEC sp_grantdbaccess 'lansweeperuser', 'lansweeperuser'
   GO
   EXEC sp_addrolemember [db_owner], 'lansweeperuser'
   GO

5. Run the following tool, found on the servers hosting your Lansweeper Server service and web console:
   Program Files (x86)\Lansweeper\Tools\ConfigEditor.exe
   
6. Click through any warnings the tool may be giving you about your password being incorrect.
7. Select the Password field and hit the Edit button.
   
8. Submit the same password you previously used in the database script and hit the Edit button.
9. If the ConfigEditor tool has multiple tabs due to your server hosting multiple Lansweeper components, select the other tab, click through any warnings and repeat the password changing process.
   
10. Hit Save and restart the Lansweeper and web server services.