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

[FastEddie]

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].

 

[Susan]

what AV are you using? I would contact that vendor...

 

[FastEddie]

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.

what AV are you using? I would contact that vendor...

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].

 

[Ben Winzenz [Exchange MVP]]

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

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.

what AV are you using? I would contact that vendor...

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].

 

[FastEddie]

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

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

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.

what AV are you using? I would contact that vendor...

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].

 

[Ben Winzenz [Exchange MVP]]

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

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

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

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.


what AV are you using? I would contact that vendor...

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].

 

[John Smith]

Hi Eddie,

I just found this. Maybe it will help:

http://www.webservertalk.com/archive128-2004-10-439692.html

Good luck
Matt

 

[FastEddie]

Ok. I understand.

We updated our client AV product to the latest engine which came out 3 weeks
ago and so far, the problem has gone away.

thanks,

-Ed

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

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

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


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.


what AV are you using? I would contact that vendor...

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].

 

[FastEddie]

Thanks John,

I also found that and the settings were already applied.

We uninstalled our AV on the client and installed a newer one and this fixed
the issue.

Fasteddie

Hi Eddie,

I just found this. Maybe it will help:

http://www.webservertalk.com/archive128-2004-10-439692.html

Good luck
Matt

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].