Re: The item is currently being scanned for viruses. Try again in a few moments. Outlook Error

From: Ben Winzenz [Exchange MVP] (ben_winzenz_at_NOSPAMdotmessageonedotcom)
Date: 02/03/05


Date: Thu, 3 Feb 2005 13:04:22 -0600

Who knows. Perhaps an updated scanning engine on the client or server? All
I know is that if you have an Exchange AV solution in place, it is not
recommended to have client e-mail scanning taking place. It is completely
fine to have file-level AV on the clients, and this would scan attachments
as they are opened, but you don't want the client AV scanning mail at the
same time Exchange is trying to.

-- 
Ben Winzenz
Exchange MVP
"FastEddie" <fasteddie@therockwells.net.no.spam> wrote in message 
news:O7DT9BiCFHA.4072@TK2MSFTNGP10.phx.gbl...
> Why is this just starting now? This configuration has been in place for at 
> least a year and it is on only 10 or so out of a few thousand clients.
>
> -Ed
> "Ben Winzenz [Exchange MVP]" <ben_winzenz@NOSPAMdotmessageonedotcom> wrote 
> in message news:Onr5j4hCFHA.208@TK2MSFTNGP12.phx.gbl...
>> You need to make sure that if the client AV has an e-mail scanning piece 
>> that it is disabled.  Otherwise, you can get into a situation where the 
>> Exchange AV and the client AV are fighting for which one gets to scan the 
>> message first.
>>
>> -- 
>> Ben Winzenz
>> Exchange MVP
>>
>>
>> "FastEddie" <fasteddie@therockwells.net.no.spam> wrote in message 
>> news:eiROfAhCFHA.1432@tk2msftngp13.phx.gbl...
>>> We are using VET www.vet.com.au which is the same as CA E-Trust. We have 
>>> disabled the virus scanning and installed a newer version. This AV is 
>>> installed on over 1000 workstations with the same version which is 
>>> updated every hour if there is an update available.
>>>
>>> We have discovered a work around. If the person affected get's the 
>>> error, they can go into their sent items, open the message and forward 
>>> it to the same user without any problems.
>>>
>>>
>>> "Susan" <susan@nospam.com> wrote in message 
>>> news:OPNXLxgCFHA.2620@tk2msftngp13.phx.gbl...
>>>> what AV are you using?  I would contact that vendor...
>>>>
>>>> "FastEddie" <fasteddie@therockwells.net.no.spam> wrote in message
>>>> news:eRMU0ugCFHA.3436@TK2MSFTNGP12.phx.gbl...
>>>>> All,
>>>>>
>>>>> I have a number of Outlook 2003 users on Exchange 5.5 suddenly getting 
>>>>> the
>>>>> following message. If we remove their profile and recreate it, the 
>>>>> problem
>>>>> goes away for a short while and comes back. I've done the necessary
>>>> searches
>>>>> in google for this message and ended up at dead ends. This is starting 
>>>>> to
>>>>> spread to more users by the hour. The messages DO NOT make it to the
>>>>> exchange server. All patches are applied on both the exchage server 
>>>>> and
>>>>> workstations including office updates. A reboot also fixes it for a 
>>>>> short
>>>>> time but it does come back after a few attachments are sent. I've also
>>>>> checked the background scanning value on the exchange server here:
>>>>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
>>>>> Set\Services\MSExchangeIS\VirusScan and it is correct.
>>>>>
>>>>> Message the users get is here:
>>>>>
>>>>> Your message did not reach some or all of the intended recipients.
>>>>>
>>>>> Subject: RE: Emailing: <attachment name>
>>>>>
>>>>> Sent: 2/2/2005 10:26 AM
>>>>>
>>>>> The following recipient(s) could not be reached:
>>>>>
>>>>> <user> on 2/2/2005 10:26 AM
>>>>>
>>>>> This message could not be sent. Try sending the message again later, 
>>>>> or
>>>>> contact your network administrator. The item is currently being 
>>>>> scanned
>>>> for
>>>>> viruses. Try again in a few moments. Error is
>>>>> [0x80040119-0x00050a-0x000546].
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
> 


Relevant Pages

  • Re: exchange basics
    ... If you find users switching between client ... often pull the mail to a different store (as in POP3) and then wonder why it ... Exchange can inform and enforce quotas on mail storage. ... Server side rules? ...
    (microsoft.public.exchange.design)
  • Re: exchange basics
    ... If you find users switching between client ... > store, so you're right, it wouldn't be a big deal. ... >> -If messages can be stored on server instead of downloading, ... > Exchange can inform and enforce quotas on mail storage. ...
    (microsoft.public.exchange.design)
  • Re: DNS not resolving in a Windows 2003 SP2 network
    ... My exchange server is a stand alone server and not running on a DC, ... exchange because exchange cant find its Preffered DNS? ... server on DC1 for my client workstations. ...
    (microsoft.public.windows.server.dns)
  • Re: WM5, VPN via PPTP/MPPE, and direct connection to Exchange
    ... non-Microsoft VPN server, in order to access an Exchange Server on a private ... clients to Exchange via the VPN server, I have to select the the Outlook ... NOT synchronising with a client laptop. ...
    (microsoft.public.pocketpc.phone_edition)
  • Re: One user having messages stuck in Local Delivery
    ... so you won't have any effect to the client PCs. ... migration of the Exchange data, ... brand spanky new intel rackmount server which has only been sitting here ... tomorrow morning another mailbox or two will start failing. ...
    (microsoft.public.windows.server.sbs)