Exchange 2003

[gkapel]

Hello again,

a major customer of us had install NOD32 in Exchange 2003 and had exclude from AMON the files which should not be scanned. last Wednsday the informatio sytem dismount and the only way to mount again was to exclude the whole Exchange folder.

Any idea about that? ??? ???

Is good idea to restart the server? ??? ???

George

[Marcos]

It sounds like the well known issue with update 2022. Upgrading to v. 2023 and newer should have remedied the issue.

[gkapel]

should i disable xmon restart the server and the enable xmon again?

[Blackspear]

Just update your NOD32 on that server to the latest virus signatures and remount the database.

Cheers ;D

[steford]

I've started having similar issues on my SBS2003 installation (since April). Server is running sig v2392 and the Exchange directories have been excluded as per Eset help. They also suggest switching off "Scan all Files" which I can't find except for in "Extensions" - switching this off seems it will scan all files and not allow me to exclude - currently excluding .EDB, .LOG etc

Not convinced it is NOD32 causing the issues but some process is locking the logs it seems causing the info store to dismount. It can be mounted straight away manually. Error is -1090 in the Event viewer.

Also notice that XMON is not running on my server for some reason.

Any help appreciated on what is now a daily occurence.

Thanks very much.