Re: Need help on debugging the code in .NET Web application.
From: Peter van der Goes (p_vandergoes_at_toadstool.u)
Date: 06/30/04
- Next message: Francis Ingels [MSFT]: "RE: Compiling a Program"
- Previous message: sridhar Akula: "Re: Setting focus to Web forms controls"
- In reply to: Muralidhar Chennoju: "Need help on debugging the code in .NET Web application."
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 30 Jun 2004 08:35:38 -0500
"Muralidhar Chennoju" <chmurali@stcroixsystems.com> wrote in message
news:up0DLnnXEHA.1036@TK2MSFTNGP10.phx.gbl...
> Hi All
>
> I'm getting the following error while trying to debug the application.
Error
> Message:
>
> "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? "
>
> Regards
> Murali
>
>
Here is a set of suggestions published previously by an MVP named Gregory
Beamer.
Thank you Gregory!
<quote>
ANSWER FROM A PREVIOUS THREAD:
There are a couple of reasons why debugging fails:
1. IIS is not set up to allow debugging
2. The person debugging is not a member of the debugging users group
3. There is no debugger on the server for .NET (remote most likely)
4. The debug process is hung
5. The IIS mappings are incorrect (very common when IIS installed after
.NET)
6. ASP.NET not mapped properly
7. IIS not working correctly
8. Missing web.config file
9. Execute rights set to none
10. RPC not set up correctly
I will look at docs and see if I missed anything. The method of
troubleshooting depends slightly on the version of windows, but generally it
is a matter of making sure debugging is on in IIS for the site. If the user
is an admin, they should be a member of the debugging users group; if not,
they have to be added. The third is strictly remote where you should not be
debugging anyway. If the process is hung, Task Mgr will clear it. For #5,
run:
C:\Windows Directory\Microsoft.Net\Framework\v1.0.3705\aspnet_regiis /i
where Windows directory is normally either Windows or WINNT. NOTE: For
Framework 1.1 change the string to:
C:\Windows Directory\Microsoft.Net\Framework\v1.1.4322\aspnet_regiis /i
For #6, you have to open IIS Manager and get ot the site properties
(normally default website) then Application Settings tab and click
Configuration. Then, click App Mappings and make sure .aspx is mapped to
C:\Windows Directory\Microsoft.Net\Framework\v1.0.3705\aspnet_isapi.dll
(same rules for Windows directory and Framework version #).
For #7, open a command prompt and type iisreset. That should cure it.
For #8, create a web.config file. No debug allowed without web.config, even
if you have no settings on non-default.
#9 is not your problem if the app runs.
#10 is only for remote debugging
Here is a help file with the most common reasons for ASP.NET apps to not
debug:
http://support.microsoft.com/default.aspx?scid=kb;en-us;306172
<unquote>
One additional comment:
If you have the Academic Edition of Visual Studio .NET, it does not support
remote debugging.
Hope this helps.
-- Peter [MVP Visual Developer] Jack of all trades, master of none.
- Next message: Francis Ingels [MSFT]: "RE: Compiling a Program"
- Previous message: sridhar Akula: "Re: Setting focus to Web forms controls"
- In reply to: Muralidhar Chennoju: "Need help on debugging the code in .NET Web application."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
