-
Title
Error: CActiveAdministratorAgent::DoAgentWork - Unable to open the database. Provider cannot be found. It may not be properly installed. -
Description
After Domain Controllers are patched and rebooted, they stop writing to the database. The following error occurs in the SLAgentSvc.log:***Error: CActiveAdministratorAgent::DoAgentWork - Unable to open the database. Provider cannot be found. It may not be properly installed.Error = -2146824582. Connection String: Provider=SQL01;Server=Quest01;Database=ActiveAdministrator;Trusted_Connection=yes;
-
Cause
The domain controllers are coming up before the Active Administrator server and SQL server or there is a SQL server client provider TLS connection compatibility issue between servers.
-
Resolution
WORKAROUND 1:
Within the Active Administrator console | Auditing & Alerting | Agents, highlight all of the agents and select "Stop" and then "Start".
If restarting the agents does not resolve the problem, try testing the connect to the SQL database from the DCs:
1. Logon to a DC with the issue using the same account that the Agent runs as2. Create a new file named Test.udl. You may need to rename the file to ensure it has the correct udl file extension3. Double click the file to invoke it4. Type the name of the SQL server (and instance if needed) or click the drop down to select it from the list5. Select Use Windows NT Integrated security6. Click the drop down for the database name and select the AA database name7. Click Test connectionIf the UDL test does not work, the issue is outside of Active Administrator and is due to communication issues between the DC and the SQL server.Note: If SQL is installed on the Active Administrator server, make sure the SQL Browser Service is started. Also verify that the default port (1433) appears in the SQL Configuration TCP/IP properties.
WORKAROUND 2:
For TLS 1.2 connection support, first make sure that the installed SQL Server version supports it. This can be verified with the help of the following link:
https://support.microsoft.com/en-us/help/3135244/tls-1-2-support-for-microsoft-sql-server
The AA agent installed in a DC first looks for the 2012 SQL native client (11.x) .dlls if they exist, and fall back to the older drivers otherwise which will only support a TLS 1.0 connection. To install the SQL 2012 native client on the DCs with agent, download it from here:
https://www.microsoft.com/en-us/download/details.aspx?id=50402Finally, try testing the 2012 SQL native client (11.x) connection from the DCs:
1. Logon to a DC with the issue using the same account that the Agent runs as2. Create a new file named Test.udl. You may need to rename the file to ensure it has the correct udl file extension3. Double click the file to invoke it4. Go to the "Provider" tab and select the "SQL Server Native Client 11.0" from the list, then click the "Next" button.4. Type the name of the SQL server (and instance if needed) or click the drop down to select it from the list5. Select Use Windows NT Integrated security6. Click the drop down for the database name and select the AA database name7. Click Test connection