I'm having an issue in IIS 7.5 where the ASP.NET feature section isn't showing on my web application.
My environment: Windows 2008 R2 SP1, IIS 7.5 (7.5.7600), .NET Framework 4.0
My issue is similar to the issue posted here: No asp.net features on IIS 7.5, only my environment is different. The 'add features' fix mentioned in that post doesn't appear to work in Windows Server 2008, as I'm not seeing a simple "ASP.NET" feature that can be selected.
I tried running the aspnet_regiis tool as administrator against .NET 4.0 with no luck. The application pool selected for the web application is currently configured to use .NET 4.0. This application is functional, so I'm assuming that .NET 4.0 is installed correctly, but I'd like to be able to configure a few more things that are in the ASP.NET section.
Try Roles > Right Click Web Server (IIS) > Add Role Services > Application Development to turn on the ASP.Net features in IIS
The UI is a bit different in the newer versions of Windows Server. Here is where you have to enable ASP.Net in order to get it working on IIS
The same issue but in a developer machine it may solve:
Windows Features - Internet Information Services - World Wide Web Services - Application Development Features - ASP.NET 3.5 + ASP.NET 4.8
Related
I have a working ASP.NET MVC 3 application. The project is built with VS 2010 and targets .NET 4.0. Now I re-targeted it to .NET 4.5 and successfully recompiled. Trying to deploy it to our test server (Windows 2008 R2 SP1) now fails:
Error Code: ERROR_APPPOOL_VERSION_MISMATCH
More Information: The application pool that you are trying to use
has the 'managedRuntimeVersion' property set to 'v4.0'.
This application requires 'v4.5'. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_APPPOOL_VERSION_MISMATCH.
The server has .NET 4.5 installed but there is no app pool 4.5 (because it's inplace upgrade and as I understand 4.0 pool should be fine). The client machine has VS 2012 and so Web Deploy 3 (was Web Deploy 2 previously). I also installed Web Deploy 3 to the server.
Tried to re-register ASP.NET with aspnet_regiis - no luck.
Why do I get the error and how can I fix it? This is so frustrating...
p.s.
Found similar question about RC but it does not help
Update:
Looks like this is a bug Microsoft hasn't fixed since CTP. IgnoreDeployManagedRuntimeVersion property did the trick. What a shame!
You can try adding this property to the project:
<IgnoreDeployManagedRuntimeVersion>True</IgnoreDeployManagedRuntimeVersion>
Windows Server 2012 includes .NET 4.5 by default and (when Web server role added) IIS has the following app pools: DefaultAppPool, .NET v4.5, .NET v4.5 Classic that use .NET Framework 4.0 (because 4.5 is inplace upgrade of 4.0). However, if we install .NET 4.5 redistributable on Windows Server 2008 that has .NET 4.0 installed the pools are not renamed: ASP.NET v4.0, ASP.NET v4.0 Classic. And this is the key why Web Deploy fails.
#kzu: not trying, this will work.
Had the same problem when installing Orchard CMS. Keep targeting v2.0.
But find the simple solution: in IIS, on the Application Pools (the list with all application pools), you can find the 2nd setting top right list: "Set Application Pool Defaults.." change there the default from 2.0 to 4.0 et, voila.
Register ASP.NET for IIS
a. Run CMD as Admin
b. CD to \windows\microsoft.net\framework\v4.x
c. Aspnet regiis -i
I have a Windows 2003 Server 64bit running IIS 6.0.
When I set the server up, I noticed that the 'ASP.NET' tab has been removed from the 'Web Sites' property in IIS Manager.
Now every website runs on .NET 2.0 and I need to change them to run on .NET 4.0.
I have ASP.NET 4 (32bit) enabled in the 'Web Service Extension' (the only other options ASP.NET versions 2 in both 32 and 64 bit modes).
I can confirm that in C:\Windows\Microsoft.net folder, there is both 'WOW' and 32bit .Net installation.
This is a production server with many websites and I'm afraid to run some IISReg scripts to put back the 'ASP.NET' tab.
When I try to the .Net 4 targeted website, I get an error:
Unrecognized configuration section system.web.extensions
The version information shows .Net 2.0
So what can I do?
Thanks!
As I indicated in my 'Comments' above, I had to run IIS in 32bit mode in a 64 bit system to target a certain web application. The background information for that can be see here:
http://dillieodigital.wordpress.com/2010/10/07/windows-server-2003-64bit-iis-6-32bit-asp-net-4-framework-and-targeting/
That resulted in running all websites in 32 bit mode with .NET 2.0. To get the new web application to run in .NET 4, I followed instructions, per:
http://mlichtenberg.wordpress.com/tag/iis6-asp-net/
Problem solved!
FYI.
Thanks.
This only references requirements for clients:
http://msdn.microsoft.com/en-us/library/8z6watww%28v=VS.100%29.aspx
I am looking for similar documentation in reference not just for .NET 4, but ASP.NET 4 and what IIS versions, OS SP's, etc. are required. I would like to see if there are any pitfalls to requesting IT to install ASP.NET 4 and MVC 3 on our server. Don't want to have egg on my face :)
Per the documentaiton on the installer download for .NET 4.0 ( http://www.microsoft.com/download/en/details.aspx?id=17851)
Additional Requirements for Server
Installation
If you have to perform a server
installation, your computer must have
the following software in addition to
the basic requirements:
•Internet Information Services (IIS)
version 6.0 or later. To access the
features of ASP.NET, IIS with the
latest security updates must be
installed before the .NET Framework is
installed. ASP.NET is supported only
on Windows XP Professional, Windows
Server 2003, Windows Server 2008, and
Windows Server 2008 R2.
So it will run in IIS 6.0 or above. If you want to know which operating systems support asp.net 4.0, that would be any operating system that supports IIS version 6.0 or above. This jives with my comment on your question.
That said, the biggest thing to watch out for is that you have to configure any .NET 4.0 IIS application to use a different applicaiton pool than 2.0, 3.0, or 3.5. There's more info on this here: http://johan.driessen.se/posts/getting-an-asp.net-4-application-to-work-on-iis6
WinXP has IIS 5 and the .net framework and ASP.NET 4 is supported on it. For server technologies, IIS6 and newer are supported, as Server 2003 which has IIS6 is the oldest server technology that supports ASP.NET 4.
I thought I could see an ASP.NET features panel (I don't know the exact name, though, some of them are .Net Compilation, .Net Roles, .Net Users and so on) on the IIS7 manager when I click a site node in the nodes list of the IIS7 manager. Now, I can see only IIS and Management, but no ASP.NET.
I first installed .NET Framework 4.0, so after installing IIS7, I used the aspnet_regiis tool, and seemed it worked well.
My environment is
Windows 7 Pro
IIS 7.5.7600
.NET Framework 4.0
I found the solution here.
http://forums.iis.net/t/1154433.aspx
Open Control Panel
Programs\Turn Windows Features on or off
Internet Information Services
World Wide Web Services
Application development Features
ASP.Net <-- check mark here
Andrew Zhu saved my life, thanks!
The solution that worked for me was slightly different:
Open Control Panel
Programs\Turn Windows Features on or off
Roles\Web server (IIS) Right-click Add Role Services Click on
ASP.NET and allow it to add any others it suggests.
Click Next
Close and re-open IIS
Can the IIS version in Windows Server 2008 R2 host all the following:
SharePoint 2010;
ASP.Net 4.0;
Classic ASP applications;
VB6 compiled .dll web applications.
If so, can SharePoint 2010 be the Default Web application when accessing the server?
Thanks,
Aaron
Sharepoint 2010 requires the .Net 3.5 framework.
I guess it's because a new SP version was being developed at the same time as the new .Net version, SP 2010 couldn't use .Net 4.0 yet.
Edit: here's the explanation in the words of the SharePoint Product Manager:
Unfortunately the release timeframes
didn't work out to get SharePoint 2010
built on .NET Framework 4.0.
I'm not sure about VB6 compiled .dll web application, but the rest is no problem.
Classic ASP isn't installed by default, but it's just a feature to enable.
As SharePoint is running .Net 3.5 it needs to be in a seperate AppPool from your .Net 4.0 sites.
Which site is the default is just a matter of selecting which Web Site is serving port 80 without a host header.
The separation; that needs to be explained here is the "application pool" term; a pool can use only one .net version so if they're in different application pools then everything is fine for IIS.
With the default web application is a relative object; if you mean through http://example.com then this means the port 80 is assigned to eg. Sharepoint on the application server.