Http Error 500.13 - Server Too Busy
Contents |
Web Platform Installer Get Help: Ask a Question in our Forums More Help Resources Blogs Forums Home IIS.NET Forums IIS 5 & IIS 6
Http 500 Internal Server Error Iis 6
Troubleshooting Error 500.13 (Server too busy) with many sites on one module or isapi error occurred machine Error 500.13 (Server too busy) with many sites on one machine [Answered]RSS 10 replies Last post 500.19 error Jun 02, 2010 04:29 PM by jn00s ‹ Previous Thread|Next Thread › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Advanced Search Reply jn00s
Iis Status Codes
9 Posts Error 500.13 (Server too busy) with many sites on one machine Sep 07, 2007 03:33 AM|jn00s|LINK
Http Status 500 Internal Server Error
physical directory on that server). The problem is that once a server gets past around 70-80 websites running simultaneously, it can't seem to get any new sites running. The first 70-80 sites to get hit by requests will work fine and will continue to run indefinitely. But after a certain point no additional websites will initialize and work correctly. Instead they will perpetually return a 500.13 error. I've seen a couple of mentions on the net of people running into the same problem with lots of sites on a machine, but never any resolution. Any help that could point me in the right direction would be greatly appreciated!
8, 20064 0 0 0 Well, before doing anything like this, PLEASE ensure that you are working on a Demo box. I am working on Win 2003 which is my Development box and I can bear the impact of that error message. The first question is WHY would you like to Repro an http 500 error error message like this?I wanted to do this because I wanted to know which sepecific key
Http 503
to modify in my Metabase/Registry/IIS GUI so that I could get 500.13 (Server Too Busy) error. After that, I wanted to set a Custom Error page so that whenever that error message appears, the client gets the Custom Error. To check whether my Custom Error page is working, I needed to repro the issue. That is WHY!! :o) Apart from that, knowing which metabase key can cause https://forums.iis.net/p/1146213/1866717.aspx which issue never hurts!! The second question is HOW to repro it WITHOUT any kind of stress tool? The answer is - AspRequestQueueMax key in the metabase. Okay, I will not be documenting what exactly it does because we have tonnes of documentation for that. The one which I really like is this. Search for ASP Server Too Busy Error and you will get a decent documentation on not only what it does, but also some good practices! So, first of all we need https://blogs.msdn.microsoft.com/rahulso/2006/09/08/how-to-repro-server-too-busy-errors/ to create a read bad ASP page which will take a lot of time and could cause your IIS Server to hang (because w3wp.exe will be at 100%). Since I have two PCs it was not a concern for me. But remember, if you are working on just one PC, you need to modify the code accordingly with a smaller loop variable. Lets begin by creating a page called Bad_Code.asp. Open it with Notepad and paste the following code. <% Server.ScriptTimeout = 30000 Response.write(now()) str= "abc" for i= 1 to 100000 str = str & i next response.write(str)%> Before browsing this page, you will need to set the AspRequestQueueMax key to 1. By default it is 3000. We are telling HTTP.SYS to throw the 500.13 error as soon as the second request gets Queued, so that we don't need to stress IIS (our bad_code.asp page is good enough to do that ;o) !! Follow the steps to change the value and remember to create a backup of the Metabase before doing any changes (just in case!). 1. Open Internet Information Services, and right-click on the Root (local computer) node.2. Click on Properties, and ensure "Enable Direct Metabase Edit" is checked.3. Open C:\WinNT\System32\inetsrv\Metabase.xml in notepad. 4. Search for AspRequestQueueMax and set the value to 15. Save the file and Reset IIS. (Start -> Run -> IISReset and click OK) Now, to reproduce the issue go to the client machine and browse the page from an Internet Explorer window. (say - http://MACHINENAME/ServerBu
Postmaster Pre-sales FAQ Publishing Your Site Reseller Tips Search Engine Optimization Security Topics SSL and HTTPS Support: Getting Help Virtual Desktops Virtual Servers Website Design & Development Website Errors http://knowledge.3essentials.com/web-hosting/article/471/ERROR-HTTP-Error-500.13-Server-error-Web-server-is-too-busy.html Knowledge Essentials - 3Essentials Hosting ERROR: HTTP Error 500.13 - Server error: Web server is too busy Article ID:471 Back to Search Question: I'm receiving "HTTP Error 500.13 - Server error: Web server is too busy" intermittently on some of my ASP pages. Answer: If you're using MS Access as a database back end, then this is likely the cause of your problem. While MS Access http 500 databases CAN work in this type of solution, they are the least preferred method. There is no "MS Access engine" running on the server that is designed to manage multiple concurrent requests for the same resource (record/file), you simply have ASP with a driver with instructions on how to access the MDB file and file format (I'm simplifying, but for comparison sake). With an MSSQL or 500 internal server MySQL database backend, you have a database engine/server that is designed to manage concurrent connections and conflicts through caching and other forms of process/thread management. If you google/yahoo this error and MS Access (or .mdb), you'll find a lot of discussion on this topic... and although there are some differening points of view, but the vast majority agree with the descriptionprovided above, and the solution is to move to an appropriate database backend capable of managing concurrent connections in a more efficient manner. You should migrate your application to utilize MySQL or MSSQL as the database back end. Most of our hosting plans already include MySQL databases and some include MSSQL. Check your LIMITS in the control panel, or submit a request to Support if you need clarification or are interested in upgrading to a plan that includes MySQL or MSSQL databases. Note that this is a different condition than what is described here: ERROR: Server Error in '/' Application - Server Too Busy Downloads Associated With This Article No downloads are currently associated with this article. © 2001 - 2016 3Essentials Inc. Terms Of Service | Privacy Policy | Copyright Policy | Affiliates