Today I set out to figure out why I couldn’t get IIS under windows server to serve up .ASPX pages.
I had asked for a .net setup from IT and when I placed my files in the site I could not get it to serve up ASPX pages. It would serve .HTML and .ASP but not .ASPX so I decided to investigate myself. Hopefully my investigation and solution will help you troubleshoot this issue without wasting as much time as I had to. All of the steps below refer to IIS 6.0 and Windows Server 2003 R2 Standard Edition.

Step one: Figure out if ASP.net is installed. You can do this several ways the quickest is to see if there is a ASP.net tab within your sites properties in the IIS Manager. Another way (and the way I chose to pursue) is to open the Control Panel and then Add/Remove Programs, and then click the Add/Remove Windows Components. Once Windows searches for installed components you will see a list. Click on Application Server and select details, this is where you should see ASP.net checked. If you don’t see ASP.net checked or if it isn’t there at all you will need to go to step two. If ASP.net is installed then skip ahead to step three.

Step two: Install ASP.net There are two ways to install ASP.net the easy way and then the way that you only do if you can’t see ASP.net in the Control Panel’s Add/Remove Windows Components section. The easy way is to check the checkbox in the Add/Remove Windows Components section and then follow the on-screen instructions. The hard way is to download the .net redistributable from Microsoft(the package linked is the 32 bit see bottom of page for X64).Install the package and then perform windows updates. This process will take 1-3 hours depending on connection speed and amount of updates needed. You will need to reboot when finished.

Step 3: ASP.net is installed but I still can’t see .ASPX pages: This can happen for several reasons and I could make you sift through thousands of google pages to figure out why, but that wouldn’t be very good of me I was getting 404 errors when trying to view an .ASPX page and this was because Active Server Pages where prohibited in Web Service Extensions. This KB Article explains why but you basically go into Web Service Extensions in the IIS manager and change Active Server Pages from Prohibit to Allow.

There we go I hope that helps you if you have a similar problem.

Thanks
David Bates