Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations sizbut on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Server busy error 500.13 - Please help!

Status
Not open for further replies.

southbeach

Programmer
Jan 22, 2008
879
US
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:
Code:
The page cannot be displayed
The 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 I do not come up with a solution for this, I will be forced to remove CA and go back to non-encrypted connection - which is not a good idea.

What say you?

Thank you all in advance for your help.
 
For those of you that may run into this problem, here is the solution


I opted for method 2 from this article. I also had to reverse the IP Restriction entry so, I would skip it all together unless you can figure out why access was denied to every one no matter where from nor the IP.

I found that the blackberry users were causing IIS to halt. As mentioned on the article, using form-based authentication may cause this - I did not want to get rid of this setting so I followed method 2 (minus the IP restriction step) and all is well now.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top