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: This would leave the source database mounted and the destination (the second database copy) would end up in a “Failed and Suspended” state. We were having issues with their Exchange 2013 servers and one node would crash or lose connection and break the DAG replication. 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.
Exchange 2013 has gone through an evolution in the way the Offline Address Book is generated and maintained.
0 kommentar(er)
