Article ID: 886680 - View products that this article applies to.
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:
Note The word "setup" in the first sentence of this error message should be "set up."
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.
This problem occurs when the following conditions are true:
Hotfix informationA 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:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMSNote 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.
Important informationYou must install the following two hotfixes to resolve this problem:
Note Remote Transact-SQL debugging will not work without both client and the SQL Server hotfixes applied.
PrerequisitesMicrosoft Visual Studio .NET 2003
Restart requirementYou do not have to restart your computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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 FirewallWhen 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.
Steps to reproduce the behavior
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates