Fix it now
0x8004010F is MAPI_E_NOT_FOUND, published as “The requested object could not be found at the server.” For an offline address book download that is literal: Outlook went where it was told and found nothing. Microsoft’s own article for this code names a corrupted Outlook profile as the cause, so test that first – it is quick, and it decides whether the problem is on the client or the server.
Get-OfflineAddressBook | Format-List Name,IsDefault
Update-OfflineAddressBook "Default Offline Address Book"
Get-OabVirtualDirectory | Format-List Server,Name,InternalUrl,ExternalUrl
Get-MailboxDatabase | Format-List Name,OfflineAddressBook
- Establish the scope. Only cached-mode Outlook downloads an address book, so online-mode users being unaffected is expected rather than a clue.
- On one affected machine, create a new Outlook profile against the same mailbox and download the address book in it. Microsoft’s published cause for this code is a corrupted profile, and this test costs five minutes.
- If the new profile works, keep it and stop. If it fails too, the fault is on the server and the commands above are where to start.
- Check the address book exists and is the default, force a regeneration, and confirm the virtual directory that distributes it has internal and external URLs set.
- Have a client download the address book again from Send/Receive rather than waiting for Outlook’s own schedule.
Recreating an Outlook profile discards local settings, signatures attached to it and the cached data file, and forces a full mailbox download. Use it as a diagnostic on one machine, not as a first response for an office.
If the address book downloads, you are done. If it does not, the next section takes generation and distribution apart.
Why it happens
Microsoft publishes 0x8004010F as NotFound, alternately MAPI_E_NOT_FOUND: “The requested object could not be found at the server.” That is a general statement, and it is the honest one. Outlook shows it with two user-facing strings – “Outlook data file cannot be accessed” and “The operation failed. An object could not be found” – and Microsoft’s article about those strings gives a corrupted Outlook profile as the cause, resolved by building a new profile.
That is worth taking seriously before you touch the server, because the offline address book is the context in which most people meet this code and it produces a strong assumption that the address book is at fault. Sometimes it is. Often, on one machine, it is the profile, and the five-minute test settles it.
When it is the server, the mechanism is straightforward. The address book is generated into files, those files are served by a virtual directory – the cmdlet reference calls these OAB distribution points – and Autodiscover tells Outlook the URL. Break generation and the files are absent; break the distribution point and the files exist but nobody can fetch them; break the URLs and Outlook is never told where to look. All three surface as an object that could not be found.
The two companion codes describe the transport rather than the object. 0x80072EFD is Win32 12029, ERROR_INTERNET_CANNOT_CONNECT, “The attempt to connect to the server failed” – Microsoft’s Windows Update guidance describes the same code as firewall rules or proxies blocking a connection. 0x80190194 has no published meaning; it appears in HTTP-carried failures and should be treated as a symptom rather than a diagnosis.
The Outlook profile on that machine is damaged
You have this one if One user on one machine cannot download the address book while the same mailbox works elsewhere.
- Note the default data file first: Control Panel, Mail, Show Profiles, the profile, Properties, Data Files. The file with the check mark is the default.
- Create a new profile from the same dialog and set it to be used by default.
- Open Outlook in the new profile and download the address book from Send/Receive.
- If that works, keep the new profile. Repairing the old one is rarely worth the time it takes.
This is the cause and resolution Microsoft publishes for this error code. Try it before you regenerate anything on the server.
The address book is not being generated
You have this one if The folder that should hold the generated files on the server is empty or absent, and no recent generation entries appear in the Application log.
- Check the arbitration mailbox that performs generation is present and on a mounted database:
Get-Mailbox -Arbitration | Format-List Name,Database,ServerName. - Mount the database if it is dismounted, and confirm the server holding it is healthy.
- Run
Update-OfflineAddressBook "Default Offline Address Book"and let it finish. On a large directory this takes a while. - Watch the Application log for the generation entries and read any failure recorded there.
The distribution point is not serving the files
You have this one if The files are on disk, but requesting the address book URL from a browser on the server returns a not-found page.
- Check what exists:
Get-OabVirtualDirectory | Format-List Server,Name,InternalUrl,ExternalUrl, adding-ShowMailboxVirtualDirectoriesto see the back end copies. - In IIS Manager, confirm the application exists and that its physical path is the folder that actually holds the generated files.
- If they do not match, recreate the directory with
Remove-OabVirtualDirectoryandNew-OabVirtualDirectoryrather than repointing it by hand. - Run
iisreset /noforceand request the URL again from the server console.
The URLs are missing, so Autodiscover hands out nothing
You have this one if Outlook’s autoconfiguration returns settings but no address book URL, or one that does not resolve.
- Set them to names your certificate covers:
Set-OabVirtualDirectory -Identity <identity> -InternalUrl https://mail.contoso.com/OAB -ExternalUrl https://mail.contoso.com/OAB. - Confirm the certificate includes those names and that the chain is complete.
- Retest with
Test-OutlookWebServices, then with the client’s own autoconfiguration test. - Allow time for clients to pick the change up. Outlook does not re-read Autodiscover on every start.
The database points at an address book that no longer exists
You have this one if Users on one database fail while everyone else is fine, and that database names an address book that has been deleted or renamed.
- Check the assignment:
Get-MailboxDatabase | Format-List Name,OfflineAddressBook. - Point it at a current book, or clear the setting so the organisation default applies.
- Confirm exactly one address book is marked as the default:
Get-OfflineAddressBook | Format-List Name,IsDefault. - Have an affected client download the address book again to confirm.
Full reference
Client or server, in one test
| What you observe | Where the fault is |
|---|---|
| One machine, one user | That Outlook profile. Microsoft’s published cause for this code |
| One user on every machine | The mailbox or the database it sits on |
| Everyone on one database | The address book assigned to that database |
| Everyone, everywhere | Generation, the distribution point, or the URLs |
| Only external clients | The external URL, the published path or the certificate |
| 0x80072EFD on the client | The connection never completed. A firewall, a proxy or an inspection device |
The three things that have to be true
- The address book is generated. There is an offline address book object, one of them is the default, and the generation has produced files.
- The distribution point serves them. The OAB virtual directory exists, its physical path is the folder holding those files, and IIS will return them.
- Outlook is told where to look. The virtual directory’s internal and external URLs are set to names the certificate covers, and Autodiscover is handing them out.
Check them in that order. Regenerating an address book that is already being generated fine is the most common wasted step in this investigation, and it takes long enough on a large directory to eat a change window.
Cmdlets worth having open
| Cmdlet | What it answers |
|---|---|
Get-OfflineAddressBook | Format-List Name,IsDefault |
Which address books exist and which one is the default |
Update-OfflineAddressBook <name> |
Forces a regeneration |
Get-OabVirtualDirectory |
The distribution points, and their internal and external URLs |
Get-OabVirtualDirectory -ShowMailboxVirtualDirectories |
The back end copies on Mailbox servers |
Set-OabVirtualDirectory -InternalUrl / -ExternalUrl |
Sets the URLs Autodiscover hands out |
Get-MailboxDatabase | Format-List Name,OfflineAddressBook |
Which address book each database is pointed at |
Get-Mailbox -Arbitration |
The arbitration mailboxes, one of which performs generation |
Reading the client side honestly
Outlook downloads the address book on its own schedule, not on demand, so a server-side fix does not show up immediately. Force it from Send/Receive on a test machine rather than waiting, and remember that only cached-mode profiles download one at all. Deleting the local address book folder under the user’s Outlook application data forces a full download next time, which is a reasonable client-side test – but if you find yourself doing it on more than a couple of machines, the fault is on the server and you are treating symptoms.
The two companion codes
| Code | What is published |
|---|---|
0x80072EFD |
Win32 12029, ERROR_INTERNET_CANNOT_CONNECT: the attempt to connect to the server failed. Microsoft’s Windows Update guidance attributes the same code to firewall rules or proxies blocking the connection |
0x80190194 |
Nothing. It appears in HTTP-carried failures and Microsoft publishes no meaning for it |
If a client is showing 0x80072EFD rather than 0x8004010F, stop looking at the address book. The connection did not complete, so nothing on the server can be at fault yet. Test the same URL from a browser on that machine, and look for a proxy, an inspection appliance or a VPN that is in the way.
When everything checks out
- Confirm the certificate covers the OAB URL names and that the chain is served, because a missing intermediate fails on some clients and not others.
- Confirm the OAB virtual directory exists on the servers clients are actually being sent to, not only on the one you have been working on.
- Confirm the address book has actually been generated since your last change, rather than assuming the update command finished.
- Test the URL from a client machine, not from the server, so you are testing the path as well as the endpoint.
- Check whether a group policy is pointing Outlook at a fixed configuration that overrides what Autodiscover returns.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x8004010F |
MAPI_E_NOT_FOUND: the requested object could not be found at the server. Outlook shows it as “Outlook data file cannot be accessed” or “The operation failed. An object could not be found”, and Microsoft’s article for those strings names a corrupted profile as the cause | Microsoft Learn |
0x80190194 |
Seen in HTTP-carried download failures. Microsoft publishes no meaning for this code; treat it as a symptom and test the URL directly | not published by the vendor |
0x80072EFD |
Win32 12029, ERROR_INTERNET_CANNOT_CONNECT: the attempt to connect to the server failed. Microsoft attributes the same code to firewall rules or proxies blocking the connection | Microsoft Learn |
Confirm the fix worked
- A new Outlook profile on an affected machine downloads the address book successfully.
Get-OfflineAddressBook | Format-List Name,IsDefaultshows exactly one default.- Requesting the OAB URL from a browser on a client machine returns content rather than a not-found page.
Get-MailboxDatabase | Format-List Name,OfflineAddressBookshows every database pointed at a book that exists.- An affected user’s Outlook shows a recent successful address book download in Send/Receive rather than an error.
Questions people ask about this
Does this cost anything to fix?
No. The offline address book, its distribution point and the cmdlets that manage them are all part of Exchange. The only spend that can appear is a certificate covering the OAB URL names, and that comes from a certificate authority.
Why does Microsoft’s page for this code talk about Outlook profiles?
Because the code is general. 0x8004010F means the requested object could not be found at the server, and one common way to produce that is a corrupted profile pointing at a data file or configuration that is no longer valid. It is why the profile test belongs first when a single machine is affected.
Only some users are affected. Where do I look?
At what they have in common. If they share a database, check the address book assigned to that database. If they share a site or a network path, check the URL and the certificate. If they share nothing, check their profiles.
How long does a regeneration take?
It depends on the size of the directory, and on a large organisation it is not quick. Let it finish rather than starting it again, and confirm from the Application log that it completed before you judge the result.
Is deleting the local address book folder safe?
Yes, as a client-side test. Outlook rebuilds it on the next download. It is a reasonable thing to try on one machine and a poor thing to script across an office, because it forces every client to download the whole book at once.
