Running Exhange 2003 Enterprise Ed ... and preparing for migration to Exchange 2007. Attempting to go through all mail stores and validate integrity (eseutil /g + isinteg -s -fix -test alltests). Latest mail store completed eseutil successfully & isinteg was kicked off. Command line window showed completed isinteg output after all 21 tests, command line was waiting at a new line prompt ... AND corresponding log file shows expected output after tool completion: . . . . . SUMMARY . . . . . Total number of tests : 21 Total number of warnings : 9 Total number of errors : 0 Total number of fixes : 4374 Total time : 3h:34m:50s Attempting to re-run isinteg tool (until fixes come out clean) as I've done on the previous stores, receive a notitfcation that Isinteg is still running and can only run on one database at a time. ??? 'Mailbox Store 2 is currently being checked with isinteg. Only one database can be checked at a time. Please run isinteg later when the check will be completed.' How can it be running if all references point to the tool having completed it's first round of checks? No errors noted in Event Viewer, no unusual processes listed or taking up CPU in task manager. I can't mount my mailbox store ... it tells me the store mounted successfully, but immediately returns as dismounted in ESM. Still no errors listed in EV. Please help?

Is there an instance of it running in Task Manager?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

This may store.exe process was looking edb file, go to restart MS Exchange Informatin Store service, then check again for the issue. Thanks, EvanEvan Liu TechNet Community Support

This may store.exe process was looking edb file, go to restart MS Exchange Informatin Store service, then check again for the issue. Thanks, EvanEvan Liu TechNet Community Support

Ed, There wasn't anything unusual listed in Task Manager for me to kill. Evan, That's exactly what I ended up doing. I stopped the Info Store service, waited a few minutes (crossed my fingers) and restarted. Then, I started the fun all over again. Starting w/a validation that the database shutdown cleanly before running isinteg again. Everything after the restart seemed to go smoothly! Thanks :-) StephanieStephanie

Ed, There wasn't anything unusual listed in Task Manager for me to kill. Evan, That's exactly what I ended up doing. I stopped the Info Store service, waited a few minutes (crossed my fingers) and restarted. Then, I started the fun all over again. Starting w/a validation that the database shutdown cleanly before running isinteg again. Everything after the restart seemed to go smoothly! Thanks :-) StephanieStephanie