Http Error 500.13
Web Platform Installer Get Help: Ask a Question in our Forums More Help Resources Blogs Forums Home IIS.NET Forums IIS 5 & IIS 6 Troubleshooting Error 500.13 (Server too busy) with many sites on one machine Error 500.13 (Server too busy) with many sites on one machine [Answered]RSS 10 replies Last post 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 9 Posts Error 500.13 (Server too busy) with many sites on one machine Sep 07, 2007 03:33 AM|jn00s|LINK
I am running 3 windows 2003 servers that host a combined total of 290 websites, which are all running the same classic ASP portal application off the same codebase (all websites on each server point to the same 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!
-j
Reply jeff@zina.co... 4640 Posts MVPModerator Re: Error 500.13 (Server too busy) with many sites on one machine Sep 07, 2007 08:15 AM|jeff@zina.com|LINK You may have found your limit for the number of sites per box. This varies depending on the load on the sites and the hardware, but you will hit this at some point on every system. More RAM can help, but eventually you need another box. Hosters ran
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Samples Retired content We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Deployment Deploying the Microsoft Dynamics NAV Web Server Components Troubleshooting the Microsoft Dynamics NAV Web Client Installation Troubleshooting the Microsoft Dynamics NAV Web Client Installation Troubleshooting: HTTP 500.13 - The request cannot https://forums.iis.net/p/1146213/1866717.aspx be processed because the amount of traffic exceeds the Web site's configured capacity Troubleshooting: HTTP 500.13 - The request cannot be processed because the amount of traffic exceeds the Web site's configured capacity Troubleshooting: HTTP 500.13 - The request cannot be processed because the amount of traffic exceeds the Web site's configured capacity Troubleshooting: Microsoft Dynamics NAV Web https://msdn.microsoft.com/en-us/library/jj651605(v=nav.90).aspx Client does have styles and images are missing Troubleshooting: Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel...' Troubleshooting: 401 - Unauthorized: Access is denied due to invalid credentials. Troubleshooting: HTTP Error 500 (or 500.21) - Internal Server Error Handler Troubleshooting: HTTP 500.13 - The request cannot be processed because the amount of traffic exceeds the Web site's configured capacity Troubleshooting: Server Error in '/' Application. Access Denied Troubleshooting: Internet Explorer cannot display the webpage Troubleshooting: A server error occurred and the content cannot be displayed Troubleshooting: A fatal error occurred. The connection to SQL server cannot be established Troubleshooting: Reports that are saved as Excel or Word files are blank Troubleshooting: Decreased Performance When Running Reports in the Microsoft Dynamics NAV Web Client TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Troubleshooting: HTTP 500.13 - The request cannot be processed because the amount of traffic exceeds the Web site's configured capaci
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search http://www.tek-tips.com/viewthread.cfm?qid=1473485 One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting http://stackoverflow.com/questions/15004717/anyway-to-simulate-server-busy-error-500-13-on-iis-7 Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To http error This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Microsoft: Internet Information Server Forum at Tek-Tips HomeForumsMIS/ITWeb ServersMicrosoft: Internet Information Server Forum Server busy error 500.13 - Please help! thread41-1473485 Forum Search FAQs Links MVPs Server busy error 500.13 - Please help! Server busy error 500.13 - Please help! southbeach (Programmer) (OP) 14 May http error 500.13 08 14:11 Last night a finally set SSL for remote users to use OWA in lieu of POP3/IMAP.This morning, lots of complaint since IIS keeps on crashing and giving following error:CODEThe page cannot be displayedThe request cannot be processed at this time. The amount of traffic exceeds the Web site's configured capacity.Please try the following:* Click the Refresh button, or try again later.* If this error persists, contact the Web site administrator to inform them that this error continues to occur for this URL address.HTTP Error 500.13 - Server error: Web server is too busy.Internet Information Services (IIS)Technical Information (for support personnel)* Go to Microsoft Product Support Services and perform a title search for the words HTTP and 500.* Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled Monitoring and Tuning Web Application Performance, Performance Monitoring and Scalability Tools, and About Custom Error Messages.I have been searching high and low for a root cause and cannot find anything that points to a solution.MS suggest to upgrade IIS from 4.0 or 5.0 to 6.0 where this does not happen.Well, I have 6.0 running on 2K3 R2 Standard edition.If
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Anyway to simulate server busy error 500.13 on iis 7? up vote 3 down vote favorite 1 Is there any way that I can return 500.13 error from IIS? I need the test the custom error page for 500.13 error. asp.net iis-7 custom-errors share|improve this question edited Nov 17 '15 at 18:23 pnuts 33.9k63769 asked Feb 21 '13 at 14:26 zforx 7021433 You need to do some load testing in Visual Studio –Raymund Feb 25 '13 at 20:31 add a comment| 5 Answers 5 active oldest votes up vote 2 down vote accepted +50 You can't raise a "server busy" error from the code. You can simulate the error codes as shown in the other answer but it will not allow you to determine if your custom error page will be shown correctly as the whole point to the "server busy" error is that code cannot be executed - so it is very safe assumption that IIS will do something different to raise this kind of error. But from what I can see the 500.13 error was thrown by ASP, not ASP.NET applications. Instead for ASP.NET applications you would see 503 Service Unavailable error. You can trigger 503 status code with the following: Open IIS Management Studio, go to Application Pools, open Advanced Settings for your app pool and change Queue Length to 10 (the minimum). In your ASP.NET application add a call to Thread.Sleep(50000). Now start pounding the web server - pretty soon you will get 503 Service Unavailable error back. share|improve this answer answered Feb 27 '13 at 16:43 Knaģis 13.4k13660 add a comment| up vote 4 down vote I don't believe IIS includes simulation of errors, however, there are benchmarking/stress testing applications out there that you can use. The only drawback to this is that you will actually have to put your (test?) server under actual stress until IIS "breaks." First, you should lower the IIS Application Pool size to the minimum available. I suggest you use Apache'