UPDATE: We have now released the hotfix that corrects this issue for Exchange 2003 SP2. The article is: 930241 The Exchange 2003 database does not mount, and event IDs 9518 and 9519 are logge...
Updated Jul 01, 2019
Version 2.0
Blog Post
I agree with JF. This is a nightmare and the documentation leaves a lot to be desired. FYI the link provided for "932599 Information Store database does not mount with Event ID 9519 and 9518" is broken.
Am I mistaken in stating that any appointments I accepted from others during that occur during the time period will be wrong if the originator does not have their Outlook fixed? Oops I better call my Dentist!
I hope MS realizes what a burden this is going to be. I only have 400 users and 2 Exchange servers but already I have spent a lot of hours setting up test environment, preparing documentation, meeting with IT staff etc. Worse than Y2K? Maybe because this is real.
Better documentation would be welcome. Like, how does this actually tie in to CRM? What are the steps when CRM Outlook client is installed. I could go on and on.
Sorry to rant, I'm very frustrated as you can tell.
Am I mistaken in stating that any appointments I accepted from others during that occur during the time period will be wrong if the originator does not have their Outlook fixed? Oops I better call my Dentist!
I hope MS realizes what a burden this is going to be. I only have 400 users and 2 Exchange servers but already I have spent a lot of hours setting up test environment, preparing documentation, meeting with IT staff etc. Worse than Y2K? Maybe because this is real.
Better documentation would be welcome. Like, how does this actually tie in to CRM? What are the steps when CRM Outlook client is installed. I could go on and on.
Sorry to rant, I'm very frustrated as you can tell.