errors.log

  • Thread starter Thread starter Hagrinas Mivali
  • Start date Start date
H

Hagrinas Mivali

I noticed that this file had grown to over 35MB. What should I be doing with
this file? A lot of the messages keep repeating, such as:

13::ln 0:Type
mismatch::gcasDtServ:UpdateSchedule:LoadUpdateSchedule::6/24/2005 12:24:17
AM:XP:1.0.613
91::Object variable or With block variable not
set::gcasDtServ:modDataStore:GetData::6/24/2005 12:24:17 AM:XP:1.0.613
 
I too noticed it today. Mine is 60MB. With a lot of errors like:


91::ln 0:Object variable or With block variable not
set::gcasDtServ:modThreatData:Initialize::5/18/2005 9:14:36 AM:1.0.501


or


7::ln 10:Out of memory::gcasDtServ:ScheduleScans:Update::6/11/2005 2:00:04
AM:1.0.501
 
do you have a lot of user account on your computer? i
think this might cause the error.log to get larger or
have you frequently shutdown MSAS.
 
I have been running MAS for a couple of months, and
recently found that the errors.log was 3GB! (not 3MB)!.
I deleted the errors log.
Yesterday, I downloaded the new version, after removing
the previous version, and after running MAS once, I find
an error log of 3MB. IS this usual?
-----Original Message-----
I too noticed it today. Mine is 60MB. With a lot of errors like:


91::ln 0:Object variable or With block variable not
set::gcasDtServ:modThreatData:Initialize::5/18/2005 9:14:36 AM:1.0.501


or


7::ln 10:Out of
memory::gcasDtServ:ScheduleScans:Update::6/11/2005 2:00:04
AM:1.0.501
mismatch::gcasDtServ:UpdateSchedule:LoadUpdateSchedule::6/2
4/2005 12:24:17
 
This is a symptom which occurs on some machines and not others, with no
pattern that I can discern. It can go away for weeks at at time and recur.

I know of no fix other than deleting the file. I don't know whether it is
still ocurring with the .614 build.

In a situation where this issue might be critical--a server with a small
system partition, for example, I recommend removing the beta from the
machine.

--
 
Back
Top