Follow

Unable to Create Case and/or Process due to DTC

Created by: Jay Chambers
Created date:
Last Updated date:

Symptoms

  • When I create a new project in Summation Pro/eDiscovery it is not immediately displayed in the project list and the System Log may have one or both of the following errors: 

"Error creating case: CaseId : 0, CaseName : XXXX: System.Transactions.TransactionException: The operation is not valid for the state of the transaction."

"Error Invoke operation 'CreateProject' failed. HttpRequestTimedOutWithoutDetail"

  • When processing in Summation Pro/eDiscovery it may seem to do nothing for a while, but eventually displays the error "Unable to connect to database 0"
  • Case/project description says "Autocreated during FTK Cases synchronization." even though the case was created in Summation/eDiscovery.
  • The Processing Options tab doesn't show a Processing Mode selected.

 

Resolution

Ensure that all components are able to communicate with each other through the Microsoft Distributed Transaction Coordinator (MSDTC) using DTCPing.  This is typically done over port 135.  Refer to the steps here for proper DTCPing usage.

If the machines were created as clones in a virtual environment they may share a CID. This will prevent transactions from completing. To resolve generate a new CID for one of the machines. Additional MSDTC troubleshooting options can be found here.

Ensure the Microsoft Distributed Transaction Coordinator service is started and the Firewall has the correct exceptions for it.

The article below may also assist with determining MSDTC related issues:

http://blogs.msdn.com/b/distributedservices/archive/2008/11/12/troubleshooting-msdtc-issues-with-the-dtcping-tool.aspx

Attached is a script that will check all servers for the MSDTC service.  It should be run from the MAP (Web) server. 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

  • Avatar
    John Wittig

    This error can also be seen on Windows Server 2012R2 when two .NET 4.5.x security updates have been installed on a system with .NET 4.6 or higher. Please see this KB from Microsoft for details and resolution: https://support.microsoft.com/en-us/kb/3118750

  • Avatar
    John Wittig

    You can quickly find if the offending updates have been installed by running the following commands from the command prompt:

    wmic qfe | find “3098779”
    wmic qfe | find “3097997”

    The above will give you the installation date, which will make finding them in the list of installed updates much easier.

Powered by Zendesk