IIS 5 & IIS 6
IIS 500 0 1396
Last post Jul 06, 2012 01:31 PM by terridonahue
Jun 12, 2012 04:06 PM|abo|LINK
Can you help me with this error.
What means above message. Is this a server to busy error because of the 13 or another error.
2012-06-10 23:47:55 W3SVC1 192.168.45.69 GET /smartsite.asp id=1005161 80 - 10.82.10.42 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.5.21022;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729)
500 0 1396
Jun 12, 2012 06:25 PM|terridonahue|LINK
If you browse to that page locally on the server, what is the error that is returned?
Jun 12, 2012 07:26 PM|peterviola|LINK
You could also check the Application and System event viewer to see if anything is being logged. If the site has a web.config turn off Custom Errors.
Disable 'Show Friendly Errors' in your browser.
Try enabling Failed Request Tracing and see if that offers any additional clues:
Jun 14, 2012 11:19 AM|abo|LINK
Well the problem is that it's was an hot issue so i have to do an IISreset immedialy.
It worked fine thats why i'm thinking about a 500 error where the server is to busy.
Only i would like to have more information.
But app and sys log doesn't show me errors where i can work on.
Jun 14, 2012 02:48 PM|terridonahue|LINK
Jun 16, 2012 06:39 PM|abo|LINK
Thanks very much for beeing so specific. Now i know how to check or debug this errors and what it means.
@everybody, thanks very much for your response.
Jun 16, 2012 06:41 PM|abo|LINK
Peter thanks very much for the failed request learning guide and for the show friendly error options i can turn out.
This gives me more to start with!
Jun 30, 2012 08:40 AM|abo|LINK
I have the same errors again. When i look i see 500 0 errors on a time the website wasn't down. I see 304 0 calls at times the website was down. And the other way around. I would write a powershell scripts that check on this errors, but then i would say
if 200 then good, otherwise not good.
But with different requests i cannot do that.
Friendly errors show a application error and Failed Request Tracing isn't there in IIS6.
The debugger i have tried on the application pool but it brings me standard debug output. Maybe i go for COM/IIS logging.
Jun 30, 2012 04:10 PM|terridonahue|LINK
You can use logparser to gather additional information from the IIS Logs related to your errors. Here is a link that has additional information about this product:
http://technet.microsoft.com/en-us/scriptcenter/dd919274.aspx. If you have friendly errors turned off in your browser, what error is returned at the time of the failure? Is there anything
in the Event Viewer that might point to root cause of the failure? Make sure that you are accounting for the fact that the logs are in GMT. A 500 error in the log corresponds to the site being unavailable. A 304 entry in the logs shows that the page was served
Jul 03, 2012 08:46 AM|abo|LINK
Got the errors, they come since two weeks. Is logparser still the right tool. Do you know which error in the IIS log displays this message?
I want to know that to trigger it in my powershell script
The World Wide Web Publishing Service service terminated unexpectedly. It has done this 18 time(s).
The IIS Admin Service service terminated unexpectedly. It has done this 18 time(s).
Jul 03, 2012 08:48 PM|terridonahue|LINK
Yes, logparser can help you located the cause of the error. You can use this query against your log file that had the failure to see if it will provide additional information related to the error:
SELECT EXTRACT_TOKEN(FullUri, 0, '|') AS Uri,
EXTRACT_TOKEN(cs-uri-query, -1, '|') AS ErrorMsg,
EXTRACT_TOKEN(cs-uri-query, 1, '|') AS LineNo,
COUNT(*) AS Total
USING STRCAT( cs-uri-stem,
REPLACE_IF_NOT_NULL(cs-uri-query, STRCAT('?', cs-uri-query))
) AS FullUri
FROM #IISW3C# (this is the location of the log you want to parse)
WHERE (sc-status = 500) AND (cs-uri-stem LIKE '%.aspx')
GROUP BY Uri, ErrorMsg, LineNo
ORDER BY Total DESC
Jul 03, 2012 08:53 PM|abo|LINK
I kow SQL and i know that i can query WMI, but i didn't know logparser and didn't know i can query the log.
Thanks very much. This is very helpfull, even in future monitoring of IIS and webservices.
Jul 06, 2012 07:27 AM|abo|LINK
Thanks for the start ahead, i got all that i want now and i can develop mij own queries. :-).
I see that IIS 6 log is 2 hours behind, is this because it keeps logging in memory?
Last question ;-)
Jul 06, 2012 01:31 PM|terridonahue|LINK