We tried to fix this copy and were unable to do so with a reseed or a resume.
So we decided to remove the copy and then create a new database copy. With a single, good database copy, we can now generate, update and download the Offline Address Book.
After we removed, we tested the OAB to see if this would make a difference. Although Microsoft touts that the address book can now reside in multiple locations (CU 7 ) and the generating mailbox can be replicated via a DAG: “This new infrastructure can also take advantage of the high availability architecture of Exchange 2013.
The OAB mailbox can be deployed on a mailbox database that has multiple copies, thereby mitigating a failure mode that occurred in previous releases.” Ironic in that if the OAB generating mailbox resides in a database that has a failed copy, then it could potentially lead to failed downloads.
What ended up happening is about a day later if a user tried to manually download the address book, they would not be able to and would get a 0x80190194 error: Troublshooting So what is this? Well, let’s look at the log files for OAB downloading.
This would leave the source database mounted and the destination (the second database copy) would end up in a “Failed and Suspended” state.
It is rather a unique issue and no definite solution was provided in the blogs.
Only generic methods to resolve the problem which were not apt. All the necessary information has been mentioned here.
We should also check to make sure we can update the OAB using Power Shell.
So, first, check to see where the mailbox is: Which gives us this result: Then we can check and the database is mounted: Next we can try to update the files for the OAB.