EDIT 10/01/2008: To read the updated (and more comprehensive) guidance for troubleshooting errors 0x8004010f, please go here.
There are a multiple reasons for why an Outlook client can receive the 0x8004010f sync error. Unfortunately, 0x8004010f is just a generic MAPI error and will show up for a variety of problems.
Here is what the error looks like under err.exe (Microsoft Exchange Server Error Code Look-up Tool:(
# for hex 0x8004010f / decimal -2147221233
# 5 matches found for "0x8004010f"
This is what the error looks like from the sync log from within Outlook:
12:45:53 Synchronizing Mailbox <dgoldman>
12:45:54 Microsoft Exchange offline address book
Some of the most common reasons for Outlook clients to receive the 0x8004010f error with regards to downloading the OAB are listed below. Most of these are documented and I have linked articles to each of these to help everybody out. Please note that these solutions can change a small bit depending on unknown factors in a company's environment.
If you are seeing this error on an Exchange 2007 server and your OAB is generated by an Exchange 2007 server, please make sure of the following:
- An administrator decommissioned the last Exchange server in a site and never pushes replicas to anot...
- A new OAB is created in the active directory and the information store never reads the active direct...
- The information store has an invalid EntryID that points to the legacy EX:/ folders. Again there is ...
- An outlook client logging in from one domain to another domain and attempting to log in to another u...
- The OAB was never generated or some OAB folders are missing from the public folder store.
- Multiple OAB Version folders exist of the same type.
- Clients are attempting to download the OAB files from a public folder store that have not received t...
- The offline address book list object has a missing address list.
- The offline address book list object has an incorrect address list.
- Send/As changes in the store affect users accounts with no mailbox full rights to another mailbox.
1. Make sure that you have added the replicas of OAB to the Exchange 2007 server
2. Make sure public folder replication is working.
3. Make sure the OAB is public folder enabled and you have OAB Version 2, OAB Version 3 and OAB Version 4 checked off so your legacy clients can download the OAB files from the public folder store.
4. Make sure that if you are using an Outlook 2007 client, your OAB is Web Distribution enabled and the OAB files have been replicated over to the Client Access Server. For more information on this process please see this blog:
5. If you are removing your last Exchange 2003 server from the org, please make sure that you follow our documentation on this process.
- Dave Goldman