Default.aspx with IIS 6.0 and .Net 4?

Question

1. We have deployed a .net 4 asp.net site on IIS 6.0.
2. Default.aspx is configured as one of the default document.
3. When we access the site using the following url

http://testsite

We expect it to render

http://testsite/Default.aspx

But instead we get 404 Not found error. We did not had this issue when it was deployed on .Net 2.0. Only thing that has changed on the server is that we use .NET 4 instead of .NET 2.0.

UPDATE: I tried the following link but it did not work.

Getting an ASP.NET 4 application to work on IIS6

The framework version on the server is .NET 4 RC. Will it help if we install the latest .NET 4 version on the server?

Update: The issue is resolved now. The problem was a Third party upload control that we were using which added its own HttpHandler in Web.Config. This HttpHandler started failing in the .NET 4.

Iatrogenic

just to double check, your setting the default document by going into the website properties, 'documents' tab and Adding 'default.aspx' to the top of the list? Saying 'default document' does make it sound like your on IIS 7.0 – Melesa

@Kellls: We can set the Default document for IIS 6.0 as well. – Iatrogenic

@Amitabh: Yes, setting the default document in 6.0 was the procedure I was outlining in my previous comment. I just mean that 'default document' is more of an IIS7.0 term. In IIS6.0 it is labeled 'default content page.' I simply wanted to double check that you were using IIS 6.0. – Melesa

@Amitabh: After you tried the procedure in that link, did you check your logs again? Were you getting 404.2 before you tried that? Are you still getting it now? Are you getting something else? – Melesa

@Kellls:2010-05-13 16:48:30 W3SVC36911924 192.168.1.11 GET / - 90 - 192.168.1.33 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.1;+WOW64;+Trident/4.4E- 302 0 0 – Iatrogenic

@Amitabh: 302 is a redirect, I would check your code, specifically the global.asax and the default.aspx. Look for Response.Redirect. – Melesa

@Kellis: There is a Response.Redirect in Default.aspx.cs? But why should that be an issue? – Iatrogenic

@Amitabh: The redirect is working, so the default document is set properly. The problem is that whatever your redirecting to is missing. – Melesa

I'm seeing a different error but otherwise the same symptoms. "Index and length must refer to a location within the string. Parameter name: length" – Tinhorn

Answer 1

Check the server logs, they will probably give you a better idea of what is going on.

You can find the path to the log file by right clicking the website in IIS and go to properties. Then goto the Web Site tab, under 'Enable logging' click properties and the logging properties window will show up which displays the path to the log file.

Melesa

Answer 2

With the new .NET 4 framework, comes some problems if you are running it on IIS 6 Windows Server. IIS 6 does not let you have more than one framework at the time running in the same instance like IIS7 that can create Application Pool targeting different framework. When IIS 6 runs under ASP.NET 2.0 (3.0 and 3.5 are superset, not frameworks) you are going to hit this error if the application is 4.0 Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive.

Source Error: 
Line 11:     </configSections> 
Line 12:     <system.web> 
Line 13:         <compilation debug="true" targetFramework="4.0"> 
Line 14:         </compilation> 
Line 15:         <pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID"/>   </ system.web>

You have a few options;

1. Downgrade the .NET application to 3.5 that Visual Studio 2010 makes it really easy. Just go to the Website properties -> Application tab and there is a drop down with all the framework releases, select 3.5, you VS2010 will reload the project and modify the web.config, if you added web service reference, that you may have to delete them and re-add them under 3.5

2. To configure the IIS6 and web config to solve the issue. I deal with the second part:

3. In IIS 6 console, you need to right click you project and click the property and check the ASP.Net tab whether Framework 4 is selected or not. If not select the framework 4.

But still you might face the same error because of the application pool; you might have same application pool for two different framework web application. IIS 6 does not let you have more than one framework at the time running in the same instance (means single application pool can’t use for two different frameworks) like IIS7 that can create Application Pool targeting different framework.

2. To solve this issue you need to create application pool and assigned this application pool to you framework 4 web application. To assign the application pool, in IIS console open the properties section of the web application, and click on the “Home directory” tab and selection application pool which you have created earlier from drop-down-list.
3. This two might now solve your problem completely sometime. You can get the error as “404 Page is not found”. Though you might now have any issue while in development time.
4. Basically page is not found issue is cause of other problem which is set hidden by is IIS6 . But you need to see the real cause. What you have do here is go to the IIS6 console open “web service extension node” which is right below the “default website” node. You will see the entire ASP.Net framework list over there, by default these frameworks might be prohibited so please select ASP.Net Framework 4 and click allow button. Browse you website now, you get other error beside “404 Page is not found”. You might get the error as listed below:
5. The value for the 'compilerVersion' attribute in the provider options must be 'v4.0' You’ll see following error when browsing the website The value for the 'compilerVersion' attribute in the provider options must be 'v4.0' or later if you are compiling for version 4.0 or later of the .NET Framework. To compile this Web application for version 3.5 or earlier of the .NET Framework, remove the 'targetFramework' attribute from the element of the Web.config file. To solve this issue, you need to modify your web config file as below:

Previously the CompilerVersion value is set as v3.5 but we already change our targetFranework to 4. Thus according to the error message above the 'compilerVersion' attribute in the provider options must be 'v4.0' or later if you are compiling for version 4.0 or later of the .NET Framework.

Hence your new setting will be as below:

    <providerOption name="CompilerVersion" value="v3.5"/>

Hope this will solve your ASP.Net 4 migration and hosting issue at IIS6.

Standpipe

Thanks for your valuable solution. I had a problm for hosting .Net4.0 site under IIS 2.0 configuration. I created virtual directory under Default Web Site and bound it to a seperate application pool. Its worked!. – Mylo

This solves my problem: "by default these frameworks might be prohibited so please select ASP.Net Framework 4 and click allow button". Thank you. – Yun

You are a beautiful person and I love you. I've been trying to fix this for 5 hours 32 minutes now. – Scanner

Answer 3

Here is a link to a more complete solution and explanation of this:

http://johan.driessen.se/archive/2010/04/13/getting-an-asp.net-4-application-to-work-on-iis6.aspx

Reddy

hmmm... was looking at the post again and realized that the poster tried this in one of his updates. Thought I was being helpful, and instead I'm just being repetitive... Anyways, this link worked for me. – Reddy

Answer 4

I think in 4.0 the default page setting is actually stored in the web.config. With the IIS 7.0 , IIS reads the web.config the determine what to do for the default page. I think IIS 6.0 is not reading the setting.

Craw