This problem is beginning to annoy.
After my machine (Vista Ultimate) has been up for a while, running my ASP.NET web site project for debugging in VS2008 results in Internet Explorer "hanging". It doesn't seem to get past the network access stage, you know when it says "Loading web site", or "Waiting for".
I've attached a screenshot of IE. Note the status bar. It stays like that forever. I have to restart it and cross my fingers for it to work the next time. Invariably, it doesn't.
This happened with IE7 and IE8.
I am using the ASP.NET Web Development Server/Cassini. I have tried restarting this each time which seemed ot have got it, but then not so any more.
I'm up to date on patches.
ie screenshot http://img40.imageshack.us/img40/5446/iehanging.png
So thankfully Microsoft have finally released Security Essentials.
This meant I could de-install AVG (Free and paid-for versions) from my machine.
Hey presto, it works!
I would check the following
1) that your not starting IE against the webserver againt the wrong port, if your using the development IIS then it changes ports at times. That combined with you setting up the browser to launch against a the old port could create this problem.
2) Stop the local IIS and restart it (Again make sure your pointing towards the correct port)
3) Make sure you dont have any hung IE in task manager ( this happens to me sometimes ). Basiclly you have a IE in task manager that uses less then 1mb of ram and does not show on the taskbar, if thats the case kill them.
This doesn't sound, strictly speaking, like a hang. Can that tab/other tabs be navigated to other sites? Is your machine configured to use a proxy?
Is the request actually sent? Using Fiddler2 from www.fiddler2.com with the URL http://ipv4.fiddler:56125/ will show you, and help determine where in IE the problem might be.
I just had a similar problem that took about a week to unravel. Using AVG 9 Business Edition.
I'm on a Windows 7 machine with Visual Studio 2010 SP1, debugging ASP.NET sites running in IIS, with the same "hang" behavior you're seeing. Disabling LinkScanner and Online Shield in AVG fixed the problem.
Related
I have this weird issue on Visual Studio 2019 Community Edition. I am running an ASP.NET MVC 5 solution with only one project. The problem is every time I run it, sometimes one port is running fine, sometimes it is not.
Here is the screenshot of my IIS Express:
As you can see, it's only under one site and is showing multiple ports. I am not running any service, only website from ASP.NET MVC. It's erratic on my part since sometimes, one port is working, the other is not. So I need to relaunch multiple times my solution so that I can debug properly.
I already changed my port on my solution, but the first one is only reflecting on my edit, the other one, I cannot find a way how to edit the port or remove it totally.
I already figured it out. I just disabled the https port, and debugging my ASP.NET solution was smooth afterwards. To disable https, go to Solution explorer, select your project and press F4 on your keyboard, to see the settings:
If during debugging, you notice that your debugger shutsdown erratically make sure of the following as well:
Seperate your browser tab to your debugging browser tab
Since if you try to remove your debugging browser tab to other tabs, VS 2019 Community Edition debugging shutsdown unexpectedly. It happens on my Microsoft Edge browsers even on Chrome.
So seperate then and you are good to go
We have a reasonably large ASP.NET MVC app that I work on in Visual Studio 2012 on Win 8. I have a strange issue with slow page load times after recompilation. Usually, the actual build time is about 5 seconds, then the browser opens up and it takes 1-2 minutes to load the page.
Some points:
It loads slowly whether I change a view or recompile the project completely
This is not a performance issue, everything else works really well, there is enough RAM etc.
It happens only with IIS Express. When I switch to the default development server, it works fine.
All the other devs in my team use IIS Express, but they do not have this problem.
I tried to re-install IIS and to use v7.5 instead of v8 and recreated all config files. No luck.
I tried to disable all extensions, obviously it didn't affect load times too.
There is nothing abnormal in Task Manager
It's a virtual machine on my Macbook Pro, but again – this is not a performance problem.
What else can I try?
Solved by turning off Windows Defender Service. Everything is a hundred times faster now.
UPDATE: I failed to find a reason why Windows Defender is using lots of CPU power pretty much all the time. I tried to google it and it turns out that many people have a similar problem on Win 8 with no good solution.
If you really want to leave Defender on, you can add the project folder path as an exception, but it still will be slow-ish.
Hope it helps someone.
UPDATE 2: The above still holds true in Windows 10. Especially if you're running it in a virtual machine (I run it in Parallels on Mac). The overall speed increase, not only page refresh times, is very noticeable.
UPDATE 3: Apparently Windows Defender has a habit of silently turning itself back on again. So, be wary of that.
After viewing this question and answer above I found that Windows Defender Service was already turned off for me, however, I was running AVG. I disabled AVG and sure enough the lag went completely away!
So if Windows Defender Service is turned off for you and you are running some sort of system protection like AV try disabling that.
I'm developing an asp.net web site to work on mobile devices. Is going ok and works fine with android and iphone. I've no got around to testing it with blackberry in my balcberry curve. When i first tried everything looked good b ut then i noticed that some od the autopost back on dropdowns etc did not work. Some research time later i turn out out that by default that blackberries do not support this and that I need a Blackberr.browser file to allow that type of functionality to work. I following this link...
http://www.codeproject.com/KB/aspnet/BlackberryASPNET.aspx
After doing this my blakberry will not load the site at all, i just get connection timeouts. So i tried removing the blackberry.browser file, read loading the assembley in an attempt to get back to where is was, but still the site will not connect. I've refreshed iis, recycled app pools and even rebooted. I have a QA site on another box that the blackberry will connect to, but my development machine it does not like anymore:-(.
Any one got any ideas in what is going on?
Thanks for any help.
Richard
I have also suffered with the pain of developing (actually optimizing) websites for BlackBerry and Symbian, and I understand your suffering.
As you're using BlackBerry Curve, I suppose you're using a MDS server simulator on your development machine to let the BlackBerry Emulator connect to Internet.
Although I am not sure if you're even using a simulator.
I also have come across some simulators which just won't connect to the Internet no matter how hard you try with MDS server and all.
I hope you're not stuck with any issue related to the above said things mate.
Are you trying to connect your localhost with your BB?
I have a new IIS7 box running Windows Server 2008 Web Edition (x64), and I have set up an existing classic ASP site there. The site works fine and super speedy for the most part, but will randomly hang (about 1 out of 20 or so requests). By hanging, I mean I will click a page from the browser, and the browser (Crome on Mac) never responds -- it just continually loads until I finally get the following error after about 3 or so minutes:
Error 7 (net::ERR_TIMED_OUT): The operation timed out.
I'm pretty sure this is a Chrome-specific error, so I'm not too hung up on the actual error, but the cause of the time out. The site connects to a SQL 2005 server on the same network, but I'm pretty sure this isn't a SQL timeout, as that would happen within 30 seconds, and give me a specific error about SQL. I think this is an issue w/ my site, or the server.
Note that often after seeing this, I can simply stop the request and reload the page, and it will load just fine, super speedy again.
I'm not even sure where to begin troubleshooting this. I have to figure this out, otherwise this will mean a new server purchase down the drain.
Thanks in advance for any suggestions.
I've noticed a few more things about this problem. It'll happen more often after I've published files to the server (even static content like js or css files). It'll also happen occasionally on other sites running ASP.NET. Namely I've noticed the timeout on dotnetkicks.com which is also running IIS 7.5. Again, this only occurs in Chrome.
I've also tried uninstalling and re-installing Chrome but the problem continues. My next step is to try this from a couple different computers running Chrome outside my network.
UPDATE (April 29, 2011)
So I moved to Colorado a couple weeks ago and I haven't seen this problem occur even once since I moved. That leads me to conclude that 1.) my internet connection in Dallas was flaky and 2.) Chrome was less forgiving of a poor connection than other browsers. And of course, it basically rules out any possibility of there being a problem at the server's end.
I have a newly deployed mvc app on a win2008 server box.
I am trying to troubleshoot some very strange ie6 behaviour when over https. if a ie6 user connects to the webserver over https a simple post back or ajax call takes around 1 minute to complete, no errors are raised on the browser, it just sits there ticking away for about a minute, then completes as expected (both server and client as expected). the same post back or ajax call over http works in < 2 seconds.
There are no errors or events raised on the server, so i am flying blind here.
has anyone experienced this behaviour before, any ideas? with no errors or events to work with im not sure where to start. any other browser over https works fine, just ie6.
cheers
andrew
a quick follow up on this one. on further investigation the issue was only occurring on windows 2000 ie6 machines, xp and ie6 was ok. I guess from these results there must be something in the encryption/decryption framework on windows 2000 conflicting with the iis7 server.
I have managed to convince the windows 2000 ie6 users that its time to upgrade!
This brings up another question, when, if at all, do you think its acceptable to block certain versions of software from your web apps?
andrew