Our exchange database is corrupted and keep dismount . The problem is not as easy as using eseutil /p and /d . It is more advanced and complicated. If anybody is aware on how to fix this issue please bid for this project.
...working properly, and the system was working correctly until 2 weeks ago, when we believe some changes were made to the server by an ex-employee. We have already performed an eseutil /mh and p on the mail queue folder. These messages are hung in the queue with "430 4.2.0 STOREDRV; mailbox logon failure error". We have changed the user running "Exchange
We attempted to repair a [log masuk untuk melihat URL] file using eseutil /p and isinteg -patch (and the usual heroic measures). Data loss was catastrophic. Only two minor subfolders were recovered out of some 4000 contacts. It is Exchange 5.5. We run it on NT 4 6A The original file was about 56MEG and the "repaired" file turned out to be only 2MEG. The original records