Neverfail for SQL Server Plugin's SQLServerConnections.xml file is still using old (local) syntax after upgrading Neverfail Engine to v8.5

Neverfail for SQL Server Plugin's SQLServerConnections.xml file is still using old (local) syntax after upgrading Neverfail Engine to v8.5

Summary

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.

 

More Information

 

Symptom

Neverfail for SQL Server Plugin DB Files Allocated Space and Databases Availability rules fail with the following warning message, in the following conditions:

Warning message: 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

 

Cause

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.

 

Workaround

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).


Applies To

Neverfail for SQL Server v201.5.12 and later

 

KBID-3026

    • Related Articles

    • Neverfail for SQL Server Plug-in Version 201.5.13 - Release Notes

      Summary This Knowledgebase article provides information about this specific release of the Neverfail for SQL Server Plug-in V201.5.13 What's new Changes since previous version: Support for SQL Server 2017 editions Added an option to include the SQL ...

    • Neverfail for SQL Server Plug-in Version 201.5.11 - Online Help

      About Neverfail for SQL Server Plug-in The Neverfail for SQL Server Plug-in is an add-on to Neverfail Continuity Engine, which provides protection for Microsoft SQL Server. It configures Neverfail Continuity Engine to protect the files and registry ...

    • Neverfail for SQL Server Plug-in v201.5.11 - Release Notes

      Summary This Knowledgebase article provides information about this specific release of the Neverfail for SQL Server Plug-in V201.5.10 More Information The Neverfail for SQL Server Plug-in provides file and registry filters that replicate critical ...

    • SQL Server Plugin Version 201.5.16 - Release Notes

      Summary The SQL Server Plugin is an add-on to Neverfail Continuity Engine, which provides protection for Microsoft SQL Server. It configures Neverfail Continuity Engine to protect both the data and service items used by SQL Server application, and ...

    • File Server Plugin v201.5.7 - Release Notes

      Summary This Knowledgebase article provides information about this specific release of the File Server Plugin. More information File Server Plugin automatically configures protection for all of your file shares as they are created, edited, or ...