glide
May 1st, 2006, 12:42 AM
Hi all,
One of my clients use NOD32 and specifically xmon for their exchange server. Lately there has been an issue where people are unable to login to exchange (outlook just freezes up) or during their outlook session, it will lose connectivity with the server. I have traced the problem back to a specific date, and in the eventvwr application logs on the server, there are about 40 instances of this every day:
{QUOTE-> Event Type: Error
Event Source: MSExchangeTransport
Event Category: Exchange Store Driver
Event ID: 348
Date: 1/05/2006
Time: 12:50:48 PM
User: N/A
Computer: <edited>
Description:
A message could not be virus scanned - this operation will be retried later. Internet Message ID <edited>, Error Code 0x0.
For more information, click http://www.microsoft.com/contentredirect.asp. <-QUOTE}
After that date, (about a month ago) it seems that this has become a regular occurence. Im not sure if the two issues are linked, but I've never had a problem like this before and I am not too familiar with NOD32.
Is this a known issue or just a coinsodence, any ideas?
One of my clients use NOD32 and specifically xmon for their exchange server. Lately there has been an issue where people are unable to login to exchange (outlook just freezes up) or during their outlook session, it will lose connectivity with the server. I have traced the problem back to a specific date, and in the eventvwr application logs on the server, there are about 40 instances of this every day:
{QUOTE-> Event Type: Error
Event Source: MSExchangeTransport
Event Category: Exchange Store Driver
Event ID: 348
Date: 1/05/2006
Time: 12:50:48 PM
User: N/A
Computer: <edited>
Description:
A message could not be virus scanned - this operation will be retried later. Internet Message ID <edited>, Error Code 0x0.
For more information, click http://www.microsoft.com/contentredirect.asp. <-QUOTE}
After that date, (about a month ago) it seems that this has become a regular occurence. Im not sure if the two issues are linked, but I've never had a problem like this before and I am not too familiar with NOD32.
Is this a known issue or just a coinsodence, any ideas?