MS Error Log (Is this normal)

  • Thread starter Thread starter PeterToland
  • Start date Start date
P

PeterToland

Hi Can anybody help explain what these are please:

They are in the MS Antispy error log and it appears to
have found errors everyday since i installed MS Antispy
on the 17/06/05,Are these just standard errors or do i
need to adjust my settings somehow ?


7::ln 10:Out of
memory::gcasDtServ:ScheduleScans:Update::17/06/2005
02:30:39:1.0.509

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::17/06/2005
02:48:03:1.0.509

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::17/06/2005
03:32:01:1.0.509

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::17/06/2005
06:55:08:1.0.509

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::17/06/2005
18:18:09:1.0.509

91::Object variable or With block variable not
set::Updates:LatestRulesetVersionID::30::18/06/2005
14:59:48

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::18/06/2005
18:32:20:1.0.509

5::Invalid procedure call or
argument::gcasDtServ:modData:InitializeFriendlyFilesData::
19/06/2005 00:32:37:1.0.509

91::ln 0:Object variable or With block variable not
set::gcasDtServ:FriendlyFiles:ExistsSysData::19/06/2005
00:32:37:1.0.509

7::ln 10:Out of
memory::gcasDtServ:ScheduleScans:Update::20/06/2005
02:00:25:1.0.509

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::20/06/2005
02:25:53:1.0.509

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::20/06/2005
05:29:37:1.0.509

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::20/06/2005
07:11:20:1.0.509

7::ln 10:Out of
memory::gcasDtServ:ScheduleScans:Update::21/06/2005
02:00:17:1.0.509

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::21/06/2005
03:56:00:1.0.509

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::21/06/2005
20:59:24:1.0.509

7::ln 10:Out of
memory::gcasDtServ:ScheduleScans:Update::22/06/2005
02:00:18:1.0.509

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::22/06/2005
03:49:52:1.0.509

7::ln 10:Out of
memory::gcasDtServ:ScheduleScans:Update::23/06/2005
02:00:24:1.0.509

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::23/06/2005
08:02:03:1.0.509

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::23/06/2005
21:06:54:1.0.509

7::ln 10:Out of
memory::gcasDtServ:ScheduleScans:Update::24/06/2005
02:00:21:XP:1.0.613

0::ln 0:Software updates could not contact update server,
IsConnectedToInternet returned false (Error:
1)::gcasSWUpdater:modMain:Main::24/06/2005
21:00:57:XP:1.0.613

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::24/06/2005
21:31:30:XP:1.0.613

7::ln 10:Out of
memory::gcasDtServ:ScheduleScans:Update::25/06/2005
02:00:30:XP:1.0.613

7::ln 10:Out of
memory::gcasDtServ:ScheduleScans:Update::26/06/2005
02:00:13:XP:1.0.613

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::26/06/2005
18:15:45:XP:1.0.613

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::27/06/2005
07:11:50:XP:1.0.613

7::ln 10:Out of
memory::gcasDtServ:ScheduleScans:Update::28/06/2005
02:00:02:XP:1.0.613

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::28/06/2005
08:14:23:XP:1.0.613

7::ln 10:Out of
memory::gcasDtServ:ScheduleScans:Update::29/06/2005
02:00:03:XP:1.0.614

91::Object variable or With block variable not
set::Updates:LatestRulesetVersionID::30::30/06/2005
14:20:51

-2147417851::ln 0:Method '~' of object '~'
failed::gcasServ:modMain:AlertNotice::01/07/2005
00:54:29:XP:1.0.614

7::ln 10:Out of
memory::gcasDtServ:ScheduleScans:Update::01/07/2005
02:00:19:XP:1.0.614

91::Object variable or With block variable not
set::Updates:LatestRulesetVersionID::30::01/07/2005
17:12:27

7::ln 10:Out of
memory::gcasDtServ:ScheduleScans:Update::02/07/2005
02:00:27:XP:1.0.614

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::02/07/2005
21:46:59:XP:1.0.614



Thanks Pete
 
PeterToland said:
Hi Can anybody help explain what these are please:

They are in the MS Antispy error log and it appears to
have found errors everyday since i installed MS Antispy
on the 17/06/05,Are these just standard errors or do i
need to adjust my settings somehow ?
Click to expand...

Hi Peter,

Since no one else has responded to your post I thought I would give
you some general observations from someone with no special knowledge
or expertise.<bEg>

You're running on XP and I must say, your log is much more
interesting than mine on w2k pro.<g>

I've sorted your log by error number and listed it below.

Error 438 appears to occur on exit every time you run the program.
This would seem to be a trivial error that doesn't effect program
operation and has probably been assigned a low priority.

Error 7 is likely a memory allocation error associated with a large
percentage of 20,000,000 users trying to check for updates before
running a scheduled scan at the default time of 2 am and swamping
Microsoft's server. Try changing your scheduled scan to ... oh, say
1:37 am. There should be less competion at that time.<g>

