I verified the file location manually but also noticed the date discrepancy (the blue rectangles in the above image) which shows the date the attempted download was made (upper left) and the date of the files (lower right). The file location is correct and shows where the current OAB files are. Notice the error “IsLocalOABFileCurrent:ManifestEnforcementDisabledAndLocalFileTooOld”. In our case, we had these error messages: Open up the latest log file in the directory and see what errors are being reported by the client.
In Exchange Server 2013, these files are located in the %ExchangeInstall%\Logging\OABDownload directory. So what is this? what does the error message mean? Well, let’s look at the log files for OAB downloading. 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)
