In the Add Application Pool dialog box, enter the name of the application pool in the Name: box, in the . NET Framework version: drop-down list select the . NET Framework version your site or application uses, in the Managed pipeline mode: drop-down list select Integrated or Classic, and then click OK.
Go to Websites & Domains > Dedicated IIS Application Pool for Website. Select the “Enable 32-bit applications” checkbox and then click OK.
Chances are you need to install .NET 4 (Which will also create a new AppPool for you)
First make sure you have IIS installed then perform the following steps:
cmd
and press ENTERcd C:\Windows\Microsoft.NET\Framework\v4.0.30319\
and press ENTER.aspnet_regiis.exe -ir
and press ENTER again.
-i
instead of -ir
. This will change their AppPools for you and steps 5-on shouldn't be necessary.(You can repeat steps 7-on for every site you want to apply .NET 4 on as well).
Additional References:
-ir
or -i
does (or the difference between them) or what other options are available. (I typically use -ir
to prevent any older sites currently running from breaking on a framework change but that's up to you.)
In the top level of the IIS Manager (above Sites), you should see the Application Pools tree node. Right click on "Application Pools", choose "Add Application Pool".
Give it a name, choose .NET Framework 4.0 and either Integrated or Classic mode.
When you add or edit a web site, your new application pools will now show up in the list.
Open a windows command line. Switch directories to C:\Windows\Microsoft.Net\Framework\v4.0.xxxx
where the x's are the build number. Type aspnet_regiis -ir
and hit enter. This should register .Net v4.0 and create the application pools by default. If it doesn't, you will need to create them manually by right-clicking the Application Pools
folder in IIS and choosing Add Application Pool
.
Edit: As a reference, please refer to the section of the linked document referring to the -i argument.
http://msdn.microsoft.com/en-us/library/k6h9cz8h.aspx
I just encountered this and whilst we already had .NET 4.0 installed on the server it turns out we only had the "Client Profile" version and not the "Full" version. Installing the latter fixed the problem.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With