This article describes the steps on how to fix the error 'SQL database name:' when GFI LanGuard fails to connect to the SQL Server during an installation or upgrade.
This error generally occurs when the SQL Server Browser service is not enabled and running or cannot appropriately read and connect to the SQL Server. In rare cases, the error might be caused by the wrong SQL server name chosen from the dropdown list.
Note: Starting in Languard v12.6, the MSOLEDB driver replaced the previous deprecated provider. Within earlier releases of Windows Server (2016 or earlier), this can result in seeing this "SQL Database Name" error due to earlier releases of the driver only supporting the unsecured TLSv1.0. Due to security concerns with enabling this outdated protocol, Microsoft has addressed this lack of support within the October 20, 2020—KB4580390 released for Windows 10 and Windows Server 2019, and TLSv1.2 is now properly supported.
- If you are running Windows 2016 or earlier, it is suggested that you consider upgrading to a modern server OS, such as Windows 2019 that supports the more secure TLS protocols.
- While not recommended, as a workaround, you can discuss temporarily enabling TLSv1.0 with your system admin on the LanGuard server machine and the server hosting the DB to allow you to complete the upgrade to get around the limitations of Windows Server 2016.
To verify the issue, start the installation or upgrade process, provide the SQL Server details required, and check that system fails to connect and displays the following error:
Instead of clicking OK, proceed with the steps below:
Open the Windows Services Manager by typing
services.mscon the Windows Run dialog ( press Windows key + R).
Locate the SQL Server Browser service. Ensure that the Startup Type is set to Automatic.
Start the service (if it is not running) or restart the service (if it is currently running):
Return to the LanGuard installation/upgrade window and click Ok.
Verify that the correct SQL Server name was chosen from the provided list of servers discovered on the network. You can check this with the Microsoft SQL Management Studio's help - the correct SQL instance is the one with the LanGuard LNSSScanresults12 database.
Click Ok on the Database Configuration panel.
You can also test connectivity to the database using Open DataBase connectivity as described in our Testing Database Connectivity Using ODBC guide.
The installation or upgrade should proceed without encountering the error/prompt mentioned above. If the issue persists, the Windows event logs should have information on why the logon is failing. If nothing helps, contact GFI LanGuard Support.