Debugger privileges for ASP.NET

[Tony Nassar]

Colleagues,

I'm new to Web apps, so forgive the density of this question. I believe I've
followed all the pertinent instructions, but I am not allowed to debug my
very first ASP.NET application. I am the sole user of this computer, and am,
obviously, the administrator. I have granted \\THISMACHINE\ASPNET debugger
privileges; it doesn't help. I followed the instructions to the point of
creating the absolutely minimal ASP application, with no data access layer
or other complications; still no luck.

Any advice?

Tony

 

[Hermit Dave]

Enclosing my conversation with Claude yesteday regarding a similar problem.
try the bottom to top approach.. ie start at bottom and read your way
through
you might find it easier to finid the post and reading your way through as
well... good luck

aaaah i know why.
think its trying to lauch the debugging as aspnet user (not sure if thats
the case).
no you dont need to reboot unless you changed or added user to to groups.
(even then log off is good enough)
just check to see if aspnet user belong to the groups.. lemme just check
msdn

http://msdn.microsoft.com/library/d...bconintroductiontowebapplicationdebugging.asp

if i find any more info will message you in just about a moment
think under debuggers you will have another user ie IWAM_MachineName

have a look at this as well
http://msdn.microsoft.com/library/d...ml/vxgrfASPNETDebuggingSystemRequirements.asp

--
Regards,
HD
Once a Geek.... Always a Geek

I did rebuild as you suggested but still the last error. Should i reboot my
system?


I'am having this message while trying to rune my asp.net app on win3k
server. I have set debug="true" in <compilation section
in my web.config .
Can anyone help me?
Thanks in advance

 

[Tony Nassar]

Dave, et al.,

ASPNET is the user who needs debugging privileges, and the configuration
file must allow debugging, but it does so by default for new Web
applications. In any case, I *did* add ASP to the Debugging user group; it
makes no difference. I can only think that there's something wrong with my
installation, but that kind of thing could take forever to untangle. Does
someone know how to find out how many, and which, ASP servers are running,
and what properties they have?

Tony

 

[Hermit Dave]

web.config <compilation language="c#" debug="true">
Build >> Confirguration Manager >> Debug Build
Project >> Project_Name Properties >> Configuration Properties >> DebuggingSave all
Rebuild the project

Debug >> start (you need to set an aspx page as a start page for the
project - under solutions explorer, right click the page and set as start
page)
This is how i got my application debug in local and remote servers

(Your problems may have somethings to do with impersonation but i am not
aware of those)
The links to two msdn article are probably good place to start.

 

[Tony Nassar]

Since I'm the sole user of the computer, and I certainly do have both
administrative and debugging privileges already, there doesn't seem to be
any reason why I should have to do all the things I was advised to do above,
but I went and did them anyway. I also reinstalled the .NET runtime (if you
press the "Help" button in the dialog informing you that you don't have
debugging privileges [even though I do, %$@@ it!], you'll be told that
installing IIS *after* VS.NET will cause problems), to no avail. I created a
Page_Load() method with this call in it:


System.Diagnostics.Debugger.Break();

....and then I *was* allowed to debug the process after the debugger attached
to it. This would not be possible if I did not have the right to debug
aspnet_wp.exe; obviously, then, I do. Thanks for all the contributions, but
I'll have to get by with this trick. I would guess that something is wacky
about my installation (of ASP.NET? of IIS? of VS.NET? Who knows?), but I've
spent enough time on this problem.

 

[Tony Nassar]

The user who needed to be added to the "Debugger Users" group was IUSR_xxxx
(xxxx being the machine name). I got lucky. That tweak isn't documented
anywhere.

 

[Tony Nassar]

All,

For what it's worth at this point, I did finally, inadvertently, solve the
problem. I had already tried adding EVERYONE to "Debugger Users," to
absolutely no avail. The user who needed to be assigned the "Debug Programs"
privelege through "Local Security Policies" was not "Anthony Nassar," nor
was is VUSR_xxxx (where xxxx is the machine name). No, it was IUSR_xxxx.
This is *not* consistent with the settings on my machine at work, where I
*do* debug ASP, nor is it documented anywhere. It's possible my settings at
home are simply messed up, but this works for now.

Tony