You receive a "Cannot debug stored procedures" error message when you try to debug a SQL Server stored procedure in Visual Studio 2005 or in Visual Studio .NET

You use Microsoft Windows Terminal Services to log on as a non-administrator to a computer that is running Microsoft Windows Server 2003. In the Windows Terminal Services session, when you use Microsoft Visual Studio 2005 or Microsoft Visual Studio .NET to try to debug a Microsoft SQL Server stored procedure that is on a remote computer, you may receive the following error message:

To work around this problem, assign the SeCreateGlobalPrivelege user right to the Windows Server 2003 user account that you want to use to perform SQL debugging. To assign the SeCreateGlobalPrivelege user right to the user account, add the user account to the security setting for the Create global objects policy. To do this, follow these steps:

1. Make sure that the user account is a member of the following groups:
   • Users
   • Remote Desktop Users
   • Debugger Users
   • VS Developers
2. Add the user account to the security setting for the Create global objects policy. To do this, follow these steps:
   1. Click Start, point to Administrative Tools, and then click Local Security Policy.
   2. In the left pane of the Local Security Settings console, expand Local Policies, and then click User Rights Assignment.
   3. In the right pane of the Local Security Settings console, right-click Create global objects, and then click Properties. The Create global objects Properties dialog box appears.
   4. Click Add User or Group. The Select Users or Groups dialog box appears.
   5. In the Enter the object names to select box, type the name of the user account, and then click OK.
   6. In the Create global objects Properties dialog box, click OK.
   7. On the File menu of the Local Security Settings console, click Exit.

This behavior is by design.

Steps to reproduce the behavior

1. Use Windows Terminal Services to log on as a non-administrator to a computer that is running Windows Server 2003.
2. Start Visual Studio 2005 or Visual Studio .NET.
3. Make sure that an instance of SQL Server is running on a remote computer.
4. In Visual Studio 2005 or in Visual Studio .NET, try to debug a SQL Server stored procedure that is on the remote computer.

For more information, visit the following Microsoft Developer Network (MSDN) Web sites: For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base: