A pre-requisite while installing and operating FTK Central is to ensure that network connectivity is sufficiently established and firewalls allow traffic to pass.

While using FTK Central, issues might occur which can be caused by missing or insufficient firewall and/or MS DTC settings. 

Some symptoms could appear unrelated, e.g. labeling jobs not accepted, jobs not finishing, orphaned jobs, gr e.a.


General information


The requirements which Exterro formulates specific to installations with MS SQL-Server can be found in


How-to verify the DTC settings 


To verify whether the requested settings are correctly configured following options exist:

  1. make a visual inspection described in the KB article
  2. use this powershell command

 

Test-Dtc -LocalComputerName "$env:COMPUTERNAME" -RemoteComputerName <Remotehost>



Step 1: Chose the servers you want to verify

  • Choose one of the servers which are intended for any of the FTK-related entities: FTK Central, FTK Enterprise, DPE, DPM or MS SQLServer). Log in.


Step 2:  Open a Powershell session as administrator

  • Enter: Test-Dtc -LocalComputerName "$env:COMPUTERNAME" -RemoteComputerName <Remotehost> -Verbose
  • Replace <Remotehost> with the respective system which you like to verify.



Examples 


output without a remote system:

 

The lines in light blue are those which are also visible in the GUI. 

All checked settings within the GUI appear in the CLI output as ‘true’, those unchecked as ‘false’. 

To observe the graphical equivalent to these values go to: 

Start > Component services > Computers > My computer > Distributed Transaction Coordinator > rightclick on 'Local DTC' > Properties > security):



Example output with an remote client:

 

Notes: observe the lines ‘Pinging computer …’ – this is a bi-directional snmp-check (local to remote system & remote to local).



Remarks


  • The Powershell cmtlet is useful to quickly inspect either the local or a single remote system, or when several systems need to be checked. 
  • The command can be expanded to send output to a file or other tools for further analysis.

 

 

Limitations

 

  • Depends on network connectivity & sufficient permissions (e.g. a strict group policy, firewall settings en-route (so settings of other network devices than those at the local and remote server) might create ‘false negatives’.
  • The described approach does not replace a dtc ping, but focus on the current settings (= minimum requirements). 


  • Microsoft DTC ping changed infrequently and might not work on the present environment. 

            Verify with their latest publications.


            Background information to start with (check for the correct server release):

            https://learn.microsoft.com/en-us/troubleshoot/windows-server/application-management/ms-dtc-connectivity-issues