IIS Web Transactions By Site Test

Compare the value of this measure across the web sites to identify the web site that is receiving more number of requests.

Compare the value of this measure across the web sites to identify the web site that is receiving more number of errors.

Compare the value of this measure across the web sites to determine which web site is slow in responding to the requests.

This measure is a good indicator of current load on each web site.

The detailed diagnosis of this measure reveals the following details for each web site:

• IP address of the client
• Name, IP address and port of the server
• Site Name
• Amount of data sent and received in KB
• Time taken to process the requests in seconds
• Host number
• Protocol version
• Method type
• Http status
• Win32 status
• Time stamp at which the log was created
• Date and time of local host
• User Agent
• Cookie
• Referrer
• Protocol SubStatus

Ideally, a high value is desired for this measure.

This measure is a good indicator of current load on each website.

The detailed diagnosis of this measure reveals the following details for each web site:

• IP address of the client
• Name, IP address and port of the server
• Site Name
• Amount of data sent and received in KB
• Time taken to process the requests in seconds
• Host number
• Protocol version
• Method type
• Http status
• Win32 status
• Time stamp at which the log was created
• Date and time of local host
• User Agent
• Cookie
• Referrer
• Protocol SubStatus

A site returns 300 series response codes when it redirects requests to other pages. Redirection is performed for various reasons. For example, when the client browser may have to request a different page on the server or to repeat the request by using a proxy server.

These codes helps the client to ensure that a redirection to a different resource or URL should take place to complete the requests and access the desired resource.

Use the detailed diagnosis of the Total redirection requests measure to find out the IP address of the client, the name, IP address and port of the server, the site same, the amount of data sent and received, the time taken to process the requests, the protocol version, the type of menthod used, the date and time of local host, and more.

When a request is permanently moved from the site, it returns the HTTP status code 301. This action is performed when the requested site has been permanently moved to a new URL.

A 302 Found message is an HTTP response status code indicating that the requested resource has been temporarily moved to a different URL. Since the location or current redirection directive might be changed in the future, a client that receives a 302 response code should continue to use the original URL for future requests.

The HTTP 304 response code indicates that there is no need to retransmit the requested resources. It is an implicit redirection to a cached resource. This means that the requested resource is already in the cache and the resource has not been modified since it was cached. Therefore, the client can use the cached copy of the resource, instead of downloading it from the server. This happens when the request method is safe, like a GET or a HEAD request, or when the request is conditional and uses a If-None-Match or a If-Modified-Since header.

Use the detailed diagnosis of the Not modified measure to find out the IP address of the client, the name, IP address and port of the server, the site same, the amount of data sent and received, the time taken to process the requests, the protocol version, the type of menthod used, the date and time of local host, and more.

The HTTP 307 Temporary Redirect status response code indicates that the resource requested has been temporarily moved to the URL given by the Location headers.

The 4xx HTTP status codes indicate that an error occurred and the client browser appears to be at fault. For example, the client browser may have requested a page that does not exist or may not have provided valid authentication information.

The web site returns the HTTP 400 code when the request could not be understood by the server due to malformed syntax. This implies that the client should not repeat the request without modifications.

The login failure error occurs when the logon attempt is unsuccessful, probably because of a user name or password that is not valid.

Ideally, the value of this measure should be zero.

The HTTP 401.2 status code indicates a problem in the authentication configuration settings on the server.

Ideally, the value of this measure should be zero.

Authorization errors will be reported when the requests are not authenticated by ACL on resource or filter or ISAPI/CGI application.

Ideally, the value of this measure should be zero.

The website encounters forbidden errors for various reasons, for example, when the website receives too many requests from the same client.

Ideally, the value of this measure should be zero.

The 404 error is reported when the server has not found anything matching the Request-URL. This error code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.

The 405 Method Not Allowed response code indicates that the method specified in the Request-Line is known by the origin server but is not supported by the target resource. To avoid this, administrators should include the response MUST an Allow header containing a list of valid methods for the requested resource.

Ideally, the value of this measure should be zero.

The HTTP 406 (Not Acceptable client) error code indicates that the server cannot produce a response matching the list of acceptable values defined in the request's proactive content negotiation headers, and that the server is unwilling to supply a default representation.

Ideally, the value of this measure should be zero.

The 408 Request Timeout error indicates that the request sent to the website server (e.g. a request to load a web page) took longer than the website's server was prepared to wait. In other words, your connection with the website "timed out".

Ideally, the value of this measure should be zero.

The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended.

Ideally, the value of this measure should be zero.

The server error messages are reported for a wide variety of server-side errors. For more information on the errors, you can refer event viewer logs and find out the reason why the errors occur.

Ideally, the value of this measure should be zero.

The 500.0 error occurs when the ISAPIModule module is missing from the modules list for the website. ISAPI filters (modules) are libraries loaded by the IIS web server. Every incoming request and outgoing response passes through the filters, and they are free to perform any handling or translation they wish. They can be used for authentication, content transformation, logging, compression, and myriads of other uses.

Ideally, the value of this measure should be zero.

The website reports 500.11 HTTP error code when an application on the server is shutting down, and thus the received request cannot be processed by the website.

Ideally, the value of this measure should be zero.

This error occurs when you tried to load an ASP page while IIS server was in the process of restarting the application. This error message will disappear when you refresh the page.

Ideally, the value of this measure should be zero.

Ideally, the value of this measure should be zero.

These errors occur when a dynamic-link library (DLL) that is required by the Microsoft Data Access Components is not registered. To alleviate this kind of errors, administrators should register the DLL before the errors cause serious impacts on the key transactions.