By default OAB is a point in time snapshot of global address list and it is used as cached source of information about Exchange recipients properties.
OAB is stored on Exchange servers (see my previous article https://ficility.net/2013/03/04/oab-differences-between-exchange-2010-and-exchange-2013-in-brief/) and downloaded to client once Outlook is configured in Cached mode.
Further Troubleshooting Let’s see where the OAB generating mailbox is and if the database is mounted.
We should also check to make sure we can update the OAB using Power Shell.
This would leave the source database mounted and the destination (the second database copy) would end up in a “Failed and Suspended” state.
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.
To summarize – we have an OAB that is not updating and clients that cannot update their local copies because the copies are too old.
Now the problem is becoming visible to all users and will eventually become a support issue for the client.
While most of the changes are advantageous, I ran into a chink in the armor while working with a customer who was having an issue with Exchange 2013 DAG replication.
We were having issues with their Exchange 2013 servers and one node would crash or lose connection and break the DAG replication.
In this stage Outlook is stuck somewhere between mode 0 and 1 and updates are not received by client.