I'm not sure about asp.net as it has its own error handling routine and only
log status code and minor info in IIS.
Unlike ASP engine, which it logs more info in the IIS log file. I wrote this
chapter in the Log Parser 2.2 book.
Chap2 - Monitoring IIS
http://www.iis-resources.com/downloads/LPChap2.zip
from:
----
Under normal circumstances, these type of errors are often caused by coding
error in the server-side query, for example, |12|800a0009|
Subquery_out_of_range:_'arrayA(...)'. This error indicates that the arrayA
defined in in a server-side query is out of range. The format normally
starts with a pipe character followed by a line number, another pipe
separator, the error code, and finally one last pipe separator with an ASP
error message.
----
and here's the query for parsing ASP 500 related error.
---Ch02AspErrors.sql---
SELECT
Uri, Errorcode, ErrorMsg, LineNo, Total
USING STRCAT(cs-uri-stem, REPLACE_IF_NOT_NULL(cs-uri-query, STRCAT('?',
cs-uri-query))) AS QryStr,
TO_LOWERCASE(EXTRACT_TOKEN(QryStr, 0, '|')) AS Uri,
EXTRACT_TOKEN(cs-uri-query, 2, '|') AS ErrorCode,
EXTRACT_TOKEN(cs-uri-query, -1, '|') AS ErrorMsg,
EXTRACT_TOKEN(cs-uri-query, 1, '|') AS LineNo,
COUNT(*) AS Total
FROM %source%
WHERE
(cs-uri-stem LIKE '%.asp')
AND
(sc-status = 500)
GROUP BY Uri, ErrorCode, ErrorMsg, LineNo
ORDER BY Total DESC
---Ch02AspErrors.sql---
--
Regards,
Bernard Cheah
http://www.microsoft.com/iis/
http://www.iiswebcastseries.com/
http://www.msmvps.com/bernard/