• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1505
  • Last Modified:

Getting 0x8004010F error when synicing offline address book. OAB folder empty on exchange server

We are getting the 0x800401F error when we try to sync out offline address book.  I found the path where the OAB should be and it is empty.  Here is the path. C:\Program Files\Microsoft\Exchange Server\ClientAccess\OAB....should there be something there?
2 Solutions
On you CAS server which is the path that you found there should be the OAB files that are present in the Shared ExchangeOAB folder. Please first check whether the shared ExchangeOAB folder has the recent OAB files created.
The try to restart the msexchange FDS service to see if the files get replicated over there.
Also, Is this a CCR environment?
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

In Exchange Management Console do the following:

Delete the old OAB and create a new one.

Once created do the following:

Step 1:

Organization Configuration -> Mailbox -> Offline Address Book -> Right Click properties on your newly created oab -> Address Lists -> Include All contacts, all users, public folders nad in Distribution select Enabled web-based distribution and add "OAB (Default Web Site)

Organization Configuration -> Mailbox -> Database Management -> Locate your Mailbox Database (default is Mailbox Database 1391317102) -> Right click and choose properties -> Client Settings -> Offline Address Book -> Browse your newly created OAB and click Apply

Server Configuration -> Client Access -> Offlien Address Book Distribution -> Right click and choose properties -> make sure external url corresponds to your certificate ( for example"https://webmail.yourdomain.com/OAB") and your internal URL corresponds correct as well (most cases external URL is the same as Internal)
PS: I hate that error like nothing else.

here's why

and it's very hard to pin down a solution which works.
OAB rebuild is usually the first thing attempted but it works probably 5% of the time.
here are two simple steps
in exchange management shell

then restart the  microsoft exchange file distribution so that the oab get copied over to the  cas\oab folder

request clients to download the OAB
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now