Unable to start debugging on the web server. Access is denied.

Hello,

I have a problem remote debugging a VS.Net 2003 C# Web Project.
I can start the program in release mode but not in debug mode.

My details:
Client: VS.net 2003 Full Installation, WinXP Pro SP2, MDAC 2.8 SP1
Server: VS.net 2003 Full Remote Debugging Installation, Win2000 SVR,
MDAC 2.8 RTM both in the same domain. MDAC checked with the Microsoft
CompChecker tool. Both have SQL Server 2000 and IE6, the IP of the
server is in "Trusted Sites" in the clients IE. The Web Project on VS
is adressed by http://servername/... and not http://serverip/, the
files are adressed with \\serverip

The Server is a VMWARE Virtual Machine running on my client and has the
IP 192.168.52.131/24, the client itself has the IP 192.168.52.1 for the
VMWARE
network interface.

I have literally speaking (nearly) every user in (nearly) every group.
My Domain User is in Administrators group on both PC, also in "VS
Developers" and the "Debugger Users" group. I also added "Everyone" to
administrators on both PC to make sure this can't be a permissions
problem.



I read http://www.experts-exchange.com/Programming/Q_21247688.html
and tried everthing suggested there and also read
http://groups.google.de/group/microsoft.public.vsnet.debugging/browse_thread/thread/338adfd5acb5932d/0a69f852b22d6530

There I made an interesting discovery:
When I start a program in debug mode, Filemon on the server machine
does not output anything. It seems that the client does not try to
connect and justs puts out the error message.


The error message I get is:
"Error while trying to run project: Unable to start debugging on the
web server. Access is denied.
Click Help for more information."

I don't think this is reated to the VM thing. I assume it is a very
small but HARD to find configuration setting. I tried the processModel
username/password change in machine.config of the server, but this also
dind't change anything. And as I wrote above. As I'm administrator on
both machines, a permissions conflict really shound'nt be the cause.

By the way: How do I see who spawned a process? The task manager wants
not display this information and I have no idea where I can find it
elsewhere.


Any help is apprectiated, best regards,
S. Talanig

.

Relevant Pages

  • Re: recommended web site creation? And existing problem
    ... I don't think I've ever seen such a convoluted way to create a web project. ... This should be posted as two separate questions, and towards the end you confuse it by saying you are running XP workstation and Server 2003, but as I understand it none of this was done on the server, it was all done on your Workstation?? ... If I choose FileSystem it will be created at a FileSystem path and if I choose HTTP it will be created in a new Frontpage extended folder under W3SVC/1/Root of my local IIS. ... In general you should not need this menu; I avoided it because it looked like it might try to use an SQL server database to store settings which is totally stupid. ...
    (microsoft.public.vsnet.general)
  • SSH problems - suddenly stopped working
    ... F-Secure SSH Server will now be started in debug mode. ... 564:SshHostKeyIO Reading private host key from D:\Program ... 2628:SshConnection: Destroying SshConn object. ...
    (comp.security.ssh)
  • Re: Team work questions
    ... Sammy, ... As for the remote debugging, I just wanted to add that the few times I've ... >> server with VS 2003 installed. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: On why debugging OpenSSH can be so hard
    ... Since nobody seems to be aware of how debugging works on OpenSSH, let me just tell you that there is a client process and a server process and they separately have debug modes. ... The client debug mode could merely say "Login failed. ...
    (SSH)
  • Unable to start debugging on the web server
    ... I can successfully create a web project ... on a Windows 2003 server, but when I try to start the project I ... "Error while trying to run project: Unable to start debugging on the ... RPC Services are running ...
    (microsoft.public.vsnet.debugging)