[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.] NOD32 Database 2022 BIG ISSUE - THE OFFICIAL BLOG OF THE SBS DIVA
Tue, Jan 30 2007 18:03 bradley

NOD32 Database 2022 BIG ISSUE

Hilton reports in the SBS2k listserve.... 

If you are running NOD32 with XMON enabled (the Exchange Server plugin)
and have the 2022 update downloaded and running, then Exchange
Information Store will fail. Disable XMON, restart Exchange, and wait
for an updated database. This issue has been reported to ESET.

http://support.microsoft.com/default.aspx?scid=KB;EN-US;823166
The fix is to ensure that you exclude additional log files such as the Exchsrvr\server_name.log directory.
....while you are at it.. review this one too....
http://support.microsoft.com/default.aspx?scid=KB;EN-US;822158

Filed under:

# re: NOD32 Database 2022 BIG ISSUE

Tuesday, January 30, 2007 11:02 PM by HiltonT

Hi All,

There's a simple fix.  It seems that Microsoft forgot to add the blah:\Program Files\Exchsrvr\<servername>.log folder from its list of folders that need to be excluded from Exchange scanner plugins.  If you exclude this folder and re-enable XMON, you will find all things are all rosy once again.

# re: NOD32 Database 2022 BIG ISSUE

Tuesday, January 30, 2007 11:05 PM by HiltonT

Database update 2023 is now released, by the way.

# re: NOD32 Database 2022 BIG ISSUE

Tuesday, January 30, 2007 11:19 PM by HiltonT

OK.  Microsoft seems to have added this location to their KB article: http://support.microsoft.com/kb/823166 today (apparently after ESET notified them about the issue).

(Note today's date on the KB article?)

# re: NOD32 Database 2022 BIG ISSUE

Thursday, February 01, 2007 7:34 PM by bradley

No Hilton, that info has been in the KB's and documents way back.  Google on that info and you'll see it was even documented on the EHLO blog in 2004.

Marina had that exclusion in there already (ooooh didn't read did ya?) ...it was the 2022 that was the issue actually.