Last post Aug 31, 2007 02:25 PM by Mr.Spangle
Aug 23, 2007 10:26 PM|Mr.Spangle|LINK
I have just started a new job. I'm given a machine with VS 2003 and XP Pro installed from an image, IIS snap-in newly installed, and a legacy ASP.NET 1.1 app that is running nicely.
When I go to attach the debugger to the local aspnet_wp process, the process is not in the list generated in the Debug > Processes dialog. Nor is aspnet_wp in the processes dialog brought up by CTRL+ALT+DEL. I have never seen (or rather not seen) this before.
I have checked the box to show processes from all users and to show system processes, and it just isn't in there. Yet IIS is dishing up .aspx pages fine. I know in Win 20003 the process is names w3wp (or something) but on XP it's definitely aspnet_wp.
After searching around I found a number of people who have had this issue, and judging by the replies, no one has ever resolved it. Now I have it too. Darn.
Does anyone have anything I can try?
Aug 24, 2007 12:22 AM|leelu|LINK
This is a problem in the .Net Framework 1.0 from microsoft itself.
Please install the relevant sp.
FIX: ASP.NET requests run, but no ASPNET_WP.EXE worker process appears in Task Manager
FIX: Your ASP.NET request runs, but no ASPNET_WP.EXE worker process appears in Task Manager when you use Microsoft .NET Framework 1.0 SP3
Aug 24, 2007 08:53 AM|Mr.Spangle|LINK
Sorry, I don't think that's the issue I'm encountering. I'm running Framework 1.1, not 1.0. The issue MS outline should have been resolved in 1.1.
Aug 31, 2007 02:25 PM|Mr.Spangle|LINK
Ok, I found the answer.
Do not install IIS after .Net Framework 1.1. If IIS is installed second, then aspnet_regiis.exe does not run, and aspnet is not 'registered' with IIS. As a result, the worker process, though it works, does not show up in the process list.
If you ever get the issue yourself, just run aspnet_regiis -i (located in the Framework install directory) to install, and wahey, all is well.