LOGPARSER #12: Troubleshoot who is causing your 500 errors?
This script is very interesting tracking down specific users causing errors in your IIS environment. Could be a physical person or a tool configured to run under a domain account.
One of my customers had a tool for checking site availability and it was pinging several pages constantly (SLA check). What they didn't know was that the tool was configured in the wrong way and was causing masses of 500 errors. Resolving them freed up server resources. Another benefit of doing some error cleaning is that you easily spot more severe problems or new error trends in the future if the log file is not cluttered. In my specific customers doing this operation removed about 100.000 of the 500 errors (about 1400/day).
We first run this script to count the 500 error per ASPX page and Domain User
count(*) as Times
This above script revealed that the bulk of all 500 errors was within 5 pages and from one specific user. To get the percentage of errors originated from this user we run the below script and it was near 97%
count(*) as Times,
propcount(*) as Percent
Customer now had plenty of data to back the decision to remove the tool or reconfigure. This is what it looked like after we removed the site pinging tool.
You can also run this script to get the all the 500 sc-substatus codes.
TO_STRING(To_timestamp(date, time), 'MMdd') AS Day,
SUM(c0) AS 5000,
SUM(c1) AS 50012,
SUM(c2) AS 50013,
SUM(c3) AS 50015,
SUM(c4) AS 50016,
SUM(c5) AS 50018,
SUM(c6) AS 50019,
SUM(c7) AS 500100
CASE sc-substatus WHEN 0 THEN 1 ELSE 0 END AS C0,
CASE sc-substatus WHEN 12 THEN 1 ELSE 0 END AS c1,
CASE sc-substatus WHEN 13 THEN 1 ELSE 0 END AS c2,
CASE sc-substatus WHEN 15 THEN 1 ELSE 0 END AS c3,
CASE sc-substatus WHEN 16 THEN 1 ELSE 0 END AS c4,
CASE sc-substatus WHEN 18 THEN 1 ELSE 0 END AS c5,
CASE sc-substatus WHEN 19 THEN 1 ELSE 0 END AS c6,
CASE sc-substatus WHEN 100 THEN 1 ELSE 0 END AS c7
5xx - Server Error
The server cannot complete the request because it encounters an error.
- 500 - Internal server error.
- 500.12 - Application is busy restarting on the Web server.
- 500.13 - Web server is too busy.
- 500.15 - Direct requests for Global.asa are not allowed.
- 500.16 – UNC authorization credentials incorrect. This error code is specific to IIS 6.0.
- 500.18 – URL authorization store cannot be opened. This error code is specific to IIS 6.0.
- 500.19 - Data for this file is configured improperly in the metabase.
- 500.100 - Internal ASP error.
- 501 - Header values specify a configuration that is not implemented.
- 502 - Web server received an invalid response while acting as a gateway or proxy.
- 502.1 - CGI application timeout.
- 502.2 - Error in CGI application.
- 503 - Service unavailable. This error code is specific to IIS 6.0.
- 504 - Gateway timeout.
- 505 - HTTP version not supported.