Catastrophic Failure !!!

  • Thread starter Thread starter Muralidhar Chennoju
  • Start date Start date
M

Muralidhar Chennoju

Hi All

I'm getting the following error while trying to debug the application. Error
Message is as follows:

"Error while trying to run project: Unable to start debugging on the web
server. Catastrophic failure Would you like to disable future attempts to
debug ASP.NET pages for this
project? "

Any help is highly appreciated.

Thanks
Murali
 
Dear Muralidhar,

Run the web application without debugging (Use "Start without debugging" option.). Ater that you can attach the aspnet_wp.exe process to visual studio by going to Debug->Process. You will get a dialog listing all the running processes. click on the "aspnet_wp.exe" and click the "Attach" button. Now all the browsers running asp.net are attached to your Visual Studio and you can debug your application.

Regards
Gaensh
 
Hello,

Thank Ganesh, Your advice helped me.

But does anyone you know why this happens in the first place. And how do we
get rid of it so we can debug application without having to attach to the
aspnet_wp.exe everytime.

Thanks

Merdaad
 
You wouldn't happen to be debugging on a W2K domain controller, would you?

If so, this will help:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q827559

Good Luck,
--- Nick

Merdaad said:
Hello,

Thank Ganesh, Your advice helped me.

But does anyone you know why this happens in the first place. And how do we
get rid of it so we can debug application without having to attach to the
aspnet_wp.exe everytime.

Thanks

Merdaad
option.). Ater that you can attach the aspnet_wp.exe process to visual
studio by going to Debug->Process. You will get a dialog listing all the
running processes. click on the "aspnet_wp.exe" and click the "Attach"
button. Now all the browsers running asp.net are attached to your Visual
Studio and you can debug your application.
 
I am having the same problem as Murali; I am not debugging on a W2K domain
controller. Gaensh's suggestion is feasible, but I too would like to know how
to properly fix this problem.

I'm using Windows 2000.

(xpost: I have posted a question on vsnet.debugging as well)
Thanks!
Jacque
 
Hello Jacque,

From the KB article:This problem occurs when the account that is used to run the ASP.NET Worker
process (by default, this is the IWAM user account on the domain controller)
is not assigned with the "Impersonate a client after authentication" user
right in the local security policy. This problem may occur when you install
Windows 2000 SP4, and then install Microsoft Visual Studio .NET. In this
situation, the IWAM account is not granted the "Impersonate a client after
authentication" user right in the local security policy.
<<

Have you granted the IWAM account the named user rights?

--- Nick
 
Nick:

Thanks, but I had read the article (and attempted to go through the steps it
recommended), but I am _not_ using a windows domain controller.

Is an IWAM account something I should add to my machine even though it's not
a domain controller?

Thanks for your attention to the thread, I appreciate it.

Jacque
 
Hi Jacque,

The KB article does not only apply to domain controllers. The problem
happens more frequently on domain controllers but the same problems can
happen on ANY server.

Look at the account that is defined for the ASP.NET Worker Process and make
sure that it has the permissions "Impersonate a client after authentication"

Is the server in a domain at all or is it stand-alone?

--- Nick
 
I am now able to debug!!

Props to Nick for making me look more closely at the article he mentioned,
which referenced http://support.microsoft.com/default.aspx?kbid=821255, which
is what I needed to do.

For others who find themselves in this same situation, I think it might be
necessary to enforce the update of policy and restart IIS, as described in
the first article (Q827559):

at a command prompt:
secedit /refreshpolicy machine_policy /enforce
and then:
iisreset

Again my thanks to Nick for persistence.

Jacque
 
Back
Top