Dave Burke - Freelance .NET Developer specializing in Online Communities

A freelance .NET Developer

To W2K3 : Simple Page Not Found fix

This is the 4th W2K3 Server I've setup (I do the web and SQL stuff; my very excellent Systems Admin does everything else) and each time I learn something new as I've posted in previous “To W2K3” entries.

This was a straightforward lesson.  IIS6 displays a

The page cannot be found

message when I know the page is there.  Full display here. From previous experiences I could conclude that something was missing or turned off in IIS.  Seems the ASP.NET subcomponent in the Windows Components Wizard was not installed.  Installing it did the trick.

 

Posted: Feb 05 2004, 10:07 AM by daveburke | with 4 comment(s)
Filed under:

Comments

BarfieldMV said:

Such a simple sollution to such an unexplainable problem. I really looked everywhere for an answer to this question. After installing windows 2003 om my laptop and configuring it as a workstation, activating the server components wasnt as easy as turning them off.

Where did you find this answer?
# April 21, 2004 10:05 AM

BarfieldMV said:

Also, do not forget to turn on asp.net in the IIS console -> web service extensions
# April 21, 2004 10:10 AM

Dave Burke said:

Barfield, This was one of those actions based on years experience. Usually the solution is found through googling for it, but this was similar to situations encountered in pre-2k3 OSs as well. Thanks for your comments!
# April 21, 2004 10:14 AM

BarfieldMV said:

Thank, i googled for it and found the solution on this blog :D . Blogs are really getting a good source of information, keep up the good work on this blog.
# May 21, 2004 2:36 AM

Andre Furtado said:

Unfortunately, this didn't work for me. Do you have any more suggestions?

Thanks,
-- Andre

(I'd thank if you could reply also to "andrewilsonfurtado at yahoo dot com dot br")

# June 9, 2004 6:36 PM

Dave Burke said:

Andre, the Page Not Found is a generic IIS6 error purposely vague as a security measure. Its vagueness makes it difficult for us as developers though! I encountered this under different circumstances which I've blogged about, so you'll find other instances in my Windows 2003 Server category and any items which start with "To W2K3." (You'll have to google on it to find them all.) Hope you find something here or elsewhere to fix you up.
# June 9, 2004 9:43 PM