When I debug/run my webs with IIS8 Express, IE starts and then just waits, nothing happens, white page with busy-mouse pointer.
This problem suddenly appeared (Windows 7 and Visual Studio 2010). I decided to reinstall my computer, now with Windows 8 and ONLY Visual Studio 2012 and I got the same problem!?
Running IIS Express (64 bit) with trace-level it works, and no error are reported, it does however not seem to work if I run the web using 32 bit (and from Visual Studio).
I have tested with a MVC4 project and ASP.NET Forms (Episerver) however the later has some issues running in 64bit (since it has dependencies that need to be 32bit).
My colleagues have the same code and for them IIS8 Express works, must be something with my installation?
I have tested reinstalling IIS8 Express (and my computer =)) no luck.
UPDATE:
I have tried running IIS 8 (not express) an it works.
For the MVC Project it seems to be signalr that "causes" the hang (removing RouteTable.Routes.MapHubs makes the site work).
I have tried creating a new MVC and ASP.NET Project and they both work.
So the problem seem to be located around my "old" Projects.
Running mu old projects on my laptop Everything works.
It is starting to drive me crazy
Any suggestions?
Jimmy,
IIS Express has had multiple bug reports with Microsoft. Personally, I'm working in IIS Express now without issue, but there are common complaints about IIS Express hanging after upgrades of VS 2010 SP1 or VS 2012.
That's not exactly your situation, but please read
http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/3917b164-2acf-4bec-8a0c-295aeaa5c198/
Problem Using IIS Express with Visual Studio 2010 SP1
Visual Studio 2010 iis express freezes when debugging multiple websites
iis express hangs
We've determined that you can use Cassini and IIS 8 at the moment. This may be a cop out, but you're right that it's project dependant (I've seen this before), and in your case you may be better off living with and moving on.
I had a similar issue running my asp.net MVC4 project on localhost under IIS express 8.0. Any time I hit Ctrl F5 to refresh a js file change every js file took 4 to 5 seconds to load. It turns out IIS Exp 8.0 is extremely slow when serving up js files. I ended up uninstalling IIS 8.0 and installing IIS express 7.5 and straight away the problem was fixed. Here are the steps I followed:
Uninstall IIS express 8.0
Delete the My Documents\IISExpress folder
Install IIS express 7.5 (Link to IIS Express 7.5 download)
IIS Express 8.0 seems to be installed with VS 2012 so if you had a new install or possibly a service pack update this might have upgraded your previous IIS express version.
Related
Running an MVC project in VS 2022, .NET Framework 4.8. When I run from VS, I get the below error. This was working as of a couple days ago, suddenly I get this error. I am inexperienced in all things IIS Express, how can I go about troubleshooting this exception? Google search has not turned up anything helpful to me. Any help is greatly appreciated!
EDIT: I created a new ASP.NET MVC application and was able to run it in IIS Express without issue. It is running under a different port (https://localhost:44327/) that the project I'm having issues with. I tried changing the port# on the problem project, but still get the same error.
In doing all of this, my applicationhost.config for IIS Express didn't change at all.
Uninstalling IIS Express in Visual Studio Installer, rebooting, and reinstalling IIS Express (along with all dependent components that had been removed) fixed my issue.
I have a TFS 2012 server running on Windows Server 2008 R2. For the past several months, whenever there are windows patches, the TFS 2012 server will not be functioning correctly. The error message is: Unrecognized attribute 'requestValidationMode' in web.config.
I checked my backup files for the web.config, the attribute was there a long time ago. I saw that 'requestValidtionMode' is for .NET runtime 4.0, not runtime 2.0. But I can see my ApplicationPool is always running under 2.0. If I changed the application pool to run under .NET runtime 4.0, the TFS application can't find many modules.
For the last couple times, I fixed the problem by upgrading my TFS server. But it is now at TFS 2012 Update 4 and I can't upgrade it anymore. I tried to run the repair of the installation, but it couldn't solve the problem.
Your help is very much appreciated.
I was experiencing the same error, and what happened to me is that some windows updates related to .Net framework 4.0 had failed, and it appears to have downgraded the AppPool in IIS to .Net 2.0 - which was having difficulties to process those attributes. Once I got the windows updates to install, and got the AppPool set back to 4.0, all the troubles went away.
I have an MVC Web API 2 application that I am running quite successfully locally within Visual Studio 2015 RC. I have also successfully published this application to an IIS 8.5 instance running on Windows Server 2012. I have installed .NET Framework 4.6 on this machine also.
The behaviour that I am getting when I try to navigate to the root of the site (http://localhost:81) is that I get a directory listing of the files in the root folder. Clearly I was expecting the routing config of the application to kick in an execute the home controller, but this is not happening.
I am a developer and it has been some time since I configured IIS, but I do remember that I had to do some fiddling with IIS (6?) to get the routing to work.
What am I missing?
Make sure your application pool is running in integrated mode and not classic.
I am developing an ASP.NET MVC 5 site targeting .NET 4.5.1 and for some reason I am struggling to deploy it on a Windows Server 2008 Standard edition server.
To be clear the site runs fine on my Windows 7 development machine and my Windows Server 2012 test environment but when I deploy it to the Windows Server 2008 in question I get this error:
At this point I tried all the advice about reinstalling ASP.NET and enabling runAllManagedModulesForAllRequests that I found in threads like this one ASP.NET MVC on IIS 7.5 but nothing would make it work.
Eventually I found that I could fix the problem by switching off the "Invoke only requests to ASP.NET applications or managed handlers" option for all managed modules in the application. What this did in essence was to make the following changes to the web.config file:
So my question is two-fold. Firstly, why is this change necessary to get the site to work? Secondly, am I safe to change the web.config permanently given that it will be installed on other servers as well, not all of which will be Windows Server 2008?
I recently upgraded my application from MVC 4/ EF 5 to MVC 5 / EF 6. I also upgraded to Visual Studio 2013 from VS 2012. Everything runs great on the IIS Express but when I publish to my production server via webDeploy, the site returns a 404 for all pages.
I am running IIS 8. There are no entries in my IIS log from today so this is not logging. I see no event alerts either.
I have done some research and performed the following:
Set the System.Web.MVC, System.Web.Routing and
System.Web.Abstractions to use a local copy when publishing. This
had no effect.
I restarted IIS.
I deleted all the files on the production server and re-published.
Thanks so much for your help!
Turns out that the problem had to do with Amazon eleastic ip - nothing wrong with the site or IIS.