Error: "Unable to start debugging on the web server. Access is den

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Can anyone help please???
Been banging my head on a wall for a few days over this.

We have installed IIS, VS.net & ASP.NET on a Windows 2000 Server (SP4) and
VS.net client on an XP and 2000 Pro client.

We can create a new VB ASP.NET Web Application and succesfuly publish it to
our web server (from either client). However, we cannot Debug the application
as we constantly get the following error:
"Unable to start debugging on the web server. Access is denied"

I've searced through various info on the web and (amongst many other things)
tried the following:
adding the domain user (who publishes the applications) to the local
"Debugger Users" group on the server, and made the Debugger Users group a
member of the local "Administrators" group on the server,
changing the ProcessModel Username attribute to SYSTEM in the machine.config
on the client machine and the server,
changing the IIS Application Setting to "Script & Executable"

One workaround we did find was that if the server and user are logged on
with the same user account then Debugging works. However, obviously we do not
want the user logged on as the server account and I'm certain this isn't the
only way around this problem.

Any ideas where I should go from here?

Any help would be much appreciated.
 
=?Utf-8?B?Z21pY2tlbHNlbg==?= said:
Can anyone help please???
Been banging my head on a wall for a few days over this.

We have installed IIS, VS.net & ASP.NET on a Windows 2000 Server (SP4) and
VS.net client on an XP and 2000 Pro client.

We can create a new VB ASP.NET Web Application and succesfuly publish it to
our web server (from either client). However, we cannot Debug the application
as we constantly get the following error:
"Unable to start debugging on the web server. Access is denied"

I've searced through various info on the web and (amongst many other things)
tried the following:
adding the domain user (who publishes the applications) to the local
"Debugger Users" group on the server, and made the Debugger Users group a
member of the local "Administrators" group on the server,
changing the ProcessModel Username attribute to SYSTEM in the machine.config
on the client machine and the server,
changing the IIS Application Setting to "Script & Executable"

One workaround we did find was that if the server and user are logged on
with the same user account then Debugging works. However, obviously we do not
want the user logged on as the server account and I'm certain this isn't the
only way around this problem.

Any ideas where I should go from here?

Any help would be much appreciated.
Click to expand...



This solved my problem. Pass it on if it works!!

http://www.codinghorror.com/blog/archives/000048.html
 
Back
Top