This problem started ocurring after I had installed Visual Studio 2011 beta.
Either I run my asp.net site with or without debugging, browser doesn't open anymore.
Web server starts working(asp.net development server and/or IIS Express) but no browser is opened automatically when I click the link [localhost:myport] from web server's context menu.
Any suggestions what the problem could be?
[UPDATE]
Also links in "MS Outlook" and "MS Word" stopped working.
[UPDATE2]
Fortunatelly the fix was found:
http://support.microsoft.com/kb/823301
Related
I'm having an issue with IIS Express (7.5) crashing whenever I launch a site in Web Matrix 2. The same sites launch fine from VS2010. The IIS icon appears in the tray, with the site listed as a running application, then disappears as soon as Chrome launches. Web Matrix serves the 'following site has stopped: xxxxxx' error.
I've uninstalled/reinstalled IIS Express and Web Matrix, have launched IIS from the command line, including error trace and it's all fine. Have also commented out the HttpLoggingModule key in the applicationhost.config file.
What else could be causing the problem?
Running webmatrix as administrator solved this, so figure it must be a security/permissions setting.
I am running VS2012 (Ultimate version 11.0.51106.01 Update 01) and do have a website project along with some console, WPF and WCF server projects. My normal debugging runs a non website project and rarely do I debug the website project.
Any debugging however, always starts IIS Express. How can I prevent that? The website project "Web" tab forces me to select some web server and "IIS Express" is currently selected, but I don't want it to start unless I'm debugging the website. Seems like this started happening after some recent VS2012 maintenance as I don't remember it happening before about a few weeks ago. Now getting old.
Is this a VS2012 bug that any debugging fires up IIS Express?
Anyway to not start it when I debug a WPF or console app?
So I've been working at this for about 2 days now and have essentially hit a dead end. I guess the first thing to know is, can IIS Express work in combination with Visual Studio 2010 and Windows 8?
I just got this new laptop in, with Windows 8 pre-installed. I installed Visual Studio 2010 Ultimate, SP1, and MVC 3. I had to enabled .NET Framework 4.0 myself...
I have a project that I transferred from my old computer (windows 7) to this computer. It was set up to run on IIS Express. So when I opened the project, VS2010 said that I was missing some components and asked if I wanted to install them--so it installed IIS Express for me. When I try to run my project, I get a "This page can't be displayed" page in IE. In fiddler, I get
- 302 HTTP localhost:16683 /
- 502 HTTP Tunnel to localhost:443
the SSL URL for the project is https://localhost:44300/
the URL for the project is http://localhost:16683/
If I go to IISExpress in my system tray and select the https link there, it opens the website up just fine. If I select the http link there, it get that "502 HTTP Tunnel to localhost:443" line in fiddler again... Why is it trying to tunnel to localhost:443???
Another thing to note is that I decided to create a test MVC 3 project from scratch to see what IIS Express would do. I set the project to run on IIS without enabling SSL. When I run the project is starts up just fine. When I click the logon link, it tries to redirect to an https link with port 44300...when it shouldn't be. I created a test project for the same purpose on my windows 7 machine, and the project did not do this.
The last thing to note is that after going to the https link for my initial project via the IIS Express tray icon, if I click the logon link for the test project, it now takes me to my initial project's https link... It's as if the projects are crossing over into each other...
The environment:
Clean (new) install of Windows 7 64bit.
Clean (new) install of Visual Studio 2010 Professional (10.0.30319.1).
Windows Update is up to date.
The problem:
I cannot start the debugger on Visual Studio 2010 (hit F5): 'Unable to start debugging on the web server. Unable to connect to the web server. Verify that the web server is running and that incomming HTTP requests are not blocked by a firewall.'
However, 'attach to process' (what I usually do) does work, but it is painfully slow to start (Visual Studio 'thinks' a lot of time before the debugging is actually enabled).
On the same hardware, running VS 2008 on good old Windows XP (32bits), this problem never happened.
Trying to debug a site running under the ASP.NET Development Server also fails: 'Unable to connect to ASP.NET Development Server.'.
There are plenty of web pages about these errors (many very outdated and does not apply to my environment), none of them worked for me.
Notes:
No matter if I run Visual Studio as Administrator or not. The problem is
the same.
The problem happens even when running a brand new blank IIS web site, either created as 'localhost/something' or 'sample.local'.
If I create a 'File System' web site (to try ASP.NET Development Server), when I hit F5, the server starts, but after a long wait Visual Studio says 'Unable to connect to ASP.NET Development Server.'
The 'hosts' file has an explicit 127.0.0.1 entry for 'localhost' and for 'sample.local'
It's the same problem either running .NET 2.0 or 4.0.
It's the same either configuring the application pool with or without 'Enable 32-Bit Applications' true or false.
It's the same either configuring the application pool is classic or integrated mode.
In a desperate attempt, I've added all the IIS 6.0 legacy 'features' stuff (not needed!) and doesn't helped at all.
I don't now what else I can try.
Thanks.
OMG!, I'm so stupid. The most oblivious thing was truly wrong. There was a wrong rule in the firewall. Therefore, even being in 'interactive mode' (as it is was always set), the connection was denied.
Hallo,
I am tryiing to migrate an application written with visual studio 2008 from windows XP IIs 6.0 To Windows 7 with IIS 7.5 and I have this problem:
Sometimes when I post the page, the server does not respond and after some minutes i receive e message "Internet explorer can not display a web page"
With IIS 6.0 the application works perfectly.
Please, can you help me ?
Mauro Servi
Try switching the AppPool to Classic .NET mode rather than integrated mode.
You can do this on the Application Pool's Basic Settings in IIS Manager