OK, after building a new system from scratch and producing the same behavior, I believe I've confirmed this to be a configuration problem in Windows 2003. Here are the steps to reproduce: 1. Start with clean Windows 2003 (I did a fresh install). 2. Install
EITHER the Windows Component Update files or use the VS.NET 2005 March 2004 preview installer to do a full VS.NET install with WCU files. 3. Apply HKLM\Software\Microsoft\ASP.NET\2.0.40301.9 corrupted registry key fix as per ReadMe file (Result: can use IIS
MMC Properties dialog again) 4. Launch IIS MMC and create a web site and application 5. Try to access that site (Result: any page with .aspx suffix will result in "Page Not Found" error) 6. Try c:\windows\microsoft.net\framework\v2.0.40301\regiis_aspnet.exe
-i and repeat steps 4 and 5 (Result: any page with .aspx suffix will result in "Page Not Found" error) [NOTE: this step will cause the corrupted registry key in (3) to reappear; you will need to fix it again] COMPARATIVE testing: - tried this on three separate
Windows 20003 Enterprise Edition servers (two physical machines, one OS rebuilt 2x); same results - tried same thing on a Windows XP Pro SP1a machine and had no problem with pulling up the website in step (5) above Frederik or others: I have been unable to
locate the appropriate MSDN 'beta' newsgroups for the VS.NET 2005 March 2004 Preview, so I can't be sure this will get posted to the right place. If someone knows how to get the word to the right people on the ASP.NET team, I'd be grateful (and, please, let
me know how to do that, if appropriate :-). Regards, /s/ James
Have you tried the ASP.Net Switcher that I pointed about in this thread? If not, try to use it and see if you can get it to work. Check if ASP.Net is allowed to run on your machine: Open IIS Manager. Select the monitoring station (or local computer if you are
on the machine's console) and select "Web Service Extensions" and select ASP.Net something and click the allow button.
Here is a response from Microsoft regarding this issue: "This is most likely due to an IIS 6.0 feature that limits the ISAPI extensions that are allowed to run. You can explicitly enable a version of ASP.NET in the IIS extensions manager. In the IIS MMC console
(Start > Run > inetmgr), select the extension manager in the left-side tree and then enable the version of ASP.NET you want. Note: No two versions of ASP.NET can run in the same application pool in IIS, so you'll need to make sure that you separate individual
applications of different versions (e.g. v1.1 and Whidbey) into different application pools. You can do this by right-clicking the the app root, choosing Properties, and selecting the appropriate app pool in the dropdown. Hope this helps, Bradley"
jgbeldock
Member
100 Points
20 Posts
Confirmed to be 2003 Server problem (was Re: This may be a Windows 2003 problem... (was Re: regii...
Apr 13, 2004 05:34 AM|LINK
Fredrik N
All-Star
29674 Points
5334 Posts
MVP
Re: This may be a Windows 2003 problem... (was Re: regiis failing after 2.0 installation; errors ...
Apr 13, 2004 06:43 AM|LINK
MVP, ASPInsider, WCF RIA Services Insider
My Blog
Fredrik N
All-Star
29674 Points
5334 Posts
MVP
Re: Confirmed to be 2003 Server problem (was Re: This may be a Windows 2003 problem... (was Re: r...
Apr 13, 2004 07:13 PM|LINK
MVP, ASPInsider, WCF RIA Services Insider
My Blog
Greg_Linwood
Member
5 Points
1 Post
Re: Confirmed to be 2003 Server problem (was Re: This may be a Windows 2003 problem... (was Re: r...
Apr 19, 2004 06:13 AM|LINK
paulsb
Member
40 Points
8 Posts
Re: regiis failing after 2.0 installation; errors in App Log looking for FW 1.2?!
Apr 20, 2004 10:59 PM|LINK