In trying to reconnect and reconfigure an existing project on a new machine, I find here (The Web Application Project [...] is configured to use IIS. The Web server [...] could not be found. ), based on the err msg I got on opening the project, that I need to go to IIS Manager (I performed the tasks prior to that in Russ C's answer, installing IIS 7.5 Express and rebooting). However, Russ goes on to write, "Next, go to your IIS Manager..." and that I haven't been able to do/find.
So I found this: http://technet.microsoft.com/en-us/library/cc770472(v=WS.10).aspx, where these instructions are given:
To open IIS Manager from the Start menu
Click Start, and then click Control Panel.
Do one of the following:
If you are using Windows Vista® or Windows Server® 2008, click System and Maintenance, and then click Administrative Tools.
If you are using Windows® 7 or Windows Server® 2008 R2, click System and Security, and then click Administrative Tools.
In the Administrative Tools window, double-click Internet Information Services (IIS) Manager.
To open IIS Manager from the Search box
Click Start.
In the Start Search box, type inetmgr and press ENTER.
As this is Windows 7, I tried System and Security | Administrative Tools, but there is no IIS Manager in the list. So I then tried the "inetmgr" route and that, too, failed (it opens a "Search Results" dialog with "No results matched you search" or similar wording).
So how can I locate the IIS Manager so that I can create anew or reattach the configurations the asp.net is failing to find?
UPDATE
I had to manually add support for asp.net 4 in IIS Manager for my project to quit whining. Why wouldn't this automatically be configured when installing asp.net 4?!? Anywho, for the benefit of future onreaders, here is what I had to add in its full color glory:
So here's how it looks at the end:
I don't know why v2 is needed and, if it is, why version 3 is not, but the important thing (for me, now) is having v4 support.
UPDATE 2
Right-click solution, there is a "Use IIS Express..." menu item. If you select that, you see:
...so maybe all that lying on my back, getting oil in my hair was unnecessary - just select this and all that behind-the-scenes stuff would have been taken care of automagically?
First of all, you need to check that the IIS is installed in your machine, for that you can go to:
Control Panel --> Add or Remove Programs --> Windows Features --> And Check if Internet Information Services is installed with at least the 'Web Administration Tools' Enabled and The 'World Wide Web Service'
If not, check it, and Press Accept to install it.
Once that is done, you need to go to Administrative Tools in Control Panel and the IIS Will be there. Or simply run inetmgr (after Win+R).
Edit:
You should have something like this:
You need to make sure the IIS Management Console is installed.
On a Windows Server 2016 I opened Server Manager from the start menu search. Then clicked Tools on the top right. Then found Internet Information Services (IIS) Manager
Or click win + r then type inetmgr then hit enter.
To open IIS Manager, click Start, type inetmgr in the Search Programs and Files box, and then press ENTER.
if the IIS Manager doesn't open that means you need to install it.
So, Follow the instruction at this link: https://learn.microsoft.com/en-us/iis/install/installing-iis-7/installing-iis-on-windows-vista-and-windows-7
Related
Normally when I asked to setup IIS (ASP.net) on Windows 2012, I do pretty much routinely doing this step below:
https://learn.microsoft.com/en-us/iis/get-started/whats-new-in-iis-8/installing-iis-8-on-windows-server-2012
List item
Open Server Manager.
Under Manage menu, select Add Roles and Features
Select "Role-based"
Select the appropriate server (local is selected by default)
Select Web Server (IIS)
.Net Framework 3.5/4.5 Feature
Customize your installation of IIS, or accept the default settings that
have already been selected for you, and then click Next
Click Install
I've encounter this following problem today:
(Missing Binding section when adding website)
Expected Result:
Anyone have idea how to fix it? I already reinstall couple of times without any success.
You are trying to add your Web Site under Default Web site , that is the reason you are unable to find the Binding Section : For Reference please check the below
Our company ships an MVC based product (targeting v4.5) which has stopped working on a customer site for what appear to be environmental issues - a build which worked with no problems once upon a time now gives a 403.14 - The Web server is configured to not list the contents of this directory.
.
What I think is happening...
The user accesses http://server/AppName
Because it's an MVC app, the default route (Reports/Index) should be used.
Instead IIS is looking for a default document...
... and, not finding one, it assumes the user wants to list the contents of the directory...
...which is not enabled so it throws a 403.14.
.
What I've tried so far...
Accessing the route directly.. results in 404 error. So I'm pretty
sure IIS doesn't realise it should use routing.
Use aspnet_regiis to register ASP.Net with IIS. This was done from the Framework64 folder since...
OS is 64 bit - Windows Server 2008 (Standard without Hyper-V)
IIS is 64 bit - though Enable 32-Bit Applications is true
Checked AppPool is targeting v4 of the framework - it is.
Changed AppPool mode to Classic - was pretty sure it should be integrated but was worth ruling it out. It is now back to Integrated
Confirmed RunAllManagedModulesForAllRequests is set to true in the web.config.
Checked permission conditions defined in <system.webServer> section of web.config are met - they are.
Created the simplest of MVC applications and deployed it - same problem.
Running the command shell as Administrator unregistered ASP.Net using aspnet_regiis -ua and re-registered using aspnet_regiis -enable -i. We hit a couple of permission problems - and the Temporary ASP.NET Files directory was missing but once they were address we were back to the same error.
Added a simple default.htm - when present, this is served in response to the http://server/AppName request.
I'm clean out of ideas and all google hits suggest some combination of the above - or enabling directory browsing (which I think is just a symptom rather than the root cause).
Also, not sure if it's relevant but the amount of configurable elements available for the application in IIS seems a bit below what I would have expected...
Have you Checked the user the application pool process is running under? I think Your site needs to run with permissions to execute the .net libraries and I've seen this just change for seemingly no reason (probably related to an overzealous update to the system).
You can try with the Enabling directory browsing .
assuming you are under Windows Server 2012 or Windows Server 2012 R2
On the taskbar, click Server Manager.
In Server Manager, click the Manage menu, and then click Add Roles
and Features.
In the Add Roles and Features wizard, click Next. Select the
installation type and click Next. Select the destination server and
click Next.
On the Server Roles page, expand Web Server (IIS), expand Web
Server, expand Common HTTP Features, and then select Directory
Browsing. Click Next.
On the Select features page, click Next. On the Confirm installation
selections page, click Install. On the Results page, click Close.
if you using the Windows PC try this in your command prompt as follows:
go to C:\Program Files\IIS Express
then press Enter:appcmd set config
/section:system.webServer/directoryBrowse /enabled
Maybe this is your case https://forums.iis.net/t/1157304.aspx
SQL Server Reporting Services creates a folder called Reports by
default if you install it on IIS. If you install SQL 2008 then
Reporting Services doesn't need to use IIS and instead will try to
reserve the URL with the HTTP.Sys service.
I believe this is the cause of the conflict you are seeing. What you
could try is changing the URL that Reporting Services uses via the SQL
Server Configuration Wizard.
Also I found that
Report Manager of SQL Server can use reports path http://<server name>/reports
Configure a Native Mode Report Server for Local Administration (SSRS)
I think the problem is IIS features that are not installed yet. I have met this kind of problem frequently in Windows Pro. Make sure to turn on every feature under Internet Information Service -> World Wide Services because by default IIS is configured to use WebForms. So there might be some features that not installed yet to use MVC, especially ISAPI filters. In my case, that was the solution. I hope it helps.
Something similar i encountered using VS 2017 & ASP.NET MVC.
Was working on the project for long with no problems at all but suddenly the routing started misbehaving & stopped working.
So I changed the Port in Project Properties Page & it started working.
I really don't know what is the relation between a port & MVC routing modules. Someone else can enlighten if at all this helps.
I had the same problem and I just created an application pool out of the Default Web Site in IIS and stoped the default web site. With that difference you will not have the application pool's path
I know it's been a long time since this question but i've had the same problema recently. I've tried every single configuration, just like #amcdermott did, but the only action that solve the problem was reinstalling .NET Framework.
My app was built under .NET Framework 4.5.2. The application server had the version 4.6.1 and 4.5.2 installed. So, i uninstalled all framework versions and installed the one that i needed.
Please, make sure that no other applications use superior versions of .NET Framework if you going to try this solution.
Here are some quote I find on Microsoft official site which I think may help:
For site administrators
This problem occurs because the Web site does not have the Directory Browsing feature enabled, and the default document is not configured. To resolve this problem, use one of the following methods:
Method 1: Enable the Directory Browsing feature in IIS (Recommended)
To resolve this problem, follow these steps:
Start IIS Manager. To do this, click Start, click Run, type inetmgr.exe, and then click OK.
In IIS Manager, expand server name, expand Web sites, and then click the website that you want to modify.
In the Features view, double-click Directory Browsing.
In the Actions pane, click Enable.
Method 2: Add a default document
To resolve this problem, follow these steps:
Start IIS Manager. To do this, click Start, click Run, type inetmgr.exe, and then click OK.
In IIS Manager, expand server name, expand Web sites, and then click the website that you want to modify.
In the Features view, double-click Default Document.
In the Actions pane, click Enable.
In the File Name box, type the name of the default document, and then click OK.
Method 3: Enable the Directory Browsing feature in IIS Express
Note This method is for the web developers who experience the issue when they use IIS Express.
To do this, follow these steps:
Open a command prompt, and then go to the IIS Express folder on your computer. For example, go to the following folder in a command prompt:
C:\Program Files\IIS Express
Type the following command, and then press Enter:
appcmd set config /section:directoryBrowse /enabled:true
I have recently installed Windows Server 2008 R2 Standard in Virtual Machine. I checked by doing localhost in browser as well as created a folder and tested with the link. It works fine. Now I wanted to add PHP extension in IIS7 which says I need to open IIS manager which I don't see either in "Administrative tool" of control panel or I can go from command prompt using "inetmgr".
Had the same problem and solved: In Server Manager (open from Administrative Tools), expand Roles, click on Web Server. Then scroll down to section 'Role Services' and click Add Role Service. From there you can click the Management Tools section. Only the Console is needed.
Just Write inetmgr in Run window it will showup..
or u need to add / install using Turn on Windows features in Add and Remove Programs
Complete Steps to Install and View IIS is here Link!!
Make sure that you installed Management Tools for IIS. It is server feature called something like "IIS Management Console"
Make sure that you have setup correct roles for Windows server. Also, please make sure that you have installed ,Management Console for your IIS installation.
Below is a useful tutorial given by Microsoft:
http://technet.microsoft.com/en-us/library/cc771209.aspx
Regards.
I had the same problem, http://localhost was working but I couldn't get to IIS Manager. Installed "IIS Management Console" and it works!
Im getting the following error in 32 bit machine classic applicationpool
Handler "PageHandlerFactory-ISAPI-4.0_32bit" has a bad module "IsapiModule" in its module list.
and in 64 bit machine
Handler "PageHandlerFactory-ISAPI-4.0_64bit" has a bad module "IsapiModule" in its module list.
If we install isapi and cgi in webservices then this error is not coming. Is there any possible way to allow my program without installiing those in classic applicationpool. and my next question is, how to recognize the isapi and cgi restrictions are installed. Is there any registry check exists or any other check.
Thanks in advance.
The above answer helped me but needed some additional steps, here is the full process I had to do.
Go to Control panel -> Programs and Features -> Turn Windows features on or off. Make sure you have the following selected:
Next, refresh IIS Manager. You should now see ISAPI and CGI restrictions on the root level of features of IIS, click Allow for both versions of .NET v4.0
did you enabled asp.net for IIS in programs and features ? check it in
programs and features -> Turn windows features on or off -> internet information service -> world wide web services -> application development features -> asp.net !
Just to add: if there is more than one framework on the machine, please install the framework in IIS by using 'aspnet_regiis -i', which is the .NET framework home directory (e.g. on my machine, is C:\Windows\Microsoft.NET\Framework\v4.0.30319)
I had this issue on a 2016 server. I found an answer that solved my problem in 1 minute after spending HOURS trying to resolve it on my own.
https://forums.iis.net/t/1149768.aspx
Steps from that page that worked:
1. Take IIS backup.
2. Open IIS
3. Click on server module node at the top of the left hand tree and choose "Modules".
4. Right click on DynamicCompressionModule and choose "Unlock"
5. Right click on StaticCompressionModule and choose "Unlock".
6. Open desired websites -> Open Modules.
7. Right click on DynamicCompressionModules and choose "remove".
8. Right click on StaticCompressionModule and choose "Remove".
9. Do IISRESET.
I have an ASP.NET website and when I press F5 it automatically attaches to the ASP.NET Development Server, how do I attach to IIS worker process instead when I press F5?
Debug->Attach To Process...
Select the aspnet_wp.exe process from the list.
If you're running IIS > version 5 the process will be w3wp.exe, and there will be one for every app pool (so if you don't know which app pool you're hitting, you'll need to attach to all of them).
open project properties, go to the web tab and choose the option for IIS.
That actually starts an instance of the app in IIS and attaches the debugger. If you only wanted to attach to an existing IIS instance, choose attach to process from the debug menu.
Debug -> Attach to Process from the VS menu.
In order to know to which w3wp.exe process to attach you can use the following command on a 2008 server
c:\%systemroot%\system32\inetsrv\appcmd list wp
While on windows 2003 it is
c:\%systemroot%\system32\cscript iisapp.vbs
For more info see IIS Application pool PID.
However if you have access to the task manager (taskmgr.exe) you can see there directly the name of the process along with the process ID, and in most cases the "user name" column of the process will be the same as the application pool name, (of course you have to set these columns to be visible in task manager in order to view the information).
But note that all of the methods will display only the processes that are currently running, which means that if your particular process has shut down due to idle time you have first to use the site in order to bring the process up in the list.
Also if the application is a "Web Garden" (which has more than one w3wp.exe) then even after attaching to the correct process there is still no guarantee that the breakpoints will be hit, since traffic to the site might be directed to another process.
Also note that if you attach to an application that runs in release mode, it will now instead run in debug mode, which means for example that there will be no timeout limitations (which might be a bit of a problem if you are actually trying to troubleshoot a timeout error).
If you want to attach to a remote process here is the best practice:
Make sure that the firewall is not blocking by opening the relevant ports or completely disabling it (just remember to turn it on again when done).
You should have a windows domain account with administrative privileges on the remote machine or have an account - with the same username and password as the local machine which is running VS - on the remote machine.
On the machine that has VS installed navigate to (Visual Studio Install path)\Microsoft Visual Studio (current version number)\Common7\IDE\Remote Debugger(Remote Machine Version), and copy and paste this folder to the remote machine or share this folder so that it is accessible from the remote machine.
On the remote machine log in as the same user as the local machine (see step 2) from there navigate to the copied or shared folder of step 3, and right click on "msvsmon.exe" and from the context menu select "Run As Administrator".
The Remote Monitor should start up and claim that it started a server usually by the name of (user)#(remote machine) or any other name.
In VS select Debug -> Attach To Process from the menu, leave the transport on "Default" and for the "Qualifier Name" enter the name from step 5.
If everything goes correctly this will bring up the list of processes on the remote machine.
Of course there is a lot more in this subject, and for debugging native code the process might be even simpler, but the steps I have listed here should work in every case.
For farther information you can take a look on http://www.codeproject.com/KB/aspnet/IISRemoteDebugging.aspx or on the MSDN, as well as many posts on this site.
Hope this will help.
Or you can use one of the Attach to IIS plugins to Visual Studio.
My preferred extension is VSCommands (for VS 2010 - 2012 or 2013, but not 2015 yet) or ReAttach (works in 2017).
go to the properties of the web application. Select the "Start Options" section, and change from "USe default web server" to "use custom server". Enter "http://localhost" in the base url.
(assumes VS 2008)