Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: iloop on December 09, 2003, 12:21:55 PM

Title: Avast 4.0 and Outlook 2003
Post by: iloop on December 09, 2003, 12:21:55 PM

Hi,

I've just installed Avast for the first time (Win XP Pro, Outlook 2003), and for some reason it keeps giving me "Cannot scan message body", or "Cannot scan attachment" messages, both with an error ID of 00046102. I had to disable e-mail protection entirely, since this kept popping up for each mail message.
Can anyone please assist me with this?

Thanks,
Iloop

Title: Re:Avast 4.0 and Outlook 2003
Post by: Vlk on December 09, 2003, 01:17:02 PM

1. Are you using the latest version of avast? (4.1.304)
2. Does this happen even after reboot?
3. The error code does not seem to be correct. Can you please quote it exactly, or better yet, attach a screenshot of the error dialog?

Generally, current versions of avast should work perfectly with Outlook 2K3.

Thanks
Vlk

Title: Re:Avast 4.0 and Outlook 2003
Post by: iloop on December 09, 2003, 02:11:52 PM

1. Indeed: 4.1.304
2. Yep. Many a reboots...
3. Here it is:

Title: Re:Avast 4.0 and Outlook 2003
Post by: iloop on December 09, 2003, 02:12:52 PM

Here it is now (I hope)

Title: Re:Avast 4.0 and Outlook 2003
Post by: Vlk on December 09, 2003, 03:27:09 PM

Oops, can you post the output of the following command entered on the command prompt:

SET TEMP


Thanks
Vlk

Title: Re:Avast 4.0 and Outlook 2003
Post by: iloop on December 09, 2003, 03:35:19 PM

"S:\Temp"

Changed it to C:\Temp, everything works beautifully!
"S" is a drive on my home LAN server, but I have no idea why this setting was there. Probably my braniac brother fidgeted without telling my.
Anyways, thanks for the help!

Title: Re:Avast 4.0 and Outlook 2003
Post by: Vlk on December 09, 2003, 03:37:49 PM

Wait a moment, the only reason for the message I see is that S: would actually be a loopback share -- i.e. it would be a 'network' disk actually mapped to your local computer (in contrary to a remote computer, which is usually the case). Can you confirm this?

Thanks,
Vlk

Title: Re:Avast 4.0 and Outlook 2003
Post by: iloop on December 09, 2003, 04:01:20 PM

Uh, it appears as a drive in Windows Explorer. Is that what you mean by "loopback share"?

Title: Re:Avast 4.0 and Outlook 2003
Post by: Vlk on December 09, 2003, 04:06:11 PM

No, thats not what I meant :D

You said:

Quote

"S" is a drive on my home LAN server

And my question was: 'are you sure'? Is it really a drive on your LAN server, isn't it in fact a mapping onto the same computer's share?

Like imagine you had folder C:\Doc and you had it shared. Then you'd map that share to disk S:, on the same machine...That's what I call a loopback share (as it points back to the same machine). And that would be causing the problems you were describing...

Thanks
Vlk

Title: Re:Avast 4.0 and Outlook 2003
Post by: iloop on December 09, 2003, 04:11:08 PM

Oh, sorry.
No, "S" is indeed a shared drive on a different computer.
On a different note - I use outlook 2k3 with an internet mail account (pop and smtp) - which provider should I use - Internet Mail or Outlook/Exchange (maybe both)?

Title: Re:Avast 4.0 and Outlook 2003
Post by: Vlk on December 09, 2003, 04:13:07 PM

Outlook/Exchange, definitely. That's what you're using now, right?

It's far more flexible than the generic Internet mail proxy.

Title: Re:Avast 4.0 and Outlook 2003
Post by: iloop on December 09, 2003, 04:14:30 PM

they're both working. I guess I'll disable Internet Mail... :)

Title: Re:Avast 4.0 and Outlook 2003
Post by: Vlk on December 09, 2003, 04:26:23 PM

OK.

Could you do me a favour? Please run the following tiny program: http://www2.asw.cz/~vlk/minitest.exe on your machine and report what it's telling you.

Thanks
Vlk

Title: Re:Avast 4.0 and Outlook 2003
Post by: iloop on December 09, 2003, 04:45:19 PM

1. calling isloopbackfile
2. returning OK

If I guess correctly, that means it thinks that it is a loopback share. I can assure you that it's not.