ASP.net 4.0 default.aspx problem on IIS6

views:

955

answers:

+2 Q:

ASP.net 4.0 default.aspx problem on IIS6

I installed .net framework 4 on my windows 2003 enterprise x64, wrote simple asp.net 4.0 application (default.aspx page only). The application works great if request is to default.aspx, not to the root site:

contoso.com/ - doesn't work (Get 404 error)

contoso.com/default.aspx - works.

Default.aspx is in list of default documents in IIS. Please help.

Are you sure it's default.aspx not default.asp in the list of default documents?

David M 2010-04-14 06:36:34

absolutely. The first number in the list

Dimonina 2010-04-14 06:37:59

Did you add it yourself or was it already there? Is there any chance it could be a typo?

David M 2010-04-14 06:54:06

It was already there

Dimonina 2010-04-14 06:58:55

+2 A:

You will find the answer here http://johan.driessen.se/archive/2010/04/13/getting-an-asp.net-4-application-to-work-on-iis6.aspx

.Net 4.0 doesn't enable itself to run with IIS so you have to run the command (while in the folder c:\windows\system32): cscript iisext.vbs /EnFile C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll or in your case since you are running x64

cscript iisext.vbs /EnFile C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll

Jonatan B 2010-04-15 06:45:57

.net 4.0 isapi extension is enabled. Site works fine. Still have no answer

Dimonina 2010-04-15 10:06:04

Run cscript iisext.vbs /EnFile C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll and then restart IIS

HasanGursoy 2010-04-28 10:42:10

@Dimonina: Did this work.??

Amitabh 2010-05-12 20:24:45

Extension is enabled, because default.aspx works

Dimonina 2010-06-24 05:57:21

Having the same issue (website/default.aspx works, but website/ results in 404).

Running "cscript iisext.vbs /EnFile C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll" and then restarting IIS doesn't work.

Any further suggestions?

Will WM 2010-06-11 23:02:21

+4 A:

Found a fix in a seemingly unrelated location - try setting the "EnableExtensionlessUrls" registry key to 0:

ASP.NET 4 Breaking Changes -> ASP.NET 2.0 Applications Might Generate HttpException Errors that Reference eurl.axd:

In the Windows registry, open the following node: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\4.0.30319.0

Create a new DWORD value named EnableExtensionlessUrls.
Set EnableExtensionlessUrls to 0. This disables extensionless URL behavior.
Save the registry value and close the registry editor.
Run the iisreset command-line tool, which causes IIS to read the new registry value.

Will WM 2010-06-15 22:10:57

didn't work for me :-(

Dimonina 2010-06-24 06:00:04

This worked for me!

Aaron Carlson 2010-09-03 22:02:05

Just as a heads for for anyone who runs into this issue, we found that installing the hotfix for this issue http://stackoverflow.com/questions/3720720/how-serious-is-this-new-asp-net-security-vulnerability-and-how-can-i-workaround-i erased this reg key, which re-created this issue. Once we re-applied this fix, default documents worked correctly again

John Hann 2010-09-29 20:56:35

Has anyone found an answer to this issue? I am experiencing the same problem.

nkranes 2010-07-23 18:45:00

I don't have enough points to comment apparently, but I wanted to say that the solution from Will WM worked for me. Adding EnableExtensionlessUrls to the registry corrected the problem.

As a side note, if your run aspnet_regiis at anytime, it will remove this value and you will need to add it again.

Jarrod 2010-10-12 16:02:54

ansaurus

tags:

views:

answers:

ASP.net 4.0 default.aspx problem on IIS6

related questions