Binaryworld - ASP.net Error on Windows 2003 Server: You do not have privileges to de ... [ ASP.net -> General Errors ]

Recentaly I had very uncommon problem which was not described anywhere and it was hard to solve without help of microsoft.public.vsnet.debugging news group.

I had the following error everytime I try to run the ASP.net project using F5 (Debug Mode)

"Error while trying to run project: Unable to start debugging on the
web server. You do not have privileges to debug the web server
process. Contact an Administrator to get the debug privileges on the
server. You may also want to refer to the ASP.NET and ATL Server
debugging topic in the online documentation."

I checked everyting mentioned on MS Site

http://msdn.microsoft.com/library/en-us/vsdebug/html/vxtbshttpservererrors.asp but still no luck. Finally I found the problem.

My problem was there was no users under Local Group Policy->User Rights Assignment->Debug Programs and thats why I was not able to run the ASP.net project in Debug Mode even though I have added Administrator in Debugger Users group.

If you face the same problem then perform the following steps

Make sure that account used for ASP.net development is added in Debugger Group
Now goto Control panel->Administrative Tools
From Administrative Tools, open the Local Security Policy snap-in for
Microsoft Management Console. Open the Local Policies node and then the User Rights Assignment node. Open the properties of the "Debug Programs" policy. On my server, the adware removed all security settings for this policy. It should have the Administrators group and the VUSR_yourcomputername user in the list. If not, add them and save the properties. Then close the Microsoft Management Console.
If you had to modify the security policy above, open a command prompt window. (Assuming that the system32 directory is part of the path environment variable, you should not need to change directories.) Update the group policy by typing the following command:

Click here to copy the following block

gpupdate /force

For Windows 2000 users, there is a different command set. See
http://support.microsoft.com/default.aspx?id=227448
After updating the group policy, I had to reboot the server in order for the change to take effect.

I hope this information helps to solve your problem.