Sladescross's Blog

Blogging about Sharepoint related stuff

MSDTC Wait and Other Connectivity Problem October 10, 2013

Filed under: DCOM,Distributed,DTc,DTCPing,Kill,Orphan,SPID,Unit Of Work,UOW,WAIT — sladescross @ 4:55 pm

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

Let’s say you have already opened enough ports but still you get this error message. In this case you should run NETSTAT -anob on the machine which is returning this error message and try to find out which program is using all the ports. You should look for the ports that you have defined in the RPC Port range and look for all EXE’s which are listening on that port range.

I REMEMBER WHEN “SOMEONE” HAD BLOCKED RPC ON THE ROUTER BECAUSE OF BLASTER VIRUS ….

http://www.sqlservercentral.com/articles/Administration/99299/

you find  SPID = -2 as your main blocker. It’s at the top of a blocking chain with a dozen other transactions behind it trying to acquire resources. Until it’s killed, nothing will happen.

Seeing the main blocker as SPID -2 you would think of killing it like a normal SPID.

The minimum permission required to run the statements below is the processadmin
privilege.

Select req_transactionUOW
from master..syslockinfo
where req_spid = -2

This will return a 32 digit UOW number like ‘FE4A57F2-28C5-44F9-8416-B08760DFE7E9’. Use this UOW to kill the main blocker.

KILL ‘FE4A57F2-28C5-44F9-8416-B08760DFE7E9’

About these ads
 

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
Follow

Get every new post delivered to your Inbox.

Join 63 other followers