VS2010 throws exception while opening project - iis

When I try opening a project I get an exception saying Web application is configured to use IIS.
Error : The Web Application Project EntityServices is configured to use IIS. To access local IIS Web sites, you must install the following IIS components:
IIS 6 Metabase and IIS 6 Configuration Compatibility
In addition, you must run Visual Studio in the context of an administrator account.
NOTE - I have already installed IIS 7. My box is a x64 bit Windows 7 box.

Go to Control Panel, Programs and Features, Turn Windows Features On or Off, and enable IIS 6 Metabase and IIS 6 Configuration Compatibility.

Have you installed IIS6 Metabase support? It is a seperate install from IIS7, although in the same area.
Turn Windows Features ON and OFF -> IIS Services-> Web Management Tools -> IIS Management Compatibility and check IIS Metabase and IIS 6 configuration Compatibility

This also happened to me when I had reconfigured the TCP Port on IIS to port 81. I was running TCPTrace, capturing traffic on port 80 and forwarding it to IIS at port 81.
After a reboot, I had to reconfigure IIS' TCP Port to 80 and the problem was resolved.

I got the same error the solution is that you should open with notepad (web project)it's csproj file and remove this tag
<UseIIS>True</UseIIS>

you need to turn on asp.net :
controlpanel- Turn Windows Features ON and OFF -> IIS Services-> www- > application Dewvelopment features check the asp.net on

In my case (Same error)
i solved my problem with following steps.
1-)open your project file with a text editor.
2-)find "USEIIS" tag and replace its value with "False". save and exit.
3-)reopen your project file with visual studio

Related

How can I tell if I have IIS Express or Full version installed?

I have two machines: Windows 10 Pro, and Windows 10 Home. I have enabled IIS on both of them. From both machines, going to IIS -> File -> About shows this dialog:
One might assume that I'm dealing with the full version of IIS simply due to the lack of the word "Express".
Is there any simple way to confirm if a machine has full or express installed?
IIS Express is normally installed into your 32-bit Program Files folder. So, to see if it's there you can try:
C:\>cd "\Program Files (x86)\IIS Express"
C:\Program Files (x86)\IIS Express>iisexpress /?
Full IIS is normally installed as a service called "World Wide Web Publishing Service" or "w3svc" for short. So, to see if it's there you can try:
C:\>net start w3svc
You opened IIS Manager to see such a dialog and IIS Manager is only part of full IIS, while IIS is part of Windows.
If you want to check that in code, then there are other ways such as checking Windows CBS data, or reading registry key.
IIS Express is completely another software, which is an MSI package to be installed either with Visual Studio or individually. To test its installation, you either check the Programs dialogue as the comment said, or query MSI data or registry keys.
If you have IIS manager installed, you have full IIS.
IIS Express is part of Visual Studio and appears in the Windows system tray when you run a web application/web site from within Visual Studio.

Setting up Coldfusion 10 with IIS - Unable to configure IIS connector

I'm trying to setup Coldfusion to work with IIS on my Windows 8 laptop. I have installed the ISAP filter and extensions along with the CGI extension but when I run the wsconfig and add the web server it then throws the error "Unable to configure IIS Connector". What can I try next? I've made sure they're all enabled in the IIS manager also.
The coldfusion 8 webserver configuration tool states that it is compatible until IIS 7. This is probably why it fails to add the handler mappings for IIS 8.
I found that by uninstalling coldfusion and re installing worked, that way in the setup it was able to identify what web servers were currently running and give me the option to configure coldfusion with IIS. Hope this helps someone else too

Migrating EPI5 from IIS6 to IIS7.5

Trying to move an EPI5 site from a server with IIS6 to a server with IIS7.5.
Having problems because of the configuration being set up for IIS6. Ive tried to follow instructions
http://world.episerver.com/en/Documentation/Items/Tech-Notes/EPiServer-CMS-5/EPiServer-CMS-5-R2-SP1/Changes-Between-IIS6-and-IIS7/#Changes in web.config
Does anyone have experience of following this guide or reconfiguring from IIS6 to IIS7.x?
What I've done in this situation (numerous times) is install a fresh (blank/demo) EPiServer 5 site on a server with IIS 7 and use those config files as a template when moving the real site from IIS 6 to IIS 7.
EPiServer 4 on Windows 2008 with IIS7 is not officially supported. You can get it to work though - one key is to run the application pool in Classic mode.
EDIT: You also need to turn on the pool's "32-bit" setting.

HTTP Error 404.3-Not Found in IIS 7.5

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.

404.2 Error after installing .net 4.0

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.

Resources