Prev: FPSE_Search File
Next: Event ID 333 Source Application Popup
From: SC Admin on 29 Aug 2005 16:19
We found out we had the latest build of Symantec. We called them on
Friday and they said they hadn't heard of the issue, but after sitting
on hold with Symantec for almost two hours today, they admitted they
had indeed heard of this issue and sent us an executable that resolved
the problem.

If contacting Symantec, please ask for a file called SAVRTICFG.exe, and
once you get it, run SAVRTICFG.exe ICFG:OpenScanningMode 0. Then
reboot. All should be solved.

From: SC Admin on 29 Aug 2005 16:24
SC Admin wrote:
> We found out we had the latest build of Symantec. We called them on
> Friday and they said they hadn't heard of the issue, but after sitting
> on hold with Symantec for almost two hours today, they admitted they
> had indeed heard of this issue and sent us an executable that resolved
> the problem.
>
> If contacting Symantec, please ask for a file called SAVRTICFG.exe, and
> once you get it, run SAVRTICFG.exe ICFG:OpenScanningMode 0. Then
> reboot. All should be solved.

Also, I forgot to mention that when installing SAV Client or Server you
must click 'Custom Install' and disable all e-mail options.

From: Rederick on 29 Aug 2005 17:03
On 21 Aug 2005 20:47:44 -0700, "SC Admin" <admin(a)shadowedcorner.com> wrote:
>So it's a word to the wise. We're not sure if anyone else is having
>this problem, but if you are: Try uninstalling AntiVirus. It can't
>hurt if you do it temporarily and if it's the problem... leave it off.

We are seeing similar errors on a Win2k3 Std SP1 box used as a file server.
We think its McAfee VirusScan Enterprise 8.0i based on this KB article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;888928

James
From: SC Admin on 7 Sep 2005 19:42
Rederick wrote:
> We are seeing similar errors on a Win2k3 Std SP1 box used as a file server.
> We think its McAfee VirusScan Enterprise 8.0i based on this KB article:
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;888928
>
> James

If you read my previous posts, you'll note that I'm not using McAfee,
I'm using Symantec AntiVirus Corporate Edition 10, and I am quite sure
of that. McAfee is not used anywhere in our organisation, and
therefore the pool tags quoted in that KB are incorrect.

First  |  Prev  | 
Pages: 1 2
Prev: FPSE_Search File
Next: Event ID 333 Source Application Popup