Menu
I have a gridview on my homepage with a view and an edit link that use query strings to display table data in read-only and editable pages, respectively. I get no error messages from my code, it's simple enough that it doesn't seem to be missing anything, but when I try to debug or view in browser, I get the permanent pinwheel on my status bar and the message "waiting for localhost". What am I missing? Does anyone out there have some experience with this particular issue? I'm using C# and ASP.NET in visual studios with sql server 2008.
364
Check firewall for blocked ports, change dynamic ports of application to some fixed port. Changes in Firewall settings may be a leading cause.
It is triggered if the firewall wrongly blocks your server or you're using the wrong port. The localhost error can also happen if your Apache web server or Chrome browser is not configured correctly.
If you are using a fast internet connection, the actual loading time of a webpage is about 2 secs, however due to resource shortage or ping issues as a result of which you may receive a Waiting for local host message. We would suggest you to use Internet Explorer and check if it helps.
Re: localhost keeps on loading, how to fix it? You should try using the Netstat button to see if both ports 80 & 443 are free. Its also possible that an OS error is preventing it from running. Check the Windows Event Viewer, Applications and System logs.
My trainer came up with a brilliant solution, he shut down VS 2010 and restarted it. Problem solved.
163
Almost sounds like the database connection is going off neverland.
If your timeout on the connection and/or command is set pretty high, like 300 (which is 5 minutes) then it would appear to just hang forever if it is unable to make that connection.
The first thing I'd try is to set the connection timeout to something reasonable like 15 seconds in the web.config.
Then I'd run it again.
Assuming you get a connection failure, I'd use another tool to try and connect to the database using the settings in your web.config.
27
Does this only happen on debug (ie F5)?
If that is the case, my guess is that you are hitting a breakpoint?
If you hit a break point, the browser appears to be dead... but in fact VS is waiting on you to respond...
24
I found that creating a new app pool, then assigning the (already created) web site to it resolved this.
45
I shut down iis, stopped debugging the site in visual studio, and restarted with F5 ;-)
30
Try to not use localhost but your local ip address.
39
I had the same thing happen; If you are on a VPN connection, you may need to change your web.config file to use your database IP instead of the name (if you have DNS issues with VPN). This won't help the OP but someone else may find this useful.
27
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
