IIS 5 & IIS 6
Possible Memory Leak
Last post May 31, 2008 12:46 AM by steve schofield
May 29, 2008 03:35 PM|bkbristlin|LINK
Hello, I am working with Windows Server 2003 Standard Edition w\ SP2. I have this running at over 40 sites. We have an app that runs within IIS that handles paging on our Cisco VoIP phone system. I am unfamialiar with IIS 6.0 so I am having trouble tracking
down the errors within this program. Currently I have been using IIS Debugging Tools 1.1 x86 on 11 of my servers. 4 of them are looking for Crashes within the IIS pool, 4 are looking for Crashes\Memory Leaks withing the processes associated with it, and 3
are looking for a Crashes within the processes themselves. I get very little from these dumps except for the w3wp.exe process exiting. I know the App has problems becuase I see them everyday when working in it. I just can't find a way to home in on these.
One problem says exception out of memory although the server has plenty of memory. From research I saw that this is becsue of .NET 1.1.4322. This app is dependant on this version of .NET. Another problem is the system will randomly say the page cannot be displayed.
Hopefully someone has some ideas of how I can track a problem with something like this. I am open to suggestions.
IPT Systems Specialist
May 29, 2008 10:37 PM|steve schofield|LINK
It sounds like you headed in the right direction. This is probably too detailed of an issue for the forums, I'd suggest you capture a complete dump file then contact Microsoft PSS for assistance.
Windows Server MVP - IIS
Log archival solution
Install, Configure, Forget
May 30, 2008 03:36 PM|bkbristlin|LINK
This is the direction I was going with my first post. Problem is that I'm not sure how to track down the error when it comes up in IE. None of the processes I am monitoring seem to be right even though I can definitely see errors when working with the program.
I'm gonna keep pluggin' away at it. Sooner or later I will get it.
May 31, 2008 12:46 AM|steve schofield|LINK
I usually open task manager and add virtual memory column. Anything with a lot of Virtual memory (say 400 - 500 MB) and the physical memory is like 5 MB, that would be a good contender for a memory leak.