It turns out you are probably correct but.. The message does come with a drop down with three options one of which is to "fix the problem". Clicking on that was unsuccessful... UNTIL... I ran SSMS with administrator privileges. At this point, I'm back and running as before. Thanks for the help.
Latest security update has caused SS debugger to fail... 2008 r2 windows 10 - Windows Firewall
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 87%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMD%3C/text%3E%3C/svg%3E)
M Douglas Martin
0
Reputation points
Getting: The WIndows Firewall on this machine is currently blocking remote debugging. RD requires... TCP Port 135... UDP 4500/ 500 be unblocked. Can't Cancel, Unlock for local or Unlock for Computer. Trying to "Debug>Start Debugging".
SQL Server | SQL Server Transact-SQL
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 41%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVR%3C/text%3E%3C/svg%3E)
Venkata Ramanamma Uppu (Quadrant Technologies LLC) 0 Reputation points Microsoft External Staff2025-11-26T12:22:32.1+00:00 Hi M Douglas Martin,
Thank you for reaching out to Q&A Forum.
Thank you Erland Sommarskog and Obinna Ejidike for the prompt response.
I wanted to check if you had the opportunity to review the information provided and resolve the issue..? Please let us know if you need any further assistance. We are happy to help.
Thank you.
Sign in to comment
Answer recommended by moderator
2 additional answers
Sort by: Most helpful
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 0%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EOE%3C/text%3E%3C/svg%3E)
Obinna Ejidike 2,870 Reputation points Volunteer Moderator2025-07-12T12:28:07.82+00:00 Hi, M Douglas Martin
Thanks for using the Q&A platform.
The error you're encountering is related to a Windows security update that has likely tightened firewall rules, thereby blocking ports required for remote debugging using SQL Server (SS) or Visual Studio.You need to manually open the following ports in Windows Firewall.
Find Microsoft documentation for additional information:
https://learn.microsoft.com/en-us/visualstudio/debugger/configure-the-windows-firewall-for-remote-debugging?view=vs-2022#allow-the-remote-debugger-through-windows-firewall
https://learn.microsoft.com/en-us/troubleshoot/developer/visualstudio/debuggers/troubleshooting-remote-debuggingIf the response was helpful, please feel free to mark it as “Accepted Answer” and consider giving it an upvote. This also benefits others in the community.
Regards,
Obinna.
-
M Douglas Martin 0 Reputation points
2025-07-13T20:39:23.0366667+00:00 Thank you for the very detailed response. Follow on question before I do this... I'm doing all of this work on my local pc: SQL Server is installed on it. Should I really need to open up these ports???
-
Erland Sommarskog 133.9K Reputation points MVP Volunteer Moderator2025-07-13T21:25:35.0666667+00:00 So you are running the debugger against an SQL Server instance on your PC? In that case, the message is a little unexpected. Possibly this could be because connections are over TCP and not shared memory. You can inspect this with help of this query:
SELECT net_transport FROM sys.dm_exec_connections WHERE session_id = @@spidIn that case you might have to open port 135 for IP 127.0.0.1.
Or, do as I did. Stop using the debugger.
Sign in to comment -
-
Erland Sommarskog 133.9K Reputation points MVP Volunteer Moderator
2025-07-12T09:33:44.1366667+00:00 It would have helped if you had described your environment in more detail. Do I get it right that you are connecting to an SQL 2008 R2 instance from a PC running Windows 10, and this is not the machine where SQL Server is running?
The last time I ran the SQL Server debugger was in 2004, so it has been a while. But, yes, the error message seem to be correct. To be able to run the debugger against a remote SQL Server instance, you need to open port 135 in your firewall. Bear in mind that port 135 is not just any port, it is the port for RPC, remote procedure call, so do not open it for everyone, only for the IP address of the SQL Server machine.
You may ask why I have not used the debugger since 2004. The answer is that I gave up. I realised that every time I used it, I spent more time to battle firewalls and other security measures than I gained in productivity. Today, I work only with debug PRINT and SELECT and that works very well. The debugger is also limited, since you cannot inspect temp tables and the like.