Are you running as an admin? Debugger user? The problem could be with
debugging into a process owned by another user. What I do is this (which you
actually have to do in order to debug as a non-admin user):
- Set up my user name and password encrypted in the registry using
- Change my machine.config to use my user name and password for aspnet_wp
- Configure IIS to use a separate, low privileged domain account for
- Configure my web site to use impersonation
Since I use anonymous on IIS and forms on ASP.NET, this allows me to debug
as a non-admin (it's my process, so I can do that) while still passing
credentials that only allow the process to do what it needs to do, and no
Microsoft MVP - Windows XP
Windows XP Associate Expert
"Meena" <meenaisiusa.com> wrote in message
news:10eea01c38387$e65464e0$a601280aphx.gbl...> Hi ,
> I have an ASP.NET web service running on a Windows 2000
> Server (WHICH IS NOT A DOMAIN CONTROLLER). Since I wanted
> to access a remote database on my intranet , I set up my
> ASp.NET worker process(aspnet_wp.exe) to run under a
> domain account(<domainname>\meenaaspnet). Everything is
> workimg fine. I can access my remote database also.
> However when I try to debug my program (using F11) it
> gives me this error.
> "Error while trying to run project:Unable to start
> debugging on a web server. Catastrophic failure"
> I can however run my application if I choose the option to
> Start without debugging.
> What do I do?