Since installing BES 4.0 SP3, we now get this message periodically, esp. at logon:

---------------------------
Microsoft Visual C++ Runtime Library
---------------------------
Buffer overrun detected!
Program: C:\Program Files\Symantec AntiVirus\Rtvscan.exe
A buffer overrun has been detected which has corrupted the program's
internal state. The program cannot safely continue execution and must
now be terminated.
---------------------------
OK
---------------------------

On Symantec's support boards, there are a number of new threads about this. The upshot is that Symantec believes it's BES-related.

Here's a representative thread.

Here, it has only happened on our BES server, and only since installing 4.0 SP3/Exchange (we were on 4.0 SP2/HF2 before SP3). We are running BES 4.0 SP3/Exchange and SAV CE 10.0.1.1000. There's a newer SAV version but we haven't deployed it yet (haven't finished deploying the last one!)

Apparently SAV 9.x doesn't have the problem. Symantec seems to be zeroing in on the QuickScan feature, which is new to 10.x, and that would explain why we most often see it at logon.

This thread describes disabling QuickScan. I haven't tried this yet.

Didn't get any hits here or on BlackBerry.com searching under "Symantec" "AntiVirus" or "SAV" so I thought I'd raise a red flag.

I have the problem. apparently these people also have the issue. http://techrepublic.com.com/5208-11184-0.html?forumID=49&threadID=182311&start=0&tag=sear ch
my concern is why we have to disable any feature.

If anyone has the solution. could you please post it here?

Arif

I was under the impression that this was an issue with SAV 10 and Windows 2003 SP1? The issue creeps up in multiple places within our environment on the 2K3SP1 servers - dies on some, fine on others.

Actually this is an issue with SAV 10.1 and 2kSP1. We have downgraded to 10.01 and we have not seen the issue since. We had the issue on a BES SP2HF2 not SP3

Maybe so...I haven't seen it on any other WS2003 SP1 servers myself. Only the 1 BES server I administer. Symantec seems to think there's a BES connection.

We are having this issue also, just went from evaluation version to Production version of BES 4.0.3 . That is the only thing that has been changed on the 2k3 server. I will keep an eye on it and watch here. The things that I do know so far: if I run a "FULL" scan it happens and it also happens on my nightly scan. Just some food for thought????

I would try to uninstall symantec fully and try re-installing 10.01 not 10.1...thats what we did and it seems to work right now on both BES Servers with w2k3Sp1 BES 4.0 SP2HF2

Also have a BES with w2k3Sp1 BES Sp3HF1 and I dont see the issue anymore.