500.13

If the page has been deleted from the server or it is not currently available you can try to get an achived copy. If you used a link from a search engine, you might be able to get some information by using the "cached" option.

You can also try viewing the site or page from an archive such as the WaybackMachine.

Most archives and cached versions only retains the site text. Graphics and other media objects are linked to the orignal site and may or may not be available.

You can try to access the site again at a later time when the server issue has been corrected.

You might notify the webmaster about the issue. Include the error number and the address (URL) where the error occurred along with any other relevant details.

Many sites use an email address in the form webmaster@sitename.com where you replace sitename.com with the web sites address (don't include a www). Keep in mind with the amount of spam, they may use a different address and/or it might get ignored. Check the websites' contact information to get reliable contact information.

Web server is too busy. The request is not processed because the server is too busy to accept any new incoming requests. Typically, this HTTP status code means that the number of incoming concurrent requests exceeds the number that the IIS 7.0 Web application can process. This problem may occur because the performance configuration settings are set too low, the hardware is insufficient, or a bottleneck occurs in the IIS 7.0 Web application. A common troubleshooting method is to generate a memory dump file of the IIS 7.0 processes when the error is occurring and then to debug the memory dump file.

Check out what others say about this issue and review or add your own comments and solutions!