|
Home > Archive > IIS Server > September 2005 > Help interpreting DebugDiag reports
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Help interpreting DebugDiag reports
|
|
| Sam Chrisp 2005-09-27, 2:52 am |
| Hi,
Below is a description of issues we have been experiencing with our
application running on IIS 6.
We have installed DebugDiag and done full userdumps of all the IIS
processes.
The Crash/Hang report is here: http://202.93.169.84/reports/CrashHang.html
And the Memory Pressure report is here:
http://202.93.169.84/MemoryPressure.html
The worker process which has been crashing is 'FooBAR' with a PID of 5012.
We can see some obvious areas of concern:
- Total reserved memory is 2.87GB, but only 148MB of that is committed.
- ADO components appear to be holding onto large amounts of memory
But cannot draw any proper conclusions from the reports.
Any comments or advice anyone can offer in interpreting these reports and
identifying the issue(s) would be appreciated.
==== Background
We have a web-based application which is predominantly ASP but with some
ASP.NET in areas.
SQL Server 2000 is used as the database backend.
For a few months now we have had issues with the IIS worker process which is
serving the application 'crashing'. Other worker processes running
webservices related to the application do not crash.
For a while this was occuring roughly once a week.
After a recent update to our application (which was quite large, and covered
many areas) it is now occuring on average once a day, and up to 3 times a
day.
Symptoms:
1. The system will slow down and take 3-4 minutes to load a page.
2. Page timeouts may occur.
3. VBScript compilation 'Out of Memory' errors will occur when trying to
load up any ASP page.
4. The worker process may crash and terminate (ref. IIS Errors below).
These issues have always been 'fixed' by an IIS reset.
==== Environment
Webserver config
Processor: 4 * 2.8GHz Xeons
Memory: 4GB DDR
Disk: 36GB U320 SCSI
Software: Windows 2003 w/SP1, .NET Framework 1.1, IIS 6 in Native mode.
Database server config
Shared SQL Instance
Processor: 4 * 2.8GHz Xeons
Memory: 4GB DDR
Disk: Fibre SAN
Software: Windows 2003 w/SP1, SQL Server 2000 w/SP3a.
===== IIS Errors
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1011
Date: 8/06/2005
Time: 4:08:27 p.m.
User: N/A
Computer: LNL11T01
Description:
A process serving application pool 'Foobar' suffered a fatal communication
error with the World Wide Web Publishing Service. The process id was '3508'.
The data field contains the error number.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 6d 00 07 80 m..?
===== Reports
http://202.93.169.84/reports/CrashHang.html
http://202.93.169.84/MemoryPressure.html
| |
| Wei-Dong XU [MSFT] 2005-09-27, 7:58 am |
| Hi Sam,
I have added my reply at your another post in the this newsgroup with the
same title.
From: "Sam Chrisp" <schrisp@ldsau.com>
Subject: Help interpreting DebugDiag reports
Date: Tue, 27 Sep 2005 17:15:26 +1000
Newsgroups: microsoft.public.inetserver.iis
Please feel free to let me know at that thread if you have any further
question on this matter.
Best Regards,
Wei-Dong XU
Microsoft Product Support Services
This posting is provided "AS IS" with no warranties, and confers no rights.
It is my pleasure to be of assistance.
|
|
|
|
|