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 ….
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
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.