Author Topic: Outlook Plugin Error [?log@clog@@... could not be located...]  (Read 11857 times)

0 Members and 1 Guest are viewing this topic.

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11655
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re:Outlook Plugin Error
« Reply #15 on: January 26, 2004, 04:33:31 PM »
There are problably other files in \windows\system.

Try

aswCmn*.dll
aswScan.dll
aswEngin.dll
ashOutXt.dll
ahRes*.dll

Delete them all.


Vlk

If at first you don't succeed, then skydiving's not for you.

Jaco

  • Guest
Re:Outlook Plugin Error
« Reply #16 on: January 26, 2004, 04:57:51 PM »
I found aswCmnOS.dll in the windows\system32 folder. I deleted the file and now the error messages disappeared!

Thanks for the help!  :D

Kind regards,

Jaco.


zippy 2004

  • Guest
Re:Outlook Plugin Error
« Reply #17 on: January 26, 2004, 05:39:49 PM »
SORTED !!!!! ;D

Thanks you VLK & Jaco for the help

Best wishes - Paul

nathanhaigh

  • Guest
Re:Outlook Plugin Error [?log@clog@@... could not be located...]
« Reply #18 on: January 28, 2004, 08:30:53 AM »
I have been busy and unable to contribute since my initial post, but i have just checked back to see that the problem seems to have been solved.

I too found a couple of the files you suggested in the system32 folder, and deleted them....outlook now loads without any warning messages and the splash screen pops up as expected, and virus scanning has resumed! YES!

Thanks for your hard work in tracking down the problem! Was this a bug with avast or is it a problem with something on our systems?

Thanks again
Nathan

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11655
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re:Outlook Plugin Error [?log@clog@@... could not be located...]
« Reply #19 on: January 28, 2004, 08:34:01 AM »
We have absolutely no idea who or what placed the avast DLLs in the system folder.

Anyway, we've changed the avast updater so that starting with the next program update, it will explicitly look for these files in Windows system folders and if found, will nuke them immediately. You're probably not the only ones with the same problem. Maybe some very old version of avast setup/updater had a bug that could cause placing the files to incorrect locations...

Anyway, thanks for helping to track this down,
Vlk
If at first you don't succeed, then skydiving's not for you.