Problems with clustered DTC server 2008 R2 when failed over or restarted

I had a working clustred DTC, but due to a disk migration, I had to delete the service and recreate it. Thats how the problem started.

When I recreate the service, it comes online perfectly. But when failed over or restarted, the service fails. Severname and Disk Drive resources comes online fine, but the DTC resource fails. I have set the dependencies for disk and name on the DTC resource.

As I said, when the service is created, it works fine, and I can see the service for clustred DTC on the active node. But when failed over or restarted, that service on the active node disappears.

Windows log says this:

Log Name:      System
Source:        Microsoft-Windows-FailoverClustering
Date:          5/26/2014 9:56:29 AM
Event ID:      1069
Task Category: Resource Control Manager
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      computer.domain.se
Description:
Cluster resource 'MSDTC-wfalitecl011Dtc' in clustered service or application 'wfalitecl011Dtc' failed.

Event XML:

  
    
    1069
    0
    2
    3
    0
    0x8000000000000000
    
    367173
    
    
    System
    computer.domain.se
    
  
  
    MSDTC-wfalitecl011Dtc
    wfalitecl011Dtc
  

More Log:

Log Name:      System
Source:        Microsoft-Windows-FailoverClustering
Date:          5/26/2014 9:56:29 AM
Event ID:      1205
Task Category: Resource Control Manager
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      computer.domain.se
Description:
The Cluster service failed to bring clustered service or application 'wfalitecl011Dtc' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.

Event XML:

  
    
    1205
    0
    2
    3
    0
    0x8000000000000000
    
    367174
    
    
    System
    computer.domain.se
    
  
  
    wfalitecl011Dtc
  

And more log:

```
Log Name: Application
Source: Microsoft-Windows-MSDTC Cli

It was a while i posted this, i did solve the problem after i while. The problem was related to Symantec Storage Foundation.

KB here: http://www.symantec.com/business/support/index?page=content&id=TECH125163

In the article it says you need to call them to get a hotfix, but SP2 that is avalible for download also solved the problem.

StackExchange Database Administrators Q#65889, answer score: 2