I have very strange issue, when when I press the asp.net button click event page is keep loading(in chrome it shows uploading(43%)), after 5-6 minutes shows below
This Application works perfect in development server.(where I have only this application in the IIS) and in Production environment and get this error
This mostly happens with Postback events(uploading files & etc).
I have been searching for a solution for few days nothing success and the most of the articles are said check the DNS/Proxy server and increasing request timeout from web.config
But as I feel this is related to something else.
Is number of SQL database request affecting on this matter?
Related
I am beginner in web development. And I am working in an ASP.Net MVC 5 application and stuck with a very weird issue.
Issue:
Sometimes my web site just won't load in the browser. When I run in the local dev machine, website loads properly (localhost). But in LIVE the browser will keep on loading the website but nothing would load.
Also
After half an hour or so, website again kicks back in and starts opening properly.
Action I took:
Sometimes restarting the WebSite from IIS fixes the issue, BUT NOT ALL THE TIME. Sometimes even restarting did not fix the issue.
Also, I checked the Chrome Debugger, I do not see any error there (when the website was not loading).
I know something called ELMAH exists. Or some error logging in IIS. Can some one tell me how can I track this issue, in step by step process. Why my website will keep on trying to load in browser but will never load But after some time it loads. Is it IIS issue?
KINDLY NOTE: Once it starts loding fine, then even if I close the website and reopens it, It opens superfast like a flash. So the hiccups comes sometimes only.
I am willing to put more details, in this question. but I am not sure what to put. as far as IIS is concerned, all I know is how to restart and stop my website. that's it.
EDIT
Step 1: So, I searched event viewer as a whole in windows search and found something like below.
Edit 3
I checked the windows log, I do not see any issue related to my web app.
I know something called ELMAH exists.
Elmah is alogging framework. With just installing the NuGet package you already have an effective error logging mechanism in place. All unhandled exceptions will be logged with all the related information. It provides a page to visualize your logs and you can configure almost everything from security, to different back-end storages.
If you need a cloud base error logger with more advanced features you can use elmah.io.
Take a look at this post for a step by step guide on how to integrate elmah.
I am fairly new to IIS.
Hello, I am experiencing a very strange error once I publish my ASP.NET webpage onto IIS. The page functions fine while browsing, which makes several SQL calls for the menus and information on the site. This works fine both while debugging and when it goes live.
My problem is that after the user has made a couple of POSTs to update information in the live version, the page becomes unresponsive, or shows extremely high latency and returns nothing of the SQL requests that it was supposed to call. What could be causing this error?
The issue was that the server administrator forgot to give an application pool to the site. Hopefully this will help other people.
I got this very odd situation on my application which not all the time most of scripts I include in the <head> is not loaded, but some times they are. If I will refresh the page (either f5 or refresh button), sometimes it loads sometimes it's not. But if I enter the URL directly to the address bar, the page loads as expected. This happens not only in one page but in most pages but intermittently. My application is deployed on my local IIS version 5.1 (i'm using XP SP3). Mostly this situation happens if I rebuild my solution or I restart my IIS to refresh my IIS cache or to restart my Application. My guess is that my IIS don't have enough memory to process all the request at a time that it forgot to load all of the included scripts. Can anyone shed some light on where I should look to solve this kind of problem? At first it only happen on my machine, but lately I've noticed that it happens to our dev server also, I don't want it to go our test server or worse at the production server.
EDIT:
Here's how I determine the scripts that are not loaded.
I don't have any changes on any scripts, css what so ever that is directly seen on the client side. I only change a bit of code behind logic that wont change a bit on what the client user can see on UI. When I build it and test it on browser directly using the local IIS, my display has been corrupted, some scripts will not function and some page methods errors shown.
If I refresh the page, once or many times, the page will displace normally. As soon as I notice this, I already know that this is a cache problem.
I've used firefox and seen the same thing, so I've viewed the source. At first I didn't notice anything suspicious and everything seems normal until I clicked each include on the pages, css and scripts. Some of it are not read instead it returned an html containing The page cannot be displayed, There are too many people accessing the Web site at this time.
Once I noticed the return of some include scripts and css on the source which they return The page cannot be displayed, There are too many people accessing the Web site at this time. which is 403 error or Access forbidden, I wonder why access is forbidden, so I've done some research on my own and found out that IIS 5.1 on XP system only allows a maximum of 10 concurrent keep-alive connection, so if the page is not cached yet or part of the page, it requests to the IIS and there are times that the first request is not done and another request is being made which stuck up to 10 concurrent request, the IIS will return an 403 error to those last requests until, the first request is done and opens another connection.
For IIS5.1 in XP system, I can't do anything but to accept the fact that it only accepts 10 concurrent request, but for IIS6+, I found this article that it can handle up to 3,000 concurrent connections easily and could go more without limits depending on the Hardware resource of the machine, and some tweaks on the settings.
I have a website that I'm hosting on a public IP using IIS 7.0. (using c# asp.net 3.5)
I find that if I navigate to the webpage for the first time in a day. It loads endlessly and nothing shows up. Then when I re-press enter in the address bar, it loads right away and everything works fine.
From then on, when I got to the address again it loads quickly.
I don't think this is a compilation issue as all my code is pre-compiled.
Any ideas what might be causing this behavior?
Thanks!
Andrew
I had a similar problem which turned out to be caused by the IIS app pool recycling.
In my case, the website had outgrown its hosting package and as soon as it hit the arbitrary memory limit, the app pool was recycled and the application restarted, recompiling on the first page view.
You can check for this by adding a Global.asax and handling the Application_Start event. You could write logs to a database or send an email notification with whatever debug details you want.
I also handle Application_Error which offered up some useful info.
If you notice Application_Start happening several times a day, you may have a memory leak or similar issue.
I am having problems with my app running on IIS 7. The application is a mixture of classic ASP and ASP.NET MVC (don't ask how and why).
Anyway, the application is up and running except for some problems that I am experiencing. For example, I have a button on my page and when I click it, javascript is opening a popup which needs to contain .asp page. But that doesn't happen. I get the blank popup with my cursor on busy as it still loads. This is happening almost always to me in IE. In Firefox it is much better but sometimes the app jams there too.
If I close the opened, blank popup, and I want to move around the application, my buttons in menu (which are also .asp) doesn't load properly. For example, I have different buttons for different sections and when I move around they should change. When I restart the browser, only then everything works normal for some time, but the problem occurs again after a while.
I am very sure that it is not the problem in application itself, because it works properly on the machines of my colleagues without those problems. They have the same OS (Vista Professional) and we compared the settings in IIS and they match.
So I am very confused, and I really don't know how to solve the problem. I found a bunch of articles and blog posts about classic ASP and IIS7 but most of them are about enabling asp, which I already did.
So I am suspecting that something wrong with IIS, but I don't know what, tried to reinstall it, hoping for some improvement, but I had no luck.
If you need more details please ask.
Does anyone have any idea what should I try or do?
When debugging ASP.NET or ASP apart from the VS itself the most important tool you need is Fiddler (free tool from MS). This allows you to observe the http sessions the occur between your server and the client. This tool will give much greater visibility on what is actually happening underneath.
Next Step
So you now know that the problem is server side and the URL of the resource causing the problem. The next step is to debug the server side process by attaching to the w3wp.exe that is serving your site. If the resource specified by the URL is an ASP paged attach for script debugging or if its ASP.NET attach for Managed Code debugging. (Note for ASP debugging you will need to enable ASP server side debugging in the ASP settings in IIS manager).
You should place a break point on the first entry point of code for the resource. Now you can step through the code and discover where it is locking up.