Hi,
0x00000005 errors you are seeing from time to time on all scanners. This seems to be mainly caused by windows and is mostly that the scanner cann't connect to the pipe cleanly any more. The new scan engines don't like alternative language settings too much, the run best (mostly only) with English language and date / time settings.
Also default settings are somehow bad .....
I don't have to deal with the support as my links go mainly to 2nd/3rd level or engineering.
Andy
-----Original Message----- From: Neis, Mark [mailto:Mark.Neis@gisa.de] Sent: Freitag, 11. Juli 2008 19:38 To: toasters@mathworks.com Cc: Kiendl, Andreas Subject: Re: CIFS virus scan
Andreas,
What are your problems? There are some tweaks you need to do then it should be running of.
We've been running it for years. We got two Win2003 servers as AV servers for each NetApp cluster we have.
The trouble is not with the filers, but with Symantec. Not too rarely, an unsuccessfull virus update has left a scan engine in a dysfunctional state. As it can still be reached from the filer, it still gets its share of scan requests, which it promptly anwers with a 0x05 error. Moreover we've had some installation problems lately with newer versions of the Symantec scanners (We use standard HP servers, so actually there should be no problem at all).
Besides, Symantec's support has grown so bad during the last two or three years, they are absolutely no help at all.
Because our license period is about to end, we were thinking about replacing the Symantec scanners by a different brand, that's why I wanted to hear about the experience others have made with the alternatives there are.
Kind regards, Mark Neis