.NET 3.0 install on IIS 6

Hi,

I've installed the .NET 3.0 framework to few IIS 6 Windows 2003 servers and had the same issue with all of them.

These servers are hosting ASP.NET 1.1 and ASP.NET 2.0 applications which are running fine.

After installing the framework I've found very wierd application event log warning entries.

Almost all of them were about that nodes and sections (new .NET 3.0) are doesn't exists in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config or C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\web.config. Which was true, so I didn't understand these warning. What was the intention of these?

Then 3 more interesting entry followed it:

1. A Web Host Script Mapping does not exist for extension .svc.

2. Could not detectASP.NET installation orASP.NET is disabled, skipping the Web Host Script Mappings component since it depends uponASP.NET to function properly. If you believe this message is an error, check yourASP.NET installation to make sure it is installed properly and is the correct version.

3. HTTP namespace reservations are not installed.

It is very weird, because all of theASP.NET 2.0 applications were happily run on that machine(before and after the install as well), so the ASP.NET was installed and enabled.

I've found the solution, what was to run aspnet_regiis then the ServiceModelReg.exe to re register the asp.net runtime and do the scriptmapping.

My question is why did the installer thought that I don't have ASP.NET runtime ?

This article says that the .NET 3.0 install automatically registers WCF with IIS if there is IIS installed, but not. I had to do it manually.http://msdn2.microsoft.com/en-US/library/aa751792.aspx

In this case is there any problem with my metabase or with custom config files ? Or everyone had the same ?

I was just wondering that why can't the installer do this re registration for me...

Thanks,

Csaba

[2998 byte] By [HarmathCsaba] at [2008-1-8]
# 1

Hi Csaba,

If you did install the WCF HTTP Activation feature for NetFX 3.0, it sounds like you may need to run servicemodelreg -i to reconfigure WCF again. You can find servicemodelreg.exe in the %windir%\Microsoft.NET\Framework\v3.0\Windows Communication Foundation folder. If you have trouble running this tool, it's probably because of the argument. It's "dash" i; sometimes the "dash" comes through as the wrong character when encoded for HTML.

Hope this helps!

Richie

SDET, WCF

RichieWeldon at 2007-10-2 > top of Msdn Tech,Visual Studio Orcas,Windows Communication Foundation (Indigo)...

Visual Studio Orcas

Site Classified