Error 91...3 of the 4 errors you've seen seem to be associated with
updating the "LatestRulesetVersion". It would be interesting to
follow that closely and see if it occurs on the first run after a
definitions update.

The remaining error 91 was related to the one error 5 you recorded
while initializing friendly files data. Hopefully a one off error
due to a mismatch of definitions or perhaps corrupted definitions???

Error 0. One occurance while not connected to the internet. I would
consider that one self explanitory.

That beings us to the error -2147417851 which I wouldn't imagine is
a valid error number<g>, but may be a serious bug as it's associated
with an alert.

Bare in mind that this is a *beta* and we expect to find bugs.

Below is your sorted and reformatted log:

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:17/06/2005 02:48:03:1.0.509

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:17/06/2005 03:32:01:1.0.509

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:17/06/2005 06:55:08:1.0.509

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:17/06/2005 18:18:09:1.0.509

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:18/06/2005 18:32:20:1.0.509

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:20/06/2005 02:25:53:1.0.509

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:20/06/2005 05:29:37:1.0.509

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:20/06/2005 07:11:20:1.0.509

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:21/06/2005 03:56:00:1.0.509

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:21/06/2005 20:59:24:1.0.509

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:22/06/2005 03:49:52:1.0.509

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:23/06/2005 08:02:03:1.0.509

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:23/06/2005 21:06:54:1.0.509

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:24/06/2005 21:31:30:XP:1.0.613

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:26/06/2005 18:15:45:XP:1.0.613

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:27/06/2005 07:11:50:XP:1.0.613

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:28/06/2005 08:14:23:XP:1.0.613

438::ln 0:Object doesn't support this property or method:
:gcasDtServ:modMain:ShutDown:
:02/07/2005 21:46:59:XP:1.0.614

91::Object variable or With block variable not
set:
:Updates:LatestRulesetVersionID::30:
:18/06/2005 14:59:48

91::Object variable or With block variable not
set:
:Updates:LatestRulesetVersionID::30:
:30/06/2005 14:20:51

91::Object variable or With block variable not
set:
:Updates:LatestRulesetVersionID::30:
:01/07/2005 17:12:27

7::ln 10:Out of memory:
:gcasDtServ:ScheduleScans:Update:
:17/06/2005 02:30:39:1.0.509

7::ln 10:Out of memory:
:gcasDtServ:ScheduleScans:Update:
:20/06/2005 02:00:25:1.0.509

7::ln 10:Out of memory:
:gcasDtServ:ScheduleScans:Update:
:21/06/2005 02:00:17:1.0.509

7::ln 10:Out of memory:
:gcasDtServ:ScheduleScans:Update:
:22/06/2005 02:00:18:1.0.509

7::ln 10:Out of memory:
:gcasDtServ:ScheduleScans:Update:
:23/06/2005 02:00:24:1.0.509

7::ln 10:Out of memory:
:gcasDtServ:ScheduleScans:Update:
:24/06/2005 02:00:21:XP:1.0.613

7::ln 10:Out of memory:
:gcasDtServ:ScheduleScans:Update:
:25/06/2005 02:00:30:XP:1.0.613

7::ln 10:Out of memory:
:gcasDtServ:ScheduleScans:Update:
:26/06/2005 02:00:13:XP:1.0.613

7::ln 10:Out of memory:
:gcasDtServ:ScheduleScans:Update:
:28/06/2005 02:00:02:XP:1.0.613

7::ln 10:Out of memory:
:gcasDtServ:ScheduleScans:Update:
:29/06/2005 02:00:03:XP:1.0.614

7::ln 10:Out of memory:
:gcasDtServ:ScheduleScans:Update:
:02/07/2005 02:00:27:XP:1.0.614

7::ln 10:Out of memory:
:gcasDtServ:ScheduleScans:Update:
:01/07/2005 02:00:19:XP:1.0.614

5::Invalid procedure call or argument:
:gcasDtServ:modData:InitializeFriendlyFilesData:
:19/06/2005 00:32:37:1.0.509

91::ln 0:Object variable or With block variable not
set:
:gcasDtServ:FriendlyFiles:ExistsSysData:
:19/06/2005 00:32:37:1.0.509

0::ln 0:Software updates could not contact update server,
IsConnectedToInternet returned false (Error: 1):
:gcasSWUpdater:modMain:Main:
:24/06/2005 21:00:57:XP:1.0.613

-2147417851::ln 0:Method '~' of object '~'
failed::gcasServ:modMain:AlertNotice:
:01/07/2005 00:54:29:XP:1.0.614

Thanks Peter and keep us updated.

Bob Vanderveen
 
Thanks Bob

Its very kind of you to go through my error list i will
try changing the time of the updates. My Internet
connection is always active so even though the no
connection message was obvious i wasnt sure what caused
it in my case .

