Exchange 0x80200049 OAB Download problem error wrong

Before encountering a question about OAB download, because of the more representative, I will share the solution to everyone.

First, the problem scene

When you use Outlook 2010/2013 to download the OAB prompt: Error 0x80200049, the error is as follows:

Second, the process of troubleshooting

Previously also resolved the OAB download problem, many are due to the OAB directory permissions set is not normal, or the OAB Generation server can not update the OAB files in a timely manner, through the server error log to see if there are obvious errors to locate the problem.

1. Use your browser to access the OAB to see if you can access it properly. The resulting result is HTTP 500, which indicates that the service is not available.

2. First I checked the permissions on the Exchange C:\Program files\microsoft\exchange server\v14\client access\oab on the CAS server. Discovery permissions are missing authenticated Users.

So, with experience, you have a problem here, you add the permissions manually, and then you restart IIS.

3, through the above permission to add, I access the oab,https://localhost/oab through IE, when still prompted with a problem.

4. Next, I try to use the command Get-offlineaddressbook | Update-offlineaddressbook updates the offline address book and restarts the Microsoft Exchange System Attendant service on the mailbox server. Then, on the Exchange mailbox server, check the directory C:\Program files\microsoft\exchange server\v14\exchangeoab\oabguid View whether the time of the generated OAB file is up to date.

Check found that after updating the offline address book, the latest LZX files are generated on the Exchange mailbox server in a timely manner, stating that the Exchange Mailbox server generates the OAB without problems.

5. Next, check for problems with the OAB files generated by the Exchange CAS replication backend, and restart the Microsoft Exchange file distribution and Microsoft Exchange Address Book for the Exchange CAS server. Then look at the directory C:\Program files\microsoft\exchange server\v14\client access\oab to copy the latest OAB files properly.

By checking, Exchange CAs is able to replicate the Exchange mailbox server to generate this LZX file in a timely manner. Note there is no problem with Exchange CAS OAB distribution.

6, through the above check, the server generation and Replication OAB no problem, the next problem appears in the OAB download link. To ensure that users can access the OAB normally, the browser https://mail.comlan.com/OAB/6f7c7005-5882-4316-9c57-0cbf7613017b/ Oab.xml access to the Oab.xml file (where the OAB GUID is replaced according to the actual situation), if you can open the file correctly, the OAB access is no problem. The test results are inaccessible.

7. Since there is a problem with OAB access, there should be an issue with OAB Virtual Directory access. This resets the OAB virtual directory directly.

8. After the OAB Virtual directory reset is complete, check the OAB directory permissions again, there is no problem with the OAB Virtual directory permissions. Access the https://mail.comlan.com/OAB/6f7c7005-5882-4316-9c57-0cbf7613017b/oab.xml,oab.xml file again through the browser

Ability to access the Oab.xml file normally.

9. Next, use the Outlook 2010/2013 client to download the OAB again, and still prompt for error 0x80200049. There is no language at this time. Through Baidu to find a variety of solutions to 0x80200049, the solution is to reset the OAB virtual directory.

10. To troubleshoot client issues, reinstall a test computer, install the Outlook 2007 client, and then use the test account to download the OAB test. What I didn't think of was that it was a success.

11. Outlook 2007 can download successfully, and Outlook 2010/2013 cannot be downloaded successfully, at which point the problem should appear on the client instead of the server side.

Previously, it was known that Outlook 2007 used a BITS server to download the OAB, while the number of bits processing processes was limited, and by default each account was able to initiate 60 queues. And I'm using Outlook 2010/2013, and there shouldn't be a problem. So, tentatively use the command: Bitsadmin/reset command to cancel all jobs in the transmission queue owned by the current user. After the command is executed, the problem is resolved.

12, summary, by understanding the discovery, the default policy, "limit the maximum bits per user" is 60, I understand that regardless of the number of customers using the version of Outlook, bits of the number of download jobs is 60, The possibility of a 0x80200049 error occurs when the number of client-initiated jobs exceeds this limit.

Iii. Summary

There are two ways to solve 0x80200049 errors in the present experience:

1. Reset the OAB virtual directory.

2, reset bits job number bitsadmin/reset. (If the server-side OAB is OK)

Exchange 0x80200049 OAB Download problem error wrong