<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Orphaned MSDTC transactions (-2 spids)</title>
	<atom:link href="http://www.eraofdata.com/blog/2008/12/orphaned-msdtc-transactions-2-spids/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.eraofdata.com/blog/2008/12/orphaned-msdtc-transactions-2-spids/</link>
	<description>SQL Server posts that DBAs will (hopefully) find useful.</description>
	<pubDate>Wed, 10 Mar 2010 05:07:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Mike</title>
		<link>http://www.eraofdata.com/blog/2008/12/orphaned-msdtc-transactions-2-spids/#comment-2448</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 16 Dec 2009 05:51:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=99#comment-2448</guid>
		<description>Thanks for your suggestion. The GUI MSDTC actually matched what the queries showed i.e. killing the SPID also removed it from the GUI. Restarting the MSDTC didn't work but restarting the SQL Server Service ended up fixing the issue.</description>
		<content:encoded><![CDATA[<p>Thanks for your suggestion. The GUI MSDTC actually matched what the queries showed i.e. killing the SPID also removed it from the GUI. Restarting the MSDTC didn&#8217;t work but restarting the SQL Server Service ended up fixing the issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajmer Dhariwal</title>
		<link>http://www.eraofdata.com/blog/2008/12/orphaned-msdtc-transactions-2-spids/#comment-2447</link>
		<dc:creator>Ajmer Dhariwal</dc:creator>
		<pubDate>Tue, 15 Dec 2009 21:58:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=99#comment-2447</guid>
		<description>The transaction should still be visible in the MSDTC  GUI. If so, it will probably be marked as in-doubt. so right click on it and choose to Abort or Forget it.
Otherwise try restarting MSDTC.</description>
		<content:encoded><![CDATA[<p>The transaction should still be visible in the MSDTC  GUI. If so, it will probably be marked as in-doubt. so right click on it and choose to Abort or Forget it.<br />
Otherwise try restarting MSDTC.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.eraofdata.com/blog/2008/12/orphaned-msdtc-transactions-2-spids/#comment-2446</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Tue, 15 Dec 2009 08:38:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=99#comment-2446</guid>
		<description>Hi,

Thanks for the informative article. I wonder if you can help. I seem to be having problems with an orphan transaction blocking a resource. I've posted the problem here: http://www.sqlservercentral.com/Forums/Topic834337-364-1.aspx

Thanks</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Thanks for the informative article. I wonder if you can help. I seem to be having problems with an orphan transaction blocking a resource. I&#8217;ve posted the problem here: <a href="http://www.sqlservercentral.com/Forums/Topic834337-364-1.aspx" rel="nofollow">http://www.sqlservercentral.com/Forums/Topic834337-364-1.aspx</a></p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL Server Central</title>
		<link>http://www.eraofdata.com/blog/2008/12/orphaned-msdtc-transactions-2-spids/#comment-2305</link>
		<dc:creator>SQL Server Central</dc:creator>
		<pubDate>Mon, 28 Sep 2009 13:52:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=99#comment-2305</guid>
		<description>[...] I have experienced –2 session_ids and I understand how to fix this problem.&#160; Click here for more information on –2 session_ids.&#160; I had never experienced a –4.&#160; After a few [...]</description>
		<content:encoded><![CDATA[<p>[...] I have experienced –2 session_ids and I understand how to fix this problem.&nbsp; Click here for more information on –2 session_ids.&nbsp; I had never experienced a –4.&nbsp; After a few [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
