Urgent- Exchange Store stopping w-XMON after 2022 update ??

Anyone that has had this issue could you please provide information about the Operating System, XMON version, other software loaded onto the server, as ESET are still trying to determine what exactly happened with the update and the Information Store.

Did you have the following exclusions within AMON?

C:\Program Files\Exchsrvr\Mtadata
C:\Program Files\Exchsrvr\Mdbdata
C:\Program Files\Exchsrvr\Servername.log (replace Server Name with your servers name)
C:\Program Files\Exchsrvr\Mailroot
C:\Program Files\Exchsrvr\Srsdata

Please forward all the above information to:

support @ eset.com with a link to this thread.

Cheers

 

Does someone of you use other version of Exchange than SBS 2003 that was affected?

 

I've just been doing mdb, mta, and mailroot lately....and the pop3 collector directory in the cases where the pop3 connector is used...(approx 1/2 of my SBS installs)

A few servers at 2.51.15
And the majority at 2.50.16 and 2.50.25

Marcos...we also had non-SBS Exchange servers affected, and I just finished my last check...on an SBS2000 box, info store was halted. Also an Exch 2K vanilla on Server 2K

All servers I checked this morning had the 2023 already, approx 1/2 of them needed the info store jump started, the others had settled in OK.

 

As much information about both those that were not affected and those that were is required.

Please email the information to support @ eset.com with a link to this thread.

Cheers

 

XMON version 2.51.15 here too. Regarding the exclusions, the parent folder "c:\program files\exchsrvr" and the mdbdata folder which was on another drive were excluded. This happened on both Win2003 SP1+Exch2003 SP2 (SBS2003) and Windows2000 SP4+Exch2000 Sp4 (SBS2000)

Other software installed.. NOD32 RA Server & Console and a couple of SQL Instances (due to Small Business Server). No other software of note installed on them.. although they have both had other Exchange AV products installed on them in the past (before I looked after them) - Symantec Mail Security 5.0.4 and AVG Exchange.

 

FYI all...I just got done remoting to a SBS2000 site that was using Symantec Corp Edition...his info store was down also.

 

Curious to see how that could possibly relate to a bad NOD32 Def What's the correlation?

 

that's odd. when i discovered that the 2022 update was what had taken down my exchange server, i quickly re-installed symantec mail security for exchange, which allowed me to run my email server fully protected all night while eset worked out a fix. in fact it's still running on symantec right now. i'm just about to switch back to eset.

btw, blackspear, i already sent an email to eset support with all of those details last night. i'm assuming that i don't need to do it again.

 

I just updated XMON to 2024 and all is well!

 

2x 2K3 R2 STD, Exchange 6.5SP2, latest patches from MS
Nod32 2.5.26
Xmon 2.51.15
Amon set to exclude Exchange runtime & datastores.

5x SBS2k3, Exchange 6.5sp2, latest patches.
Same versions of Xmon & Nod32, Amon set the same.

1x 2K3 STD, Exchange 6.5SP@, latest ms patches.
Same versions of Nod32 + Xmon + Amon & same settings.


Have a look at the attached for additional Nod info.


Spec wise, machines are single or dual cpu P4/Xeon machines.. Mostly IBM ... Pretty standard setup..

 

Why? I'm not. ctrl+v worn out yet?

 

Geez- sorry I didn't reword it for you. I assume you're referring to me posting in both forums? You posted the same comment in both, I asked the same question in both. Am I not supposed to say I'm curious about the relationship to the 2 failures?

 

Gentlemen, enough of the personal banter, back on topic please.

Cheers

 

blackspear is on the money with the exclusions...

http://www.msexchange.org/articles/Properly-Configure-file-system-antivirus-Exchange.html

thoes should be added regardless if you had a problem... and here are some ms articles to boot

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