There is a script file you need to run to make ASP.NET the ISAPi filter to run aspx pages. I forget the details on it but this is a common problem and can be found documented on MSDN. Maybe someone else here remembers the details better than I but do not fret. There is a well-known solution.
I had this same problem once when IIS is installed after the .NET SDK and doing a repair install on the .NET Framework SDK did not fix it. From a command prompt:
C:\WINNT\Microsoft.NET\v1.0.3705\aspnet_regiis -r
will fix the script maps in your IIS to run your .aspx pages. See this:
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.