View Full Version : XMON - infromation store stops!
bcampbell
August 13th, 2005, 12:47 PM
OK - I did not read the XMON install first - doh! I installed NOD32 and then installed Exhange version not knowing that it wasn't a seperate module. So now the information store mounts - then a couple of minutes later the information store stops. I have uninstalled everything. I have deleted every 'eset' entry from the registry and deleted the ESET folder. I have now installed correctly (several times) however this behaviour still exists. When I stop XMON the information store is stable - when i start it again it stops anywhere between a few seconds and a few minutes later. Any ideas? Am I missing something when I am uninstalling NOD32?
asdf69
August 14th, 2005, 07:35 PM
have a read through the following, KB328841 from Micro$oft
http://support.microsoft.com/default.aspx?scid=kb;en-us;328841
this may help to solve your problems...and y none of the anti-virus vendors can't just follow these guidlines when the exchange versions are installed I'll never know...
bcampbell
August 15th, 2005, 06:02 AM
Thankyou for that. Unfortunately it isn't working in this case. Even with AMON disabled all together XMON kills the information store.
culla
August 15th, 2005, 06:15 AM
try uninstalling it, get ccleaner run it, search for issues and fix them, save a backup just incase, this cleans stuff left behind, restart then install again let me know if this works for you if not will try something else but try this first
bcampbell
August 15th, 2005, 06:17 AM
cccleaner? whats that then?
culla
August 15th, 2005, 06:20 AM
ccleaner is commonly known as crap cleaner check it out here
http://www.ccleaner.com/
Marcos
August 15th, 2005, 06:28 AM
With this issue, you could contact support @ eset.com. We will provide you with a newer version of xmon.dll to see if it resolves the problem, in case it's actually caused by XMON.
bcampbell
August 15th, 2005, 09:46 AM
Have recieved an updated XMON.dll and unfortunately the problem persists.
Have uninstalled and ran ccleaner.
Have followed KB328841 and excluded all necessary folders.
Have turned off AMON.
This will be the 5th Server I have installed NOD32 on in the 2 weeks and the first time I have had any problems. This is the only Windows 2000 Small Business Server I have installed it on though other 2003 SBS and Windows 2000 Server with Exchange posed no problems at all. I am at a loss!
bcampbell
August 17th, 2005, 04:48 AM
In a clutching at straws attempt to fix this issue I moved the Exchange databases to a different drive, and when I restarted XMON our bizarre fault went away – for the first 12874 scanned emails and then the information store stopped again. I then defragmented the databases but it just crashed it again; however I now believe it points more to database consistency and XMON.
I used a combination of ESEUTIL and ISINTEG to repair errors in the priv1.edb and priv1.stm.
I then told XMON to rescan and I received 1342 virus alert emails similar to the one below. A strange alert saying that infected files are ok? It got further this time but still the outcome was the same.
Virus Alert email - part of
...s@hotmail.c > MIME > text2.html > MIME > text2.html > MIME > text2.html > MIME > text2.html > MIME > text2.html > MIME > text2.html > MIME > text2.html > MIME > text2.html > MIME > part000.htm is infected with is OK.
FYI NOD32 replaced Symantec Multi Tier V9.0 on this server.
vBulletin® Copyright ©2000-2013, Jelsoft Enterprises Ltd.
Copyright ©2002 - 2013, Wilders Security Forums