You are unable to connect to the LanGuard server backend database getting a startup message 'Can’t connect to database backend' or 'Access Denied' errors. This can happen after the upgrade, migration, change of the Windows service account credentials or password, or other environmental changes leading to the SQL database not being available.
This problem is usually encountered when the LanGuard service tries to connect to a remote SQL server machine or instance for which it lacks administrative rights. LanGuard runs under the service account running the LanGuard Attendant service, and if this account does not have access to the SQL database, you will get the errors above.
You can remedy using either of the options below.
Option 1: Ensure the GFI LanGuard Attendant service account is added to the SQL database and granted the necessary access
- Open the Services panel by going to Control Panel > System and Security > Administrative Tools > Services.
- Locate the GFI LanGuard 12 Attendant service, double click on it, and select the Log on tab. Notice the account specified to start the service.
- Ensure that this account has administrator rights to access the SQL Server machine. If you need to change the account - stop the service, make the necessary changes, and start the service back.
- Log in to the Microsoft SQL Server Management Studio and connect to the SQL server where the LanGuard backend database lives.
- Navigate to Security -> Logins.
- Locate the GFI LanGuard 12 Attendant service account or add it here.
- Right-click on the service account, choose properties and ensure that the server roles include public and sysadmin.
Option 2: Use SA user to logon from the LanGuard console
- Configure SQL server to mixed mode to accept SQL Authentication and set up the user account that will be used by LanGuard to connect. It is recommended to use the sa account.
- Launch LanGuard console and navigate to Configuration -> Database Maintenance Options.
- Click on the Database Backend Settings.
- Untick the box for Windows authentication and fill in the details of the SQL server sa user.
Launch the LanGuard console and verify that the errors are no longer there. If the issue persists, contact GFI LanGuard Support.