Article ID: 329282
Article Last Modified on 4/29/2007
APPLIES TO
- Microsoft Visual Studio .NET 2002 Professional Edition
- Microsoft Visual Studio .NET 2002 Enterprise Architect
- Microsoft Visual Studio .NET 2002 Enterprise Developer
- Microsoft Visual Studio .NET 2002 Academic Edition
This article was previously published under Q329282
Note If you are debugging on a computer that is running Microsoft Windows XP SP2, see the following article before you continue in this article.
833977 How to turn on remote debugging in Windows XP with Service Pack 2
SUMMARY
This article lists the minimum permissions that you must have to debug applications with Visual Studio .NET.
MORE INFORMATION
Debugging managed code
To debug managed code that is running under your own account, you must be a member of either the Administrators group or the Debugger Users group.
To debug managed code that is running under another user account, such as the local SYSTEM account, you must be a member of the Administrators group.
Debugging native code
To debug native code that is running under your own account, you must be a member of either the Administrators group or the Debugger Users group.
To debug native code that is running under another user account, such as the local SYSTEM account, you must be a member of the Administrators group or the Debugger Users group, and you must have the SE_DEBUG_NAME permission in the local security policy. By default, the Administrators group has this permission.
Debugging TSQL
To debug Transact-SQL (TSQL), you must have the permission on the database to execute the SP_SDIDEBUG stored procedure. By default, only the system administrator has this access. Additionally, Mssdi98.dll must be installed in the Binn directory of the computer that is running Microsoft SQL Server.
Note In Microsoft Windows NT 4.0, the debugger does not work correctly when you execute SQL Server under the local system account. For more information, visit the following Microsoft Developer Network (MSDN) Web site:
Setting SQL Server permissions for debugging
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/html/vxlrfSettingUpDebugUser.asp
Remote debugging
When you perform remote debugging, you must configure both local and remote systems to meet the minimum permission requirements:
On the remote computer, where the application to be debugged is running, you must have the minimum permissions that are listed earlier in this article.
Note When you perform remote debugging of native Microsoft Visual C or Microsoft Visual C++ applications with Remote Debug Monitor (Msvcmon.exe), the remote computer user does not have to be a member of the Debugger Users group. However, this method is not secure.
On the local computer, where the Visual Studio .NET debugger is installed, you must be an administrator or a member of the Debugger Users group to run the debugger successfully.
Note Remote debugging requires extra configuration if you are using DCOM or Machine Debug Manager (MDM). For more information, visit the following MSDN Web site:
REFERENCES
For additional information about debugging TSQL, click the following article number to view the article in the Microsoft Knowledge Base:
170496 Tips for Debugging stored procedures from Visual Basic
For more information about setting up debuggers, visit the following MSDN Web site:
Setting debug permissions on Windows 2000
http://msdn2.microsoft.com/en-us/library/aa291232(VS.71).aspx
For more information about how to enable remote debugging on Windows XP Service Pack 2, visit the following MSDN Web site:
Keywords: kbconfig kbdebug kbinfo kbmanaged kbnativeattributes kbremoteprog kbtsql KB329282
