Re: Trying to create and debug ASP.NET on Windows 2003 Server

I think that if you are trying to access the project with the webserver
extensions
then the account being used needs to have the local logon user right, and if
the
access is via a shared folder it needs the logon over the network user
right.
That info is just in case the failure handler is interpreting the denial
when it says
access denied. Otherwise access denied is usually a missing permission
grant,
but the debugging attempt should be in context of account being used and you
say this is in the debugger users group, and I assume it has modify on the
files
that are the content. Are you seeing on the server any failed or successful
login events in the security log when you try (assuming this logging is
enabled)?
That would help to indicate how far one gets before the denial.

"Rico" <r c o l l e n s @ h e m m i n g w a y . c o mREMOVE THIS PART IN
CAPS> wrote in message news:3ErEf.311986$tl.155691@xxxxxxxxxxx
Hi Roger,

Yes, the server is set to allow both Serverside and Client side debugging
Yes, the content area was created as a virtual directory and has a network
share associated

I can't find any reference to "Windows 2003 firewall", but if you're
talking about the Web Service Extensions, all asp items are allowed, and
I've even tested with all items permitted, but still no luck.

I've tried a couple of workthroughs that I gleened from the net and have
had different error messages, but I'm still unable to connect. Right now
I'm getting an "Access Denied" error which keeps coming back no matter
what I try. This is strange, because I have admin rights and debugger
user rights, ASPNET has debugger rights, MDM is configured to run with
Debugger user rights and network service rights. The only thing I
couldn't figure out is how to add "NETWORK SERVICE" to the Debugger users
group, which is one item that I found elsewhere that I wasn't able to
accomplish. When using ADS, I open the Debugger User group and try to add
NETWORK SERVICE, it doesn't recognize this as a user, group or any other
object type.

Any ideas?

Rick



"Roger Abell [MVP]" <mvpNoSpam@xxxxxxx> wrote in message
news:u5hE147JGHA.604@xxxxxxxxxxxxxxxxxxxxxxx
Is the web set in its configuration to allow serverside debugging?
Is the content area being shared as a network share?
Is the W2k3 firewall on?

"Rico" <r c o l l e n s @ h e m m i n g w a y . c o mREMOVE THIS PART IN
CAPS> wrote in message news:FSaEf.411020$2k.54519@xxxxxxxxxxx
Hello,

I have an issue that I'm pulling my hair out about. I have a Windows
2003 Server with IIS 6.0.

I have an ASP.NET application that will run on the server up to a
certain point, which requires debugging.

I don't want to install Visual Studio on the server, so I will have to
debug from a remote workstation that does have VS installed on it.

I have two problems; 1) when I try to debug my web app, I get an error
message stating "Unable to start debugging on the web server. Debugger
is not properly installed. Run set up to install or repair the debugger.
Click help for more information (which doesn't help at all).

The second thing is, when I try and create a new web application, it
throws an error "Web Access failed..the default web access mode for this
project is set to file share..etc. etc.". I have run the gammut of
developer solutions, most of which seem to have left any developer I've
talked to scratching their heads. This lead me to believe that maybe
it's a Windows 2003 security issue.

Any ideas what might resolve these issues? Any help would be greatly
appreciated.

Rick








.

Relevant Pages

  • Re: asp.net debuggin error
    ... some times ASPNET or Network Service account (depending on OS, ... case it would be Network Service) is not part of debugger users group. ... the debugger component on the server failed to connect to the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: SQL2k debugging broken/problem
    ... Firewall existing between the client and the server. ... Turn off any firewall installed on the client computer and the server. ... "Troubleshooting the Transact-SQL Debugger" topic in BOL to allow remote ...
    (microsoft.public.sqlserver.tools)
  • Server 2003 reboots
    ... OS is Windoes Server 2003 Standard. ... After reboot there is a system has recovered from a serious error ... When I run Windbg on the mini dump files the problem file appears to be ... If a kernel debugger is available get the stack backtrace. ...
    (microsoft.public.windows.server.general)
  • RE: Stepping through stored procedures not working
    ... With Visual Basic 5.0 Enterprise Edition or later, you can debug SQL Server ... For information on problems that may arise when using the debugger with SQL ... SQL Server must run under a Windows NT user account, ...
    (microsoft.public.sqlserver.programming)
  • RE: Problem using SQL Debugger
    ... locally" user rights. ... | Thread-Topic: Problem using SQL Debugger ... | the server was replaced with a Windows 2003 Server, ...
    (microsoft.public.sqlserver.tools)