I'm sure there is something that needs to be run in PowerShell that will fix it, but there doesn't seem to be any documentation or other peoples experiences regarding the aftermath of doing a exchange restore. I don't really want to have to go round a remove and re-add all the user profiles on to client machines outlooks (150+ spread over different locations in the UK). I have tried doing a local machine index rebuild but this has not resolved the issue. Some items may not be included in your search results.' 'We're having trouble fetching results from the server. However, each time a client outlook does a search it now comes up and says. that really sucked, so instead we restored the whole VM back 2 days before the corruption occurred, no biggy, and no really email loss. and would not run, even on different computers. On repair but the utility kept on APPCrashing.
Take a backup of the Identities folder of Outlook for Mac in C drive. Firstly, close all the Outlook for Mac-related processes currently running on the system. The first problem I had was ESEUtil recovery was fine, but still stated dirty shut down, no logs were required to complete the recovery. Rebuild the Outlook for Mac file To fix this issue, you should perform the troubleshooting as explained here.
We had a problem where by we had database corruption and the database would not mount.
