This article has been archived. It is offered "as is" and will no longer be updated.
When you try to debug a stored procedure on a remote computer that is running Microsoft SQL Server 2000, you may receive an error message that is similar to the following:
Cannot debug stored procedures because the SQL Server database is not setup correctly or user does not have permission to execute master.sp_sdidebug. Run SQL Server setup or contact database administrator.
Note The word "setup" in the first sentence of this error message should be "set up."
This problem occurs when the following conditions are true:
You are using Microsoft Visual Studio .NET 2003 to debug the remote stored procedure.
Visual Studio .NET 2003 is installed on a computer that is running Microsoft Windows XP Service Pack 2 (SP2).
Note This problem does not occur when you try to debug Transact-SQL in SQL Server that is installed on the local computer.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio .NET 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
You must install the following two hotfixes to resolve this problem:
The hotfix in this article. This hotfix is a client-side fix for Visual Studio .NET 2003.
Hotfix 890742. This hotfix is a server-side fix and is SQL Server 2000 Post SP3a hotfix build 2000.80.993.
Hotfix 890742 requires hotfix 885442. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
885442 FIX: You receive a "Server: Msg 8624, Level 16, State 1, Line 3 Internal SQL Server error." error message when you compile a delete query that contains sub-queries that use "NOT IN" clauses in SQL Server 2000
For more information about SQL Server 2000 Post SP3a hotfix build 2000.80.993, click the following article number to view the article in the Microsoft Knowledge Base:
890742 FIX: Error message when you use a loopback linked server to run a distributed query in SQL Server 2000: "Could not perform the requested operation because the minimum query memory is not available"
Note Remote Transact-SQL debugging will not work without both client and the SQL Server hotfixes applied.
Microsoft Visual Studio .NET 2003
You do not have to restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name --------------------------------------------------- 15-Oct-2004 01:27 7.10.4288.0 163,840 Sqlle.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Steps to configure Windows Firewall
When you use Windows Firewall, you must enable TCP port 135 (RPC port) and then add Visual Studio .NET 2003 to the list of exceptions. If you do not do this, you cannot do remote SQL debugging. To enable TCP port 135 and then open Windows Firewall for Visual Studio .NET 2003, follow these steps.
Important These steps may increase your security risk. These steps may also make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We recommend the process that this article describes to enable programs to operate as they are designed to, or to implement specific program capabilities. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this process in your particular environment. If you choose to implement this process, take any appropriate additional steps to help protect your system. We recommend that you use this process only if you really require this process.
In Control Panel, open Security Center.
Under Manage security settings for, click Windows Firewall.
Click the Exceptions tab, click Add Program.
In the Programs list, click Microsoft Visual Studio .NET 2003, and then click OK.
In the Windows Firewall dialog box, click Add Port.
In the Name box, type any name that you want.
In the Port number box, type 135 , click TCP, and then click OK.
Click OK to close the Windows Firewall dialog box.
Steps to reproduce the behavior
Start Visual Studio .NET 2003 on a computer that is running Windows XP Professional Service Pack 1.
Configure the computer to perform SQL debugging.For more information about how to set up SQL debugging, visit the following Microsoft Web site:
In Visual Studio .NET 2003, use SQL debugging to debug a stored procedure that is on a remote computer that is running SQL Server 2000. Make sure that you can debug the remote SQL Server stored procedure successfully.
Install Windows XP Professional SP2 on the client computer, and then restart the computer.
Start Visual Studio .NET 2003.
On the View menu, click Server Explorer.
Right-click Server, and then click Add Server to register the remote SQL Server.
Expand ServerName, expand SQL Servers, expand InstanceName, expand the Pubs database, and then expand Stored Procedures.
Right-click reptq1, and then click Step Into Stored Procedure.You receive the error that is described in the "Symptoms" section.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates