Please follow the steps given below :


  1. Make sure your Data Source (SQL instance name) is correctly submitted in *both* of the configuration files below, found on the servers hosting your Lansweeper Server service and web console. The first config file is used by the Lansweeper service, the second by the web console. Open the files with Notepad or another text editor, perform a search for connectionString and make sure the instance name submitted in your connection string matches what you see in SQL Server Management Studio.

    Program Files (x86)\Lansweeper\Service\Lansweeperservice.exe.config

    Program Files (x86)\Lansweeper\Website\web.config

    checking SQL instance name in SQL Server Management Studio

    checking SQL instance name in Lansweeper configuration files

    - Make sure DNS is up-to-date and your database server's NetBIOS name resolves to an IP address. In the example above, the database connection will fail if DELPHINE cannot be successfully pinged from Command Prompt on the servers hosting the Lansweeper Server service and web console.

    - Within your Lansweeper configuration files you can replace your database server's NetBIOS name with its IP address, e.g. 192.168.1.4\SQLEXPRESS. This may not be a good idea in DHCP enabled networks however, as IP changes will break the database connection.

    - If (and only if) your Lansweeper Server service and web console are hosted on the same machine as the Lansweeper database, you can replace your database server's NetBIOS name with localhost, e.g. localhost\SQLEXPRESS.

  2. Make sure the SQL Server and SQL Server Browser services are running at all times on the server hosting your SQL instance.

    checking SQL service properties in Windows Services

    checking SQL service startup type in Windows Services

    starting SQL service in Windows Services

    checking SQL service status in Windows Services

    - Right-click one of the services in Windows Services.

    - Select the Properties menu item.

    - Set the service's startup type to Automatic in the resulting popup and hit OK.

    - Right-click the service and select Start, if the service is not already started.

  3. Make sure your SQL instance is configured for mixed (Windows and SQL) authentication, as the Lansweeper service and web console use a SQL user called lansweeperuser to connect to the database.

    checking SQL instance properties in SQL Server Management Studio

    checking SQL Server authentication in SQL Server Management Studio

    restarting SQL instance in SQL Server Management Studio

    - 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. If your Lansweeper service and/or web console are hosted on a different server than the Lansweeper database, make sure your SQL instance is set up to allow remote database connections.

    enabling remote connections in SQL Server Management Studio

    checking protocols in SQL Server Configuration Manager

    checking TCP/IP properties in SQL Server Configuration Manager

    enabling TCP/IP IP addresses in SQL Server Configuration Manager

    restarting SQL service in SQL Server Configuration Manager

    - Right-click your SQL instance name in SQL Server Management Studio, select Properties and open the Connections tab in the resulting popup.

    - Tick Allow remote connections to this server

    - Open SQL Server Configuration Manager and select the Protocols item under SQL Server Network Configuration. There should be a shortcut to SQL Server Configuration Manager in your Start menu.

    - Right-click Named Pipes and select Enable, right-click TCP/IP and select Enable.

    - Right-click TCP/IP, select Properties and ensure that connectivity is enabled for the appropriate IPs in the IP Addresses tab.

    - Right-click the SQL Server service under SQL Server Services and select Restart.

    - For SQL Server 2005, additional steps may be required to allow remote database connections. More information on allowing remote connections under SQL Server 2005 can be found in this Microsoft knowledge base article.

  5. If your Lansweeper service and/or web console are hosted on a different server than the Lansweeper database, make sure SQL Server traffic is allowed through your firewall(s). TCP port 1433 is the most basic port used by SQL Server, though other ports are sometimes used as well. More info on allowing SQL Server traffic through firewalls can be found in this Microsoft knowledge base article.