lsass.exe

30 May 2006 12:37 PM

Gary

We recently moved to requiring Common Access Cards to access our web server.
Since the implementation the lsass.exe process starts around 7mb of memory
usage on a fresh reboot but climbs to around 90mb after 24 hours and 200mb
after 48-72 hours. Needless to say it's killing our server after a couple of
days. Any ideas?

Running Windows 2003 SP1/IIS6. Thanks.

30 May 2006 2:24 PM

Roger Abell [MVP]

many memory leak scenarios known
not sure if any of these apply to Sp1, but worth a check first
http://tinyurl.com/l9czq

Show quoteHide quote

"Gary" <G***@discussions.microsoft.com> wrote in message
news:E1D59CF1-2429-456A-9989-507CDBE5074B@microsoft.com...
> We recently moved to requiring Common Access Cards to access our web
> server.
> Since the implementation the lsass.exe process starts around 7mb of memory
> usage on a fresh reboot but climbs to around 90mb after 24 hours and 200mb
> after 48-72 hours. Needless to say it's killing our server after a couple
> of
> days. Any ideas?
>
> Running Windows 2003 SP1/IIS6. Thanks.

30 May 2006 2:52 PM

Gary

Thanks Roger.

Show quoteHide quote

"Roger Abell [MVP]" wrote:

> many memory leak scenarios known
> not sure if any of these apply to Sp1, but worth a check first
> http://tinyurl.com/l9czq
>
> "Gary" <G***@discussions.microsoft.com> wrote in message
> news:E1D59CF1-2429-456A-9989-507CDBE5074B@microsoft.com...
> > We recently moved to requiring Common Access Cards to access our web
> > server.
> > Since the implementation the lsass.exe process starts around 7mb of memory
> > usage on a fresh reboot but climbs to around 90mb after 24 hours and 200mb
> > after 48-72 hours. Needless to say it's killing our server after a couple
> > of
> > days. Any ideas?
> >
> > Running Windows 2003 SP1/IIS6. Thanks.
>
>
>