To be more precise, the whole error message when I try to scan files+folders via the rightclick context menu is:
Error: During Open ATL dialog. Error number:340.
Happened only after the last update (pro version, 4.0.235, VPS file 09306-8).
Waiting for some good advice… ;D
How about the normal avast? Does it start? What OS are you using?
Yes, it does start and behave normally. Using XP Professional Service Pack 1 (and none of the updates following Service Pack1).
I would like to add that the above error message box closes down by itself after 4-5 seconds without any input (but it does have the typical “OK” and “Cancel” buttons).
All providers seem to operate normally, and the logfiles do not give much to think about… problems registered:
- Emergency, alert, critical and info logs are empty.
- Error log has one entry:
19.06.2003 09:19:38 NT AUTHORITY\SYSTEM 1416 ODBC function SQLConnect() failed. Error description: [Microsoft][ODBC Microsoft Access Driver] Could not find file ‘(unknown)’… - Warning log:
20.06.2003 10:46:44 PBLE\Boudoufalos 3920 ASWSIMPLE program run information: CaswSimplePos::LoadWindowMove() failed. - Notice log:
19.06.2003 09:22:33 PBLE\Boudoufalos 1684 Library Setiface.dll was successfully updated.
19.06.2003 09:23:04 PBLE\Boudoufalos 1684 Library Setiface.dll was successfully updated.
20.06.2003 10:46:55 PBLE\Boudoufalos 3920 ASWSIMPLE program run information: CaswSimpleDlg::OnDlgEnhance() > OnCancel() is called.
22.06.2003 17:11:00 PBLE\Boudoufalos 1456 Library Setiface.dll was successfully updated.
22.06.2003 17:11:27 PBLE\Boudoufalos 1456 Library Setiface.dll was successfully updated.
04.07.2003 21:44:15 PBLE\Boudoufalos 1464 Library Setiface.dll was successfully updated.
10.07.2003 21:31:05 PBLE\Boudoufalos 1900 Library Setiface.dll was successfully updated.
10.07.2003 21:31:27 PBLE\Boudoufalos 1900 Library Setiface.dll was successfully updated.
12.07.2003 15:23:52 PBLE\Boudoufalos 1416 Library Setiface.dll was successfully updated.
18.07.2003 22:42:06 PBLE\Boudoufalos 1532 Library Setiface.dll was successfully updated.
So far, I had not any problem with ODBC objects in any other application.
Avast! 4 pro was running in parallel with Kerio Personal Firewall 4 beta 4, which was a mess of a program- so I uninstalled it, cleaned every trace of it and tried the fast scan thing again, with the same results. Recently I upgraded to Kerio 4 beta 5 (which at last does seem to work… somehow) but needless to say the Avast problem is still there.
Thank you for your input… I’m not a newbie computer user, but the problem is quite puzzling and beyond my knowledge level… I could attempt a fresh Avast installation, but I’d rather prefer finding out the root of the problem- you too, I guess.