Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: JeffK on November 08, 2005, 07:17:28 PM

Title: Outlook 2003 Error in oleaut32.dll
Post by: JeffK on November 08, 2005, 07:17:28 PM

After installing avast! pro 4.6 Outlook 2003 SP2 generates the following error:

Faulting application outlook.exe, version 11.0.6565.0, stamp 42cacc7d, faulting module oleaut32.dll, version 5.1.2600.2180, stamp 411096f3, debug? 0, fault address 0x00004ba4.

I don't have to be doing anything in particular to generate the error.

This is a new computer that has never had any other anti-virus installed. The system is a Dell Precision 670 3.0 GHz Xeon with 512MB of RAM. Our mail server is Exchange 2003 and has Norton Antivirus for Exchange installed.

When I uninstall Avast the problem goes away.

Thanks,
Jeff

Edit: I have unchecked the avast! add-in in Outlook 2003 and the problem seems to have gone away. Not a very good solution but is a bandaid until I get a good solution.

Title: Re: Outlook 2003 Error in oleaut32.dll
Post by: Lisandro on November 08, 2005, 07:55:20 PM

Did you try just repairing your avast! installation?
Go to Control Panel > Add/Remove programs > avast! antivirus > Remove. Then choose Repair function in the popup window (Repair). You must be connected to the internet while repairing.
Please, close other running programs before repairing, specially MS Outlook.

If this does not help, can you uninstall / boot / install / boot again?

Title: Re: Outlook 2003 Error in oleaut32.dll
Post by: JeffK on November 08, 2005, 08:30:09 PM

I have tried both with no results.

Thanks,
Jeff

Title: Re: Outlook 2003 Error in oleaut32.dll
Post by: Vlk on November 08, 2005, 09:44:14 PM

This is related to a bug in the "MSN Search Toolbar". MS promised it would be fixed in the next version of that software.


Thanks

Title: Re: Outlook 2003 Error in oleaut32.dll
Post by: JeffK on November 08, 2005, 10:41:58 PM

I uninstalled the MSN toolbar and the issue has gone away.

Thanks,
Jeff