After moving the location of the MSDTC log file the MSDTC service fails to start

Follow

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.


More Information

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:

  1. Revert the configuration to the original polarity.
  2. Launch Component Services.
  3. Navigate to Local DTC > Properties .
  4. Change the Logging location to the default location – normally this is C:\windows\system32\MSDtc
  5. Verify that the file filter C:\windows\system32\MSDtc\** has been added to the protected set.
  6. Using the Neverfail Heartbeat Management Client, stop replication.
  7. Change the Logging location to the custom location on the active server.
  8. Change the Logging location to the one chosen at previous step on the passive server(s).
  9. Using the Neverfail Heartbeat Management Client, start replication.


Applies To

Neverfail for SQL Server Plug-in v201.5.5

Neverfail for SQL Server Plug-in v201.5.6

Neverfail for SQL Server Plug-in v201.5.7

Neverfail for SQL Server Plug-in v201.5.8


Related Information

None

KBID-2480

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.