This Knowledge Base article provides information and workaround about Neverfail for SQL Server Plugin DB Files Allocated Space and Databases Availability rules failure when a passive management name is configured, after Neverfail Engine was upgraded to v8.5 from earlier versions.
Neverfail for SQL Server Plugin DB Files Allocated Space and Databases Availability rules fail with the following warning message, in the following conditions:
Task error output: [SqlServer]: Failed to obtain the databases list using connection string: Initial Catalog=master;Data Source=(local)\mssql2016;Integrated Security=SSPI;Pooling=false. Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
Conditions: a passive management name is configured on the active server and Neverfail Engine was upgraded to v8.5 from earlier versions
The SQLServerConnections.xml file is not recreated or changed by the Neverfail SQLServer Plugin with the new Data Source which uses netbiosName syntax. This change was implemented in the SQL Server Plugin version bundled with Neverfail Engine v8.5.
Design limitations: When Neverfail Engine is upgraded from any earlier version to v8.5, the SQLConnections.xml file is not deleted by the uninstall process of Neverfail Engine, being left in the %ProgramData% folder. Then, after Neverfail Engine upgrade, the SQL Server Plugin File Filter Discovery task first checks if the SqlServerConnections.xml exists: if it does, it won’t recreate it and will read the SQL Server instances from old .xml file which uses the old (local) Data Source syntax.
On the Active server, navigate to %ProgramData% and delete the SqlServerConnections.xml file. This will allow the file to be recreated by the SQL Server plug-in. Neverfail Engine will replicate then SqlServerConnections.xml on the passive servers on the passive servers (as it is part of the protected data set).
Neverfail for SQL Server v201.5.12 and later