I'm having some trouble with upgrading our Exchange 2007 SP1 servers to SP3. I read a few articles on how to do it (e.g. http://technet.microsoft.com/en-us/library/bb676320%28v=exchg.80%29.aspx), but nevertheless, I did it out of order. What I think I was supposed to do is:
- Update the AD schema
- Upgrade our CAS
- Upgrade the passive CCR node (node B)
- Move resources to the passive CCR node (node B) and run setup /upgradecms
- Upgrade CCR node A
Instead, I did something like this:
- Upgraded the passive CCR node (node B)
- Moved resources to the passive CCR node and ran setup /upgradecms, which got stuck at 75% while trying to start the clustered mailbox server. I closed the command window and rebooted the machine, which forced resources back to node A.
- Realized my mistakes, updated the CAS and the AD schema, then repeated step 4 with setup /upgradecms. It still got stuck at 75%, so I edited the registry to clear the Watermark and Action entries. It didn't like that, complaining that the upgrade version and the current version were the same, so I put back the Watermark and Action entries and re-ran it. It failed with this error:
"Error The properties were stored but not all changes will take effect until the next time the resource is brought online occured while performing exsetdata operation; the original error code was 0xc00713a0."
I tried to move resources using the cluster management snap-in, but that got stuck trying to bring up the Exchange Information Store Instance. I noticed that when this was happening, there were also many MSExchange System Attendant Mailbox 4001 errors. I have also had a recent issue with the SENS service causing lock-ups when I log-off, but I doubt it's related.
Any ideas?