I appreciate its a beta test and im happy to be involved
in the testing i was just suprised it had found a error
everyday since i installed it but like you say alot of
these could be due to the scheduled scan time so i will
change that.

Checking it again today its got more entries and like you
say this error comes up whenever i close MS Antispy or
shut down my pc

438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::03/07/2005
07:14:08:XP:1.0.614
438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::03/07/2005
22:31:48:XP:1.0.614
438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::03/07/2005
22:32:28:XP:1.0.614

I just shut it down a couple of times to test it and it
did enter them as a error

Thanks for the advise i will keep a eye on it for any
other errors but as long as everything is working normal
besides for the errors im happy to carry on using it.


All the Best

P.Toland
 
FWIW, fresh install of v.614 and the only entries in the error log are :

7::ln 10:Out of memory::gcasDtServ:ScheduleScans:Update::7/5/2005
10:52:02 AM:XP:1.0.614
438::ln 0:Object doesn't support this property or
method::gcasDtServ:modMain:ShutDown::7/5/2005 2:20:05 PM:XP:1.0.614


Steve Wechsler (akaMowGreen)
MS-MVP 2003-2005
===============
*-343-* FDNY
Never Forgotten
===============
 
You've done a much more comprehensive job of analysis than I could have!

I would recommend ignoring this log except in the case that it grows very
large very fast, in which case deleting it is a good idea. In early days of
the beta there were some installation issues we were able to solve using the
content of the log file, but recently it hasn't really been useful for
problem solving.

--
 
I would not ignore the error.log growth problem. It was slowing down my
system.

After updating my definitions for Windows AntiSpyware my system slowed down,
and rebooting didn't fix it. Looking for the problem I noticed my Antivirus
program (avast) was constantly scanning the error.log file. Only exiting
Windows AntiSpyware brought my system back to normal (or stopping my virus
scanner).

After the update on 5th November 2005 to the definitions, I keep getting
error 91 in the log file. Trying to re-download the definitions doesn't work,
I keep getting 'Most recent spyware definitions installed'.

Will there be some kind of check in the future for corrupt definition
files?? Or some option to re-download, or purge (delete
gcThreatAuditScanData.gcd and gcThreatAuditThreatData.gcd???), without
re-installing the program?? Thanks.

error.log starts with:
-2147467259::Method '~' of object '~'
failed::gcasDtServ:modData:InitializeAgentDataStoreData::11/5/2005 1:04:33
PM::1.0.615
Then:
91::Object variable or With block variable not
set::gcasDtServ:modAgentsDataStore:GetData::11/5/2005 1:04:33 PM::1.0.615
And:
91::ln 0:Object variable or With block variable not
set::gcasDtServ:AgentDataStore:GetDataStoreCollection::11/5/2005 1:04:39
PM::1.0.615
And:
91::ln 0:Object variable or With block variable not
set::gcasDtServ:modAgentsDataStore:SaveData::11/5/2005 1:04:40 PM::1.0.615
And continues with this....
 
Isaac - the growth of the error log was capped with the release of the 6xx
versions of the program, I believe--certainly it is capped in .615.

However, of course, there may remain users whose log file grew to the
maximum bound for their filesystem before the growth was capped.

If you re-read what I said, I was recommending ignoring the content of the
file itself, and recommending NOT ignoring the rapid growth issue--which you
can solve by simply deleting the file.

That message was written a few weeks before the release of the .6xx builds
in which this issue was finally fixed.

So--just delete the log file. Don't worry about its content, and don't
worry about it growing out of control again. And expect that the file will
in all likelyhood go away completely by the end of the year with the release
of Windows Defender - beta2.

--
 
Ok, thanks Bill. I am using version 1.0.615. What is the size limit on the
file? And deleting the file it comes back, and starts growing again. (ps. I
am using the Real-time Protection feature). I will simply re-install the
program.

Just wanted to mention: The only thing that annoys me about the error.log
file growth is that gcasDtServ.exe and gcasServ.exe cause a peak in cpu usage
to about 30% every ~7 seconds. With real-time AV protection on top of that,
it's a spike at 100% cpu usage every ~7 seconds. Log file is now 1.98mb.
(Using 1.8GHz x64 CPU). Anyway, thanks for your time :)
 
That CPU spike would worry me too.

Here's what I'd do, just to see whether it helps:

1) uninstall Microsoft Antispyware beta1.
2) delete \program files\microsoft antispyware and all subfolders
You will lose access to any quarantined items, history, and customized
settings.
3) reinstall Microsoft Antispyware.

I can't recall just what the cap should be--20k or so is what I think I
recall.

I think what you are seeing is definitely not normal--so I'd try the steps
above (2) is the key one--and see whether a new install resolves both
issues.

If it doesn't, I think I'd back off and look again at beta2, which we expect
to be available before the end of the year.

--
 
Back
Top