This page explains how to solve connection issues between your SQL Compact, SQL LocalDB or SQL Server database and your SQL instance.
Lansweeper stores data, reports and settings in a database. Your database is hosted in either the Microsoft SQL Compact, Microsoft SQL LocalDB or Microsoft SQL Server database server. If you install Lansweeper under SQL LocalDB or SQL Server and the connection to your SQL instance is lost at some point, you may encounter errors such as the ones below.
These errors indicate that Lansweeper is unable to locate the SQL instance hosting your Lansweeper database. It's important to note that this does not point to database corruption or to an issue with the database itself.
Though there are many possible causes for a loss of SQL connectivity, below are some troubleshooting steps you can try to resolve the issue.
This article is divided into steps for the SQL Server database and steps for the SQL LocalDB server. You can verify which database server you are using with the ConfigEditor tool or in the Lansweeper web console.
To resolve the SQL connection errors if your database server is a SQL Server (most commonly SQL Server Error 53), follow these steps:
Program Files (x86)\Lansweeper\Tools\ConfigEditor.exeon the servers hosting your Lansweeper Server service and web console.
To resolve the SQL connection errors if your database server is a SQL LocalDB, follow these steps:
Was this post helpful? Select Yes or No below!
Did you have a similar issue and a different solution? Or did you not find the information you needed? Create a post in our Community Forum for your fellow IT Heroes!
More questions? Browse our Quick Tech Solutions.