I'm using IIS 7.5 on Windows Server 2008 R2 x64 Enterprise Edition. In the project we have developed with ASP.NET 4.0 we used WCF Service. But it doesn't run over domain when the software is running from local computer. Otherwise, I am getting the following error:
HTTP Error 404.3-Not Found
The page you are requesting cannot be served because of the extension
configuration. If the page is script, add a handler. If the file should
be downloaded, add a MIME map.
You should install IIS sub components from
Control Panel -> Programs and Features -> Turn Windows features on or off
Internet Information Services has subsection World Wide Web Services / Application Development Features
There you must check ASP.NET (.NET Extensibility, ISAPI Extensions, ISAPI Filters will be selected automatically). Double check that specific versions are checked. Under Windows Server 2012 R2, these options are split into 4 & 4.5.
Run from cmd:
%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir
Finally check in IIS manager, that your application uses application pool with .NET framework version v4.0.
Also, look at this answer.
In my case, along with Mekanik's suggestions, I was receiving this error in Windows Server 2012 and I had to tick "HTTP Activation" in "Add Role Services".
In windows server 2012, even after installing asp.net you might run into this issue.
Check for "Http activation" feature. This feature is present under Web services as well.
Make sure you add the above and everything should be awesome for you !!!
I was having trouble accessing wcf service hosted locally in IIS. Running aspnet_regiis.exe -i wasn't working.
However, I fortunately came across the following:
Rahul's blog
which informs that servicemodelreg also needs to be run:
Run Visual Studio 2008 Command Prompt as “Administrator”.
Navigate to C:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation.
Run this command servicemodelreg –i.
Related
I've just got a new server setup on Windows 2008 Web edition. I'm trying to set the first asp.net 4 application up on it but am having nothing but problems.
The latest is that I'm getting the 404.17 error, which says "the requested content appears to be script and will not be served by the static file handler.".
I've done a lot of research on google but most suggestions seem to be to run aspnet_regiis -i to install asp.net 4. I've done this several times both on the Framework and Framework64 folders, but with no success.
I tried changing from the default application pool to a .net4 application pool, which appeared to work at first and I instead got a server error to do with permissions. I fixed that, and immediately the 404.17 error returned.
Other suggestions I've read say to go into the "turn windows features on and off" and make sure .net 4 is selected there under IIS. However on this server clicking "turn windows features on and off" takes me to the standard windows 2008 server manager. I click "add features" there, and only ".NET Framework 3.0 Features (Installed)" is listed and selected. .NET 4 isn't shown there, yet it is selectable through the application pools.
What else can I try to get the website running as I'm at a complete loss now. Its annoying because my old server was easy to manage - I did it all through the server itself without a control panel (Windows 2003), now on my new server I have to manage most of it through Plesk because there is no dns.
Any help would be much appreciated.
I too had the same problem but solved it with simple solution. My program was in framework 4.0 but in application pool was mapped to framework 2.0.
Just changed the frame work in application pool to 4.0.
It worked.
I've finally figured out the problem, and it was to do with Plesk itself.
After delving through some of the thousands of links throughout the plesk control panel I found a page for "Website Scripting and Security". Under there it was set to .NET 2.0. However, even though I'd installed .NET 4 on the server, Plesk didn't know about it. Although the application pool I'd set the website to run under through IIS was .NET 4, it still wouldn't work for some reason.
I then found another page under "tools and settings" for server components, and on that page is a refresh button. Hit that and it suddenly realised that .NET 4 was installed, went back to the website scripting and security page, selected .NET 4, and hey presto, I got a server error (never have I been so glad to see a server error).
I then just had to give the application pool identity read access to the web folder, and the website worked.
I wish I'd paid an extra £15 per month for Windows 2008 Standard edition now so I could manage it all manually without Plesk.
Ensure that you are running this application under a Virtual Directory, also ensure that your IIS has ASP, ASP.Net, ISAPI Extensions And Filters, Static Content installed.
Change the .net framework from 'plesk' panel:
go to Domains
select then domain
Go to 'Domain and Websites & Domains'
Hide Advanced Operations
Go to 'Asp.net Settings'
Go to 'Change Version'
select 4.0
If you don't have the 4.0 option then you must install the framework on your server first.
I am new to the world of IIS and I wanted to know the following...
I have heard about IIS Express. I run Windows 7 Ultimate and have installed the IIS that comes packaged with Windows 7.
As a developer, is there any major benefit for me if I install IIS Express over the default IIS that comes with Windows 7 for .Net Web projects?
Here are the differences from http://www.mywindowsclub.com/resources/3302-Key-differences-between-IIS-IIS-Developer.aspx.
If you already have IIS installed - its a better product. IIS express would only be used by people who don't have access to IIS or want something that is lighter than IIS but more like IIS than Cassini.
Integrated with OS
IIS 7 ships with the operating system and is tightly integrated to Windows.
IIS developer express is a separate downloadable tool
Targetted users
IIS 7 is for both developers as well as for production purposes.
IIS developer express can be used only for development purposes and not for production.
Supported Windows editions
IIS 7 will work only on Windows Vista and newer editions of Windows. In case of server OS, IIS 7 will work only on Windows 2008.
IIS developer edition will work even on older version - starting from Windows XP and newer.
Process model and activation
In IIS 7, the worker thread is automatically launched and managed by Windows Process Activation Service.
In case of IIS Express, user has to handle this.
FTP support
IIS developer express does not support FTP while IIS 7 supports it.
WCF support
IIS Developer express supports only WCF over HTTP.
IIS 7 supports WCF including over TCP, Named Pipes, and MSMQ.
Multi developer support
IIS 7 is a single user application.
IIS Developer express supports multi developer environment. Configuration files, settings, and Web content are maintained on a per-user basis.
Visual Studio integration
All editions and versions of Visual Studio have built-in support for IIS 7.
Only VS 2010 and future versions will have built-in support for IIS developer express.
Runtime extensions
IIS developer has support for URL Rewrite and FastCGI.
Webmatrix offers support for SEO, database management and Web Deployment. Other extensions that are offered with IIS are not yet tested with IIS Developer express.
Management Tools
IIS 7 is managed using the IIS Manager.
IIS Developer express can be managed using Webmatrix. Also, the express edition has support through system tray.
Port used by IIS
The default website comes with IIS 7 listens to port 80.
The default website part of IIS developer express listens to port 8080 to avoid conflicts with IIS 7 when they are running side by side.
From Scott Gu's post on IIS Express:
Why Not IIS
The downside with using the IIS option today, though, is that some
companies don’t allow full web-servers to be installed on developer
machines. IIS also requires administrator account access to setup and
debug projects. Different versions of Windows also support different
versions of IIS. For example, if you are running on Windows XP you
have to use the IIS 5.1 web-server that comes with it – which doesn’t
support all the new features of IIS 7.x. Configuring a web project
within VS to use IIS also requires some extra installation and
configuration steps.
Why IIS Express
It’s lightweight and easy to install (less than 10Mb download and a
super quick install) It does not require an administrator account to
run/debug applications from Visual Studio It enables a full web-server
feature set – including SSL, URL Rewrite, Media Support, and all other
IIS 7.x modules It supports and enables the same extensibility model
and web.config file settings that IIS 7.x support It can be installed
side-by-side with the full IIS web server as well as the ASP.NET
Development Server (they do not conflict at all) It works on Windows
XP and higher operating systems – giving you a full IIS 7.x developer
feature-set on all OS platforms IIS Express (like the ASP.NET
Development Server) can be quickly launched to run a site from a
directory on disk. It does not require any registration/configuration
steps. This makes it really easy to launch and run for development
scenarios.
After a couple of hours i found one significant reason to use Express over Local IIS : "Edit and Continue" does not work on local IIS.
While developing an ASP.NET application I tried to install IIS Express 7.5 onto Windows XP. I downloaded the installer and ran it - IIS installed okay (I see it in Add/Remove Programs list), but I didn't find anything for controlling it (like the IIS console).
My colleague told me I should use IIS Manager for IIS 6, I installed it, but it only allows me to control IIS 5 that was installed on XP from the very beginning. I tried to install IIS Manager for IIS 7 but when I ask it to connect to localhost it shown an error message saying it can't find Microsoft.Web.Administration assembly which AFAIK is only available on Vista and later versions.
How exactly do I install IIS Express 7.5 and some administration console to control it onto Windows XP?
Currently there is no UI for IIS Express. You can install WebMatrix from following link which provides some basic IIS Express mangement functionality.
http://www.microsoft.com/web/
OR
You can also use IIS Express from command line. Below link provides info about how to start use IIS Express from command line.
http://learn.iis.net/page.aspx/870/running-iis-express-from-the-command-line/
IIS 7.5 Express can be controlled via integration with VS2010 SP1, WebMatrix and the command line.
From the IIS 7.5 readme
You will most likely need an
Integrated Development Environment to
build web applications over IIS 7.5
Express. Microsoft WebMatrix provides
a simple and integrated user
experience for building both ASP.NET
and PHP websites using IIS 7.5
Express. You can use IIS 7.5 Express
with Visual Studio 2010 SP1 Beta to
build and test web applications
instead of the built-in ASP.NET
Development Web Server (also known as
Cassini). It is also possible to run
IIS 7.5 Express using the command
line.
I'd also check out the great blog post from Scott Guthrie
I have a project which I have upgraded to .Net 4.0, but when I try to access it, I retrieve the following error:
HTTP Error 404.2 - Not Found
The page you requested could not be displayed because of the settings for the list of ISAPI and CGI restrictions on web server.
ErrorCode: 0x800704ec
Handler PageHandlerFactory-ISAPI-4.0_32bit
Do I need to do something extra to the IIS 7 or APP pool, when converting an existing site to a .NET 4.0 site?
Also if I look at ISAPI both 32bit and 64bit of the .Net 4.0 is installed.
In IIS, enable .NET 4.
Here is image:
I take it you're running on IIS6 right now..
Open the IIS manager, and go to the Web Service Extensions area.. You'll be able to enable .NET 4 in there.. All new extensions are disabled by default :)
If you're running on IIS7, .NET might not have registered in IIS.. Then open up an admin command prompt and navigate to the .NET 4 framework folder (C:\Windows\Microsoft.NET\Framework\v4.{version}). If you're on a 64 bit machine go to the Framework64 folder instead of the Framework folder.
Then run aspnet_regiis -i in there
I had this same issue. Strangely, for me it would run in integrated mode but not in classic mode for .NET 4. After enabling the .NET 4 extensions via the Isapi and Cgi restrictions section in IIS 7, it then began working in both modes. The Isapi and Cgi restrictions section is located at the server level node in IIS manager. This option should not be confused with the Isapi Filters section at the site level.
I have a web-page application already created, but when I open it in visual studio 2008, it says there that:
ASP.NET 2.0 has not been registered on the Web Server. You need to
manually configure you Web server for ASP.NET 2.0 in order for your
site to run correctly.
I'm using asp.net 2.0, IIS7 and running on vista home premium.
How to register ASP.NET 2.0 to my web server(IIS7)?
ASP .NET 2.0:
C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -ir
ASP .NET 4.0:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -ir
Run Command Prompt as Administrator to avoid the ...requested operation requires elevation error
aspnet_regiis.exe should no longer be used with IIS7 to install ASP.NET
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
If anyone like me is still unable to register ASP.NET with IIS.
You just need to run these three commands one by one in command prompt
cd c:\windows\Microsoft.Net\Framework\v2.0.50727
after that, Run
aspnet_regiis.exe -i -enable
and Finally Reset IIS
iisreset
Hope it helps the person in need... cheers!
If you installed IIS after the .Net framework you can solve the porblem by re-installing the .Net framework. Part of its install detects whether IIS is present and updates IIS accordingly.
Open Control Panel
- Programs
- Turn Windows Features on or off
expand - Internet Information Services
expand - World Wide Web Services
expand - Application development Features
check - ASP.Net
Its advisable you check other feature to avoid future problem that might not give direct error messages
Please don't forget to mark this question as answered if it solves your problem for the purpose of others
The system I was working on is Windows Server 2008 Standard with IIS 7 (I guess that my experience will apply for all Windows systems of the same age).
Running
C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -ir
SEEMED to work, as
C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -lv
showed the .Net framework v4 registered with IIS.
But, running the same for .Net v2, namely
C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -ir
did NOT result in
C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -lv
showing the framework registered.
(And, for me, the installer for Kofax Capture Network Server was still missing ASP.NET.)
The solution was:
Open Server Manager
Go to Roles/Web Server (IIS)
Push Add Role Services
check ASP.NET under Application Development (and press Install)
After that, aspnet_regiis.exe -lv (either version) shows the framework registered.
(And the Kofax installer was also happy and worked.)
I got it resolved by doing Repir on .NET framework Extended, in Add/Remove program ;
Using win2008R2, .NET framework 4.0