Whenever I try to run an ASPX project within the VS .Net IDE, both at home 

and at work, I end up getting the message, "Unable to start debugging on 

the Server. You don't have permissions to debug the server. Verify you are 

a member of the Debugger Users Group."



I am a member of that group.



Do I have to make some manual changes to either the web.config or 

machine.config file to solve this?



I have changed the process model username and password to "system" 

and "autogenerate".



Once again, I cannot find the answer in the help system, or if I have, I 

don't understand it.



Thanks.



j

J,



	Make sure that the ASPNET account (the aspnet_wp account) as

well as the VS Developers group has access to the complete web-folder

tree. See if giving "Everyone" access to those folders will help, if

none of the above work.



	Also, it's very tricky to accidentally set the username's

processModel in the wrong line, as they have copied every line into a

comment as well. I changed the username's processModel in the commented

code and I was baffled for three days.



	Also, when you change the machine.config or web.config a restart

of IIS also helps.



Minh.



-----Original Message-----

From: jude@j... [mailto:jude@j...] 

Sent: Thursday, February 28, 2002 1:31 AM

To: aspx_beginners

Subject: [aspx_beginners] Permissions & Debugger Users Group





Whenever I try to run an ASPX project within the VS .Net IDE, both at

home 

and at work, I end up getting the message, "Unable to start debugging on



the Server. You don't have permissions to debug the server. Verify you

are 

a member of the Debugger Users Group."



I am a member of that group.



Do I have to make some manual changes to either the web.config or 

machine.config file to solve this?



I have changed the process model username and password to "system" 

and "autogenerate".



Once again, I cannot find the answer in the help system, or if I have, I



don't understand it.



Thanks.



j




$subst('Email.Unsub').







_________________________________________________________



Do You Yahoo!?



Get your free @yahoo.com address at http://mail.yahoo.com

Thanks for the quick reply, Minh. It was your tip in another thread that 

turned me on to changing the processmodel username and password. They are 

in the right place, though I earlier made the same mistake you did and 

changed the comments!



Unfortunately, I've tried the things you mentioned above. This has been an 

ongoing problem since I installed the release version of VS .Net in late 

January, so I've done as much research as I can. I've just been giving up 

and working without the debugging.



Right now, all possible users (including the ones you mentioned) are in 

the Debugger Group. I restarted IIS (localhost) on my system. Still the 

same problem.



I'll try your suggestions at work tomorrow and see if they help there. 

That might give me a clue as to what's going on on my desktop at home.



Grrrrrrrrrrrrrrrrrr.



j

I think I got it! I found the answer under point number 6 below.



I'm posting what I found because it might help some others out there.



My thanks to Minh and Dan!





FROM: "Dan Hurwitz" <dhurwitz@s...> 

DATE: 10/23/2001 8:12:00 AM 

SUBJECT: [aspngvs] RE: FW: Why am I getting this error when trying to 

Debug? 

This apparently is a common problem.  I found the following list posted

here on Aspngvs on 9/14/01.  The item number 6 solved my problem.



> There are several things to try - we plan to have these linked up to

> the help topic you see when you get this error, in RTM.

>

> Is the account that you are logged in with in the Debugger Users group



> on the machine?

>

> Else, heres the rest of stuff to try:

>

> 1. Make sure you have a valid web.config file and one in which the

> compilation flag debug is set to true.

>

> 2. The web.config file must not have syntax errors. You can verify

> this by running the app, by selecting 'Start Without Debugging' from

> the debug menu. Any syntax errors will be displayed.

>

> 3. The user logged on must be a member of the Debugger Users group. If



> you login as an administrator be sure that Administrator is in the

> group. When debugging ASP.NET which runs as system, you need to make

> sure that the user logged in has Admin priveliges on the machine, as

> managed System processes can only be debugged by admins.

>

> 4. A valid URL must be specified for the start page of the project.

> Invalid extenions or project directory will result in error mentioned

> in 5.

>

> 5. If remote debugging to another machine, you need to make sure that

> the remote debugging components have been installed on the remote

> machine.

>

> 6. The security settings of IIS also affect debugging. To check this,

> you need to look at the settings for the default web site. To get at

> the Default Web Site settings start up IIS manager by doing either

> Start.Programs.Administrative Tools, select Internet Services Manager

> and expand the machine node OR select My computer on your desktop,

> bring up context menu, select Manage, expand Services and

> Applications. After selecting the Default Web Site, right mouse click

> and select its properties. Now select the Directory Security tab and

> click on the Edit button for Anonymous access and authentication

> control. Both 'Anonymous Access' and 'Inegrated Windows

> authentication' must be selected. If not, select them.

>

>

>

> An alternative way of debugging your application would be to manually

> attach to the process running your application. As an example consider



> a VB web application that is running under aspnet_wp.exe. You could

> start the application up by doing a Debug.Start without Debugging and

> then do a Tools.Debug Processes. Now check the 'show system processes'



> to list processes running under the system account. You can now select



> aspnet_wp.exe and click on the Attach button. You will then have the

> choice of selecting the program types you want to debug. You need to

> chose the Common Language Runtime if your application is a managed

> only application for instance.