[Web] IIS 500 error failed request trace

%SystemDrive%\inetpub\logs\FailedReqLogFiles

5xx error

These errors are caused by the server failing to fulfill seemingly valid requests from visitors. Usually, you need the help of your server administrator to investigate them.

It's also important to always consider that the server chain is processing HTTP requests, so it may not be your server that returns the error.



500 Internal server errors

This error indicates that the server is experiencing an unexpected situation. This usually happens when an application request cannot be fulfilled due to an incorrect application configuration on the server.



501 not realized

This error indicates that the server does not support the HTTP method sent by the client. This is usually caused by an outdated server. This is a very rare bug that usually requires updating the web server.



502 bad gateway

This error is usually caused by a misconfigured proxy server. However, this issue can also occur when IP communication between backend computers is poor, client servers are overloaded, or firewalls are not functioning properly.

The first step in resolving the issue is to clear the client's cache. This action should result in the use of a different proxy to resolve the contents of the web server.



503 service is not available

This error occurs when the server is unable to process requests due to temporary overload or due to a temporary server shutdown for maintenance. The error indicates that the server will only be temporarily shut down. Other errors may be received in place of the 503.

If this issue persists, contact the server administrator.



504 gateway timeout

This error occurs when a server somewhere on the chain does not receive a timely response from a server further down the chain. The problem is caused entirely by slow communication between upstream computers.

To resolve this issue, contact your system administrator.



505 does not support the HTTP version

This error occurs when the server refuses to support the HTTP protocol specified by the client computer. This can be caused by the client computer not specifying the protocol correctly; For example, if an invalid version number is specified.



The 506 variant is also negotiated

This error indicates that the server is not configured correctly. Contact your system administrator to resolve this issue.



507 Insufficient storage space

This error indicates that the server is running out of available memory. This is most likely to occur when the requested application fails to allocate the system resources it needs to run.

To fix this, you may need to clear all unwanted files on the server's hard drive to free up more hard disk space, you may need to expand its memory, or you may just need to restart it.

For more information about this error message, contact your system administrator.



509 Exceeded bandwidth limit

This error occurs when the bandwidth limit imposed by the system administrator is reached. The only way to fix this is to wait until the limit resets in the next cycle.

For information on getting more bandwidth, consult your system administrator.



510 Not extended

This error occurs when the web server does not support extensions attached to HTTP requests.

To fix this, you may need to update your servers. For more information, consult your system administrator.