MSAS throwing errors.log file every 2 hours

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I've been using MS AntiSpyware without problems for at least 8 months now,
have upgraded twice without problems, but since November 21st @ 12:05 AM my
version 615 has been acting up. Every 11 seconds or so, the "gcasDtServ"
task will spike, and the "errors.log" file gets another 80 entries in it.
These 80 errors are all the same:

91::ln 0:Object variable or With block variable not
set::gcasDtServ:modAgentsDataStore:SaveData::2005-11-27 3:41:56
PM:2000:1.0.701

These 80 errors follow one of the following errors (every 11 seconds):

91::ln 0:Object variable or With block variable not
set::gcasDtServ:modAgentsDataStore:IsDirty::2005-11-27 3:41:55
PM:2000:1.0.701

This huge rate of error reporting causes the "errors.log" file to grow to
about 9.5 MB every 2 hours, at which point it gets deleted, and replaced with
a new errors.log file. This has been going on for a week now, and I've just
noticed it.

To try to cure it, I've upgraded MSAS from version 615, to the latest
version 701 (and rebooted) but it's still throwing the same errors, at the
same rate. Any suggestions?

I guess the error message "...modAgentsDataStore:IsDirty" means that there
is some data corruption in whatever database it uses. This is unusual,
because I rebooted on Nov 16, and 25th, nowhere near the problem start -
problem seems to have arisen on its own; coincidentally on the same date the
new version was released (Nov 21).

I guess I should uninstall / delete / reinstall to get a clean database, but
I was wondering if Microsoft support people / Giant Software people would
like more investigation / information on it?

Windows 2000 Service Pack 4
AMD Athlon 1.4 GHz
256 MB RAM, 160 GB SATA HDD
Always latest Windows Update security patches
Always up-to-date McAfee Enterprise v7 anti-virus
Hardware firewall
Reboot every 2 weeks ("whether I need to or not")

Thanks for your help,
-- Best Regards,
Greg L

None of this will matter once the AIs take over.
 
Greguru7 said:
I guess I should uninstall / delete / reinstall to get a clean database,
but
I was wondering if Microsoft support people / Giant Software people would
like more investigation / information on it?

Thanks for thinking about the support side of the issue, but I'd go ahead
and do what you propose above, I think. I don't believe that further effort
is going into troubleshooting issues related to the beta1 code, so the
shortest route to a fix on your machine is probably best.
 
Hi,

Thank-you, that fixed it. I uninstalled MS Anti-Spyware, renamed the
installation directory (C:\Program Files\Microsoft AntiSpyware), and then
re-installed clean. Works AOK now.

BTW, I think your product does a world of good, and I recommend it to
everyone I know.
Thanks again,

-- Best Regards,
Greg L

None of this will matter once the AIs take over.
 
Thanks--I do too--and 18,000,000 active installs says it must be doing some
good.

I expect beta2 will be a major improvement, too.

--
 
Back
Top