February 4, 2012 at 9:43 pm
When I click on the Debug button in SQL Server Management Studio, I get the following message:
[font="Times New Roman"]The Windows Firewall on this machine is currently blocking remote debugging. Remote debugging requires that the debugger be allowed to receive information from the network. Remote debugging also requires DCOM (TCP Port 135) and IPSEC (UDP 4500 / UDP 500) be unblocked.[/font]
According to Microsoft, you must configure Windows Firewall exceptions to enable Transact-SQL debugging when connected to an instance of the Database Engine that is running on a different computer than the Database Engine Query Editor. I'm not connected to a different computer--the Database Engine and the Database Engine Query Editor are both running on my laptop. According to Microsoft, there are no configuration requirements to run the Transact-SQL debugger when SQL Server Management Studio is running on the same computer as the instance of the SQL Server Database Engine. This doesn't appear to be the case. Can someone help me with this problem?
February 6, 2012 at 4:21 am
bob.ward (2/4/2012)
When I click on the Debug button in SQL Server Management Studio, I get the following message:[font="Times New Roman"]The Windows Firewall on this machine is currently blocking remote debugging. Remote debugging requires that the debugger be allowed to receive information from the network. Remote debugging also requires DCOM (TCP Port 135) and IPSEC (UDP 4500 / UDP 500) be unblocked.[/font]
According to Microsoft, you must configure Windows Firewall exceptions to enable Transact-SQL debugging when connected to an instance of the Database Engine that is running on a different computer than the Database Engine Query Editor. I'm not connected to a different computer--the Database Engine and the Database Engine Query Editor are both running on my laptop. According to Microsoft, there are no configuration requirements to run the Transact-SQL debugger when SQL Server Management Studio is running on the same computer as the instance of the SQL Server Database Engine. This doesn't appear to be the case. Can someone help me with this problem?
February 6, 2012 at 4:23 am
Enabling Web Server Debugging on Windows XP Service Pack 2
Windows XP Service Pack 2 provides enhanced security. To enable Web server debugging on Windows XP Service Pack 2, you must perform the following additional steps on the web server host machine. Administrator privileges are required.
To enable Web server debugging on Windows XP Service Pack 2
Open the Control Panel and double-click the Security Center icon.
Under Manage Security Settings For, click Windows Firewall.
In the Windows Firewall window, click the Exceptions tab, and then click the Add Port button.
Steps 2-5 open the TCP 80 port, which needs to be opened for ASP.NET, ASP, and ATL Server debugging.
In the Add a Port dialog box:
For Name, type a description such as TCP 80 port.
For Port Number, type 80.
For Protocol, select TCP.
(Optional) Press the Change Scope button. In the Change Scope window, select My network (subnet) only. This limits access to the firewall hole you are opening to machines on the local subnet. Use this option if possible.
Click OK to close the Change Scope dialog box (if you opened it in Step d).
Click OK to close Add a Port dialog box.
Click OK to close the Windows Firewall dialog box.
http://msdn.microsoft.com/en-us/library/bt727f1t(v=vs.80).aspx
February 6, 2012 at 9:31 pm
My firewall is managed by McAfee Personal Firewall. I added TCP port 80 but I'm still getting the error message. I'm still not sure why it's necessary to open a port. It shouldn't be necessary when everything is running on the same computer according to Microsoft.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply