Greetings all. Needless to say, I haven't been able to send/reveive any email through exchange lately. Due to an incident of which I'm still unsure as to its nature, the message store was dismounted. Upon trying to remount it, I get an error message instructing me to close "Exchange System Manger" & a couple of exchange servieces, then restart both. Whe I try to remount the message store, I get the same results. Please help.ricseb1

What is the exact error message you are getting? What is being logged in the event log?Mark Morowczynski|MCSE 2003:Messaging, Security|MCITP: Enterprise Support|MCTS:Windows Mobile Admin|Security+|http://almostdailytech.com

hi,please look at http://support.microsoft.com/kb/299000regards,System & Network Support Specialist - Bursa / TURKEY

I suppose the error you are getting is to restart information store.Checked the health of the database using the eseutil /mh command and make sure the same is in a clean shutdown state.http://exchangeis.com/blogs/exchangeis/archive/2007/05/28/using-eseutil-how-to-check-which-transaction-log-files-are-not-committed.aspxIt should look like this: http://exchangeis.com/photos/articles/images/original/Eseutil-_2F00_MH-Database-Header.aspxhttp://exchangeis.com/blogs/exchangeis/archive/2007/04/30/eseutil-r-soft-recovery-a-quick-and-simple-tutorial.aspxhttp://technet.microsoft.com/en-us/library/aa998075.aspxRatish

If the issue is still unresolved, and provide the info about the following questions for further analyzing: 1. Please describe the exchange topology 2. Please clear once application log, and then reproduce the issue. monitor the warning/error event in the application log and also post the exact words about the error you said about close Exchange System Manager 3. Check the health of the mailbox database is a good startpoint as Ratish suggested

Check your hard drive space where the logs and database resides. Do you have enough drive space free?BP

Thanks to all for your advice and help. I have the issue resolved. I restored the message store db from the most recent backup & that solved the issue.ricseb1