"The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed"

  • "The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed"

    I am receiving the aforementioned error using a Project with VB6 and ADO without any linked servers.

    This Issue occurred only once in production server but I dont have access to the server so cant do much tweeking. Just need to know common causes

  • open component services on the server and local DTC info will be in there under DTC

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • But this issue came just once the settings haven't been changed. So if the settings were the problem them the issue should be recreate able.

  • i didnt mention settings. Under DTC in component services is where you'll find the transaction info 😉

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Hello,

    My name is Tony and I work on the distributed transaction coordinator team at Microsoft support. I noticed your forum question here and wanted to take a moment to try and provide some feedback.

    Considering the error you are seeing, I would recommend collecting the transaction logs. It's possible you are already collecting transaction tracing information and therefore it's possible we can isolate the particular transaction that was cancelled.

    If you're interested in trying to track this down, let me know and I'll provide more instruction.

    For the time being, check out our team blog and take a look at this entry which may help you on your journey:

    http://blogs.msdn.com/b/distributedservices/archive/2009/02/07/the-hidden-tool-msdtc-transaction-tracing.aspx

    Best wishes,

    Tony Devere

  • Thanks Tony,

    But in the hidden tool article its stated that It almost impossible to go through the complete Transaction Log file rather you have to create a log for the specific issue.

    And the issue isn't recreate able, so we can not get that. Is it possible to search the issue from the log file which is created by default.

  • Hi Tony

    Thank you for the link, it does a much better job of explaining DTC tracing. It seems the settings are relevant after all 😉

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • If the error message was captured with a time stamp, you should be able to locate the transaction. Assuming, tracing was enabled.

    Consider, enabling full tracing if you'd like to investigate this.

    Otherwise, depending on where the error is being throw you could write some code to handle the error differently.

    Best Wishes,

    Tony

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply