Remote Debugging Permissions
This topic applies to:
Edition |
Visual Basic |
C# |
C++ |
Web Developer |
|---|---|---|---|---|
Express |
.gif "Topic does not apply") |
|
|
|
Standard |
|
|
|
|
Pro and Team |
.gif "Topic applies") |
|
|
|
Table legend:
|
Applies |
|
Does not apply |
.gif "Topic applies but command hidden by default") |
Command or commands hidden by default. |
The following permissions are required for remote debugging:
Native Debugging |
|---|
To debug a process that is running under your account and password: No special permission is needed. To debug a process that is running under another account name: Your Windows login account has to be a member of the system administrators group on the remote computer. |
Managed Debugging |
|---|
To debug a process that is running under your account and password: No special permission is needed. To debug a process that is running under another account name: You Must Have Administrator privilege on the remote computer. If the ASP.NET worker process aspnet_wp.exe is running as SYSTEM or ASPNET, for example, you have to be an administrator on the computer where that process is running. Processes that host the common language runtime, such as SQL Server 2005, may enforce custom debugging privileges. |
TSQL (versions earlier than SQL Server 2005) |
|---|
You must have permission to execute sp_sdidebug() on the SQL2000 or SQL7 database. On operating systems before Windows XP, SQL Server must not be running as Local System. |
SQL Server 2005 |
|---|
Your Windows user account on both the application computer and the SQL Server has to be a member of the SQL Server sysadmin group. The account that is used for connecting to SQL Server 2005 in Server explorer also has to be a member of the SQL Server sysadmin group. For more information, see How to: Set SQL Server Permissions for Debugging. |