After moving the location of the MSDTC log file the MSDTC service fails to start
Summary
The SQL Server Plug-in is only able to provide automatic protection for the
MSDT.log
file; it is unable to replicate the configuration information used by Windows. If the log file location is changed, the Administrator must reconfigure MSDT on the passive server before switching over. This Knowledgebase article provides information about how to resolve the problem of the MSDTC service failing to start because the configuration information is incorrect on the passive.
Symptom
After changing the location of the
MSDTC.log
file location on the active server, performing a switchover, and running the File Filter Discovery task on the new active server, the
MSDTC.log
file location is not protected on the new active server and the Distributed Transaction Coordinator (MSDTC) service will fail to start.
Cause
Neverfail for SQL Server Plug-in provides automatic protection of the
MSDTC.log
file ensuring replication to the passive server(s). It does not however replicate the
MSDTC.log
file location information to the passive server(s). If the location of the
MSDTC.log
file is changed, you must manually update the passive server
MSDTC.log
file location information with the new location.
Resolution
This procedure should be performed to be able to change the location of the
MSDTC.log
file on the active and passive server(s).
To update the passive server(s)
MSDTC.log
file location:
-
Revert the configuration to the original polarity.
-
Launch Component Services.
-
Navigate to
Local DTC
>
Properties
.
-
Change the
Logging
location to the default location – normally this is
C:\windows\system32\MSDtc
-
Verify that the file filter
C:\windows\system32\MSDtc\**
has been added to the protected set.
-
Using the Neverfail Heartbeat Management Client, stop replication.
-
Change the
Logging
location to the custom location on the active server.
-
Change the
Logging
location to the one chosen at previous step on the passive server(s).
-
Using the Neverfail Heartbeat Management Client, start replication.
Applies To
SQL Server Plug-in
KBID-2480
Related Articles
SQL Server Plugin Version 201.5.17 - 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 ...
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 ...
Neverfail for SQL Server Plug-in Version 201.5.15 - Release Notes
Summary 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 both the data and service items used by SQL Server ...
Neverfail for SQL Server Plug-in Version 201.5.14 - Release Notes
Summary 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 both the data and service items used by SQL Server ...
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 ...