Windows 2003 Memory Leak

[Willem Zonnevijlle]

Can anyone advise me on how to find a memory leak in Win2003 X64.
Is the best way to compare poolmon screendumps by hand or should I use
memsnap en analyze the logs with memsnap -a <logfile>

[Pegasus \(MVP\)]

"Willem Zonnevijlle" <Willem [email protected]> wrote in
message news:[email protected]...
> Can anyone advise me on how to find a memory leak in Win2003 X64.
> Is the best way to compare poolmon screendumps by hand or should I use
> memsnap en analyze the logs with memsnap -a <logfile>

In many cases it is sufficient to observe the Memory Usage
column in the Task Scheduler. With a leaky application the
number keeps creeping up.

[Willem Zonnevijlle]

In my case it's not enough. Let me explain what is the problem.
I administer 3 fileservers running Win2003 R2 x64 with 2 dualcore AMD
Opteron Processors and 8GB memory. Main storage is on a Equalogic iSCSI
device connected with MS iSCSI initiator over a dedicated 1GB network. The
average number of users connected to each fileserver is about 1100 Part of
their userprofile is redirected ro their homedir. The roaming part of their
profile is stored on a separate partition. Network load is minimal: on the
iscsi network ranging from 0,1% to 2% max. On the regular network from 2-9%
max. Backups are made over the network with Legato Networker and the
antivirus solution is Symantec Antivirus 10.x in a managed environment.
At irregular intervals one of the fileservers freezes and the users loose
their connection to their profile and home directories although the machine
iresponds to pings. On the console the windows explorer is frozen (doesn't
respond).
But, from a command window which is always open I can browse all partitions
and drives. Nothing is logged in the eventlogs and the only solution is to
reboot the machine by using the powerswitch.
My first suspicion was a memory leak, but I can't find it, nor by using
memsnap, nor by using poolmon. So, I am wondering whether I'm using the right
method to discover a leak.
The problem is very annoying

[SF]

Hi all

I have the same problem happen in my IBM server as Willem mentioned. I even
do not to know how to use poolmon to trace the memory leak. Also I can only
find the poolmon.exe tool in the system diskettes but without the other
required files pooltag.txt, msvcp70.dll, msdis130.dll, msvcr70.dll in order
to run the poolmon.

Would you help me where I can find those files and how to use the poolmon to
trace the memory leak problem.

My configuration is 1G ram with an IBM x206m server, runing as a web server
only. I almost removed all the applicaiton just leave the postgres sql, Java,
and Tomcat applcation in running, but the problem is still happened.

Thanks
SF

[Niklas]

I had the same problem, It was caused by Symantec endpont protection
Look for a patch at symantec.

/Niklas

In my case it's not enough. Let me explain what is the problem.
I administer 3 fileservers running Win2003 R2 x64 with 2 dualcore AMD
Opteron Processors and 8GB memory. Main storage is on a Equalogic iSCSI
device connected with MS iSCSI initiator over a dedicated 1GB network. The
average number of users connected to each fileserver is about 1100 Part of
their userprofile is redirected ro their homedir. The roaming part of their
profile is stored on a separate partition. Network load is minimal: on the
iscsi network ranging from 0,1% to 2% max. On the regular network from 2-9%
max. Backups are made over the network with Legato Networker and the
antivirus solution is Symantec Antivirus 10.x in a managed environment.
At irregular intervals one of the fileservers freezes and the users loose
their connection to their profile and home directories although the machine
iresponds to pings. On the console the windows explorer is frozen (doesn't
respond).
But, from a command window which is always open I can browse all partitions
and drives. Nothing is logged in the eventlogs and the only solution is to
reboot the machine by using the powerswitch.
My first suspicion was a memory leak, but I can't find it, nor by using
memsnap, nor by using poolmon. So, I am wondering whether I'm using the right
method to discover a leak.
The problem is very annoying