I have a site that ran well for about 8 years on Server 2003/IIS 6. I recently migrated to Server 2008/IIS 7, and the site is no longer running (???). The site is located on
E:\, so nothing was changed when the OS was refreshed.
I recreated the site after the OS install (just like I would for IIS6). When I navigate to
default.aspx from another machine, I get a 404 error:
I'm not sure why I get the error since the page is there. And more bizarre is the favorite icon is served but not the page.
I've been poking around in the dark trying to find a solution. Some Googling took to me to missing Handler Maps, and there was nothing for ASP or ASPX at the server level or the site level. So I added a top level handler for the server according to Add a Managed Handler Mapping (IIS 7):
Name: ASP and ASPX Default Handler Request Path: *.asp, *,aspx Type: System.Web.Handlers
I verified the above handler was enabled at the site level. But the above did not work as I got a different 404 error (if there is such a thing):
I also tried changing permissions on the handler to add script and execute. That did not work either. I even deleted the Application Pool and recreated it. That did not work either. And adding
aspnet_isapi.dll as the type caused a 500 server error (per another page's suggestion).
EDIT (OCT-12-2013): I uninstalled and reinstalled Web Server IIS 7 (the server role). This time, I followed the instructions at How to Install IIS 7 and Setup a Static Website in 13 Easy Steps. No joy (and I could not find a useful Microsoft page on installing IIS 7. For example, this is the junk they are trying to claim is documentation: http://technet.microsoft.com/en-us/library/cc725762.aspx).
Any ideas what Microsoft has done to break a simple ASPX site? Or any ideas what hoops I should try to jump through next?