Out of Memory Errors - Errors.Log

  • Thread starter Thread starter Peter Crickman
  • Start date Start date
P

Peter Crickman

When I looked at the Errors.Log file in the MSAS program folder I see at
less one line for each nightly scan of the following text:

7::ln 10:Out of memory::gcasDtServ:ScheduleScans:Update::3/7/2005 2:00:57
AM:1.0.509

Is this a normal occurrence? Each nightly scan has completed successfully.

Thanks,
Peter
 
I know by default it is set to run scans at 2:00 AM. Is your PC Left on
overnight?
 
I think it is safe to say these are normal--I've seen them on most if not
all machines I have looked at.
 
Let me jump onto this thread . . . I don't do a scheduled
scan with MSAS, but have found that when I open things up
in the morning, MSAS appears to seize almost all of the
available CPU capability. I use Norton Systemworks and get
a CPU originated "red flag" almost every morning. This is
(as far as I am concerned), clearly the same problem.

Any ideas or is this just the way things are??

Bob
-----Original Message-----
When I looked at the Errors.Log file in the MSAS program folder I see at
less one line for each nightly scan of the following text:

7::ln 10:Out of
Click to expand...
memory::gcasDtServ:ScheduleScans:Update::3/7/2005 2:00:57
 
This isn't unique to your system, but neither is it a frequent
occurrence--the vast majority of users don't see this effect. I don't have
any suggestions that I know would make a difference in this behavior, but
the "usual suspects" may be worth trying, a repair install of Microsoft
Antispyware via start, control panel, add or remove programs, Microsoft
Antispyware, change, update. Perhaps disabling third-party services to see
whether there's a conflict--in general, other active-scanning
processes--antivirus, other Norton services--might be good to try to
eliminate from the startup mix to see what happens.
 
Back
Top