Home > Http Error > Http Error 500.13

Http Error 500.13

I receive that error message after I see the "security alert" window that asks me if I want to Procedd. o 500.19 - Data for this file is configured improperly in the metabase. Generally in this scenario you would not see CPU and Memory issues as the ASP's are stuck in the queue waiting for external dependancies (database for example) to return data. I still have found no solution. this content

The tutorial is available on their site. Close Reply To This Thread Posting in the Tek-Tips forums is a member-only feature. Dev centers Windows Office Visual Studio Microsoft Azure More... Faking Http Status Codes in IIS/.net for testing share|improve this answer answered Feb 28 '13 at 3:11 Glenn Ferrie 6,79321752 add a comment| Your Answer draft saved draft discarded Sign

Among the MANY possibilites is failure to close your connections and destroy your objects. Join Now For immediate help use Live now! The content you requested has been removed. Covered by US Patent.

By default, this queue is limited to 3000 requests. do i need more memory (currently it is 1 GB)? IIS 6.0, ASP pages, HTTP Error 500.13 - Server error P: n/a rezapasha Hello, we have a website in ASP , the pages connected to .mdb access database by ODBC there Configure the following entries: Name: SessionViewSize Data Type: REG_DWORD Value data: 120 (decimal) 4.

The number of requests that can wait in the queue is controlled by the AspRequestQueueMax metabase property. Any help that could point me in the right direction would be greatly appreciated!

-j
Reply [email protected] 4640 Posts MVPModerator Re: Error 500.13 (Server too busy) with many sites Before I was averaging about 200 sites up (out of 340 total) and now with everything on one server I'm averaging about 60, occasionally peaking in the 80s. Each site is running in its own application pool.

Selenium Grid may help. Start Registry Editor. 2. I have gone through MS KB article 815372 and that didn't seem to have any effect. 0 LVL 26 Overall: Level 26 Exchange 25 Message Accepted Solution by:Vahik2006-01-03 http://support.microsoft.com/kb/823440 read 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.

o 404.0 - (None) – File or directory not found. http://knowledge.3essentials.com/web-hosting/article/471/ERROR-HTTP-Error-500.13-Server-error-Web-server-is-too-busy.html One other observation I made is that sometimes the non-working sites will start working a few minutes after first being tried. o 403.8 - Site access denied. You should migrate your application to utilize MySQL or MSSQL as the database back end.

when users get that error! news A 500.17 error indicates that the store could not be found. Jeff Have you Binged a solution before posting? This error code is specific to IIS 6.0.

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 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 Basically I was running out of non-interactive desktop heap even though I had a vast surplus of memory. have a peek at these guys I am using ASPCache for dataset caching so db access is minimal, my SQL server is nearly idle.

Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. Once i restart the server the page file useage useage drops to right around 600 MB. The error description might contain information such as an HRESULT and description.

By default, this queue is limited to 3000 requests.

Among other administrative tasks, IIS URL Authorization configures the Authorization Manager store by setting the AzStoreName metabase property. For more information about LDP.exe, in Help and Support Center for Windows Server 2003, click Tools, and then click Windows Support Tools. Internet Information Services (IIS) BUT only .asp pages on all domains make this error, all images or aspx or html pages work correctly. Internet Information Services (IIS) Honestly, MS Access (not to mention the use of ODBC) is more likely the cause: http://aspfaq.com/show.asp?id=2195 BUT only .asp pages on all domains make this error, all

I also have been having to mess with these settings again recently, because I again started to get more 500.13 errors as the size of my website applications grows. With an MSSQL or 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. It slowly climbs though in in some amount of time... check my blog If users encounter this error, select the Active Server Pages/Requests Queued performance counter check box.

We show this process by using the Exchange Admin Center. Now start pounding the web server - pretty soon you will get 503 Service Unavailable error back. If the queue fills up, but ultimately empties again, or if the queue remains partially filled but requests move through very quickly, there probably is not a problem, just a spike If more ASP requests arrive than there are threads available to execute them, ASP places the extra requests in a queue, where they wait until a thread becomes available.

Reply ganeshanekar 542 Posts Re: Error 500.13 (Server too busy) with many sites on one machine Apr 04, 2008 02:33 AM|ganeshanekar|LINK There are 4 main reasons in IIS 6 why the o 404.1 - Web site not accessible on the requested port. 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 o 403.6 - IP address rejected.

becouse after all users will recive the 500.13 error, but when it was on 3000 they recived after 8-9 hour and now will recive after 10-12 hour! 1) do you think For more information, see Microsoft Knowledge Base article 248013, Err Msg: HTTP Error 500-12 Application Restarting.Top of page500.13-Web Server Too BusyASP requests are executed by threads from a pool of threads 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. o 404.2 - Web service extension lockdown policy prevents this request.