HUGE error.log

[Cal]

I am running the beta on a Windows Server 2003 computer.
One day Windows was telling me that my C: drive, dedicated
to Windows OS, was out of space. When I went to
invistigate I had a 2 gig error.log file from Microsoft
Antispyware. After I deleted that file it started to grow
again. I finally had to set permissions for everyone to
deny access to file to stop it. Has anyone else seen this
problem before or have any idea what I can do to stop it.

The error is "91::ln 0:Object variable or With block
variable not
set::gcasDtServ:modThreatData:Initialize::5/23/2005
9:40:57 AM:1.0.509" My MAS is up to date, and I can't seem
to find a disable log settings.

 

[Andre Da Costa]

Delete the huge file--stop Microsoft Antispyware via the system tray icon
before doing so.

Do you find any "visual" defects in your installation of Microsoft
Antispyware--missing System Explorers, for example?

There are several things you can try here:

1) you can try registering the files referenced in errors.log by hand.

2) One source of some failures to register during the installation routine
can be mismatched versions of multiple files constituting the VB6 runtime.

A fix for this is to install a Service Pack for this runtime:
(download)
http://www.microsoft.com/downloads/...61-7a9c-43e7-9117-f673077ffb3c&DisplayLang=en

 

[Andre Da Costa]

You can simple uninstall the Microsoft AntiSpyware (Control Panel >
Ad-Remove Programs), then navigate to c:\program files\Microsoft AntiSpyware
and delete the error log.

 

[Bill Sanderson]

I'd recommend uninstalling the beta from this machine. Your workaround
seems reasonable, but I'm not sure what other side effects it might have.

 

[Andre Da Costa]

Actually I'm following your workaround uninstall procedure based on
someone's successful experience try it Bill. ;-).

 

[Bill Sanderson]

Here's my thinking:

In my case, I was testing the beta on a Windows 2000 server from which only
I surfed--and mostly to isc.sans.org and www.microsoft.com and
support.dell.com

I uninstalled and reinstalled, and all went well for a period of weeks.
Then it happened again.

So--I pulled the beta from the server.

No sense bringing down a server, whether it is serving a dozen users or a
thousand, to do a minimal test of beta software.

So--given that he had the problem, and that it was occurring on a server,
and I think beta2 isn't too far away--I made the recommendation that I did.

 

[Andre Da Costa]

You surf the web on a Server OS Bill?