Error log size

[Dennis Pinney]

In the process of failing to get the MSAS update feature
to work, I found that my error log file in the MSAS
directory is over 139M in size. Many of the errors speak
of being out of memory and then later the dll not being
registered. I even ran a HijackTHis report before
completely unistalling MSAS. I did save the diagnostic
and error logs from MSAS beforehand. I am about to re-
install MSAS one more time to see if my update problem
gets fixed. Is there some reason my error log is so
huge? Who should (if I even should) I send the
error.log, diagnostic.log, and [possibly] the HijackThis
report to?

Dennis

 

[Bill Sanderson]

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

(explanatory KB article)
http://support.microsoft.com/default.aspx?scid=kb;en-us;290887

I've not tested this download as a cure for the failure to update issue, and
I'm skeptical about the likelyhood that it would work. But if you've got
the bandwidth--the experiment shouldn't harm anything and might help.

My usual recommendation for failure to update is to manually delete the
definition files involved:
http://support.microsoft.com/default.aspx?scid=kb;en-us;892519

shows which files are involved.

Try this and see what happens.

At present, if you aren't experiencing Error 10x messages, I don't have
information about Microsoft being interested in the errors.log files.