Microsoft → [W2K] Visual Studio.Net

Has anyone ever installed/maintained this software? The problem I'm facing is that a user is getting an Access is Denied error message whenever she is trying to debug an asp.net application. The machine has IIS 6.0 installed. We've tried everything MS suggested (with the exception of granting the user full admin rights) and nothing worked. I prefer not to give this user administrative rights. Has anyone encountered this issue before?

Thanks.

How about this?
»msdn.microsoft.com/libra ··· eges.asp

First thing it says that in addition to being in the Users group, add the user to the Debugger Users group as well.

Yes, we've already done that. Unfortunately all suggestions form MS seems to be pointing to granting the user full administrative rights. The problem is, whenever the user begins to debug the asp.net application, IIS checks the user for administrative rights. They do this to prevent hackers and so on I guess from looking at codes. However, if the user account has already been given rights to the Debuggers Group (and MS Developers), then that should be more than sufficient.

Unfortunately I cannot see where it says that they are pointing to granting a user full administrative rights. Here's a checklist:
[ ] User is in the Debugger Users group
[ ] User is, in the Security Policy, added to: Log on as a batch job
[ ] User is, in the Security Policy, added to: Debug programs
[ ] Because IIS in involved, the user is also in the IIS_WPG group
[ ] Following permissions are applied for the user:

%WINDIR%\Temp
 Read and Write

%INSTALLROOT%
 Read

%INSTALLROOT%\ASP.NET Temporary Files
 Read and Write

Note   %INSTALLROOT% is of the form C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705 and %WINDIR% is of the form C:\WINDOWS.

»blogs.bartdesmet.net/bar ··· 512.aspx
»blogs.wwwcoder.com/rajag ··· 083.aspx
FIX: "Access Is Denied" Error Message When You Try to Access Indexing Service from ASP.NET with Impersonation Enabled

If all fails, talk to humans: Microsoft newsgroups

Well its not that they had it written in bold to give them full rights, but its implied you have to because there is an article on how non-administrative users can run the debugger tool but that involves an overly complex method. The only work around was to grant them admin rights but thats something we want to avoid.

And that list won't work since IIS_WPG is only available on 2003 and were running 2000.

As explained in one of the links above, in general you will need to be an administrator of that machine to have full control of the debugger. This is due to the security constraints of .net framework and IIS.

You could also give this link a try and see if it resolves your issue.

»www.eggheadcafe.com/ng/m ··· 8782.asp