Click to Rate and Give Feedback
TechNet
TechNet Library
Exchange Server
Troubleshooting
 Troubleshooting Error 0x8004010F Wh...

  Switch on low bandwidth view
Troubleshooting Error 0x8004010F When Outlook 2007 Clients Download OAB

Topic Last Modified: 2008-03-14

This topic provides information about how to troubleshoot error 0x8004010F when Microsoft Office Outlook 2007 clients fail to download the offline address book (OAB). You may receive the following error message: "Task ‘Microsoft Exchange’ reported error (0x8004010F): ‘The operation failed. An object cannot be found.’

This issue may occur when Outlook 2007 is started on a client that is not a member of a domain. The service connection point is not available to deliver the offline address book, and Outlook tries to locate the Autodiscover service by using Domain Name System (DNS). For Outlook to locate the Autodiscover service by using DNS, there must be a host record in DNS for the Autodiscover service that maps the entry point, or public IP address, to the Client Access server where the Autodiscover service is hosted.

To perform this procedure, the account you use must be delegated membership in the local Administrators group. For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.

To resolve this issue, add a host (A) record in DNS for Autodiscover.domain.com and point to the Exchange 2007 server that has the Client Access server role. For example, if the user’s primary SMTP address is user@contoso.com, the host (A) record you need to add is: autodiscover.contoso.com A <IPaddress>. For more information about adding a host (A) record, see Add a host (A) record to corporate DNS for a federation server.

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
DNS is OK but still same problem      Pezhman   |   Edit   |   Show History
Hi,

my DNS is working fine and where ever I installed outlook 2007, auto discoverer is also working fine but still when i try to download Offline Address Book it will give me same error message. What can be the problem?

Thanks,
Pezhman
Tags What's this?: Add a tag
Flag as ContentBug
Weaknesses in this article      Thomas Lee   |   Edit   |   Show History
This article could be improved.

a) Second paragraph, 2nd sentence begins "The service connection point is not available to deliver the offline address book". It would be useful to explain what the service connection point is and why it's not available. I think what this sentence is trying to say is that when you run outlook on a domain client, Outlook can access the AD to obtain Service connection point information - i.e. details of where Exchange is, and this information in turn can help you locate your correct Exchange server.
b) this paragraph should also point to more information about the service connection points. and to the Exchange Autodiscover feature (http://technet.microsoft.com/en-us/library/bb332063(EXCHG.80).aspx).
c) paragraph 2 should go on to say something like: 'under these situations, Exchange 2007 features an Autodiscover feature that Outlook can use to find Exchange. This autodiscover feature is implemented as a web service, which Outlook finds by using a specially constructed DNS domain name.
d) The end of the article talks about 'resolving the issue' - I think this shoudl be more "to enable Outlook on a non-domain joined machine' or somethng. After all, the issue is due to the computer not being a member of the domain - this underlying issue is NOT resolved by using autodiscover.

I've written a somewhat deeper blog article at: http://cacorner.blogspot.com/2008/07/exchangeoutlook-autodiscover-feature.html.

DNS is OK ... &amp; I have the same problem      PJ_Pistola ... Thomas Lee   |   Edit   |   Show History
I feal the issue is not due to DNS Autodiscover...

My Outlook 2007 is on a client that is not a member of the domain.
All reports run on Exchange 2007 indicate a functioning system except:
  • a certificate error (I have not yet added my WAN's external dns FQDN {but; Outlook is on the LAN} to the cert and it is a self generated cert.
It is also worth noting Outlook is on a wireless subnet different to the Exchange server. So the firewalls inspection has been turned off.

Hope this helps.
Configuring OAB to avoid 0x8004010F error      Tarka Dhall   |   Edit   |   Show History

I have had the same problem with the OAB 0x8004010F error. My environment is an Exchange 2007 machine which has been added to an existing Exchange 2003 organisation.

This is how I resolved the problem

I created an external host A record autodiscover.mydomain.com (where my domain.com is the customers domain)

The Exchange 2007 OAB had not been created, it was using an Exchange 2003 replica. I created the OAB using the Exchange 2007 Manager.

I then changed the OWA and OAB on Exchange 2007 to use https://autodiscover.mydomain.com as the external web address

I created and installed a Thawte SSL123 certificate for autodiscover.mydomain.com

I am now able to download the OAB using Outlook Anywhere.

As a user: How I fixed 0x8004010F      pepj   |   Edit   |   Show History
I'm not an admin on the domain, and I'm not sure that I could get our outsourced IT group to make this DNS change for me. I use my home computer a lot for work so I run into this since I'm running Vista Home Premium (can't join a domain), not having the ability to add a computer to our domain (since I'm not an admin), and not sure that I want to subject my home PC to the policies in force on the work domain.

Anyway, I edited my hosts file by going to Start > Run and using the following command:
notepad c:\windows\system32\drivers\etc\hosts

I then added a line at the bottom that looked something like this:
10.1.1.3autodiscover autodiscover.domain.com

In my case, I knew we had a pretty small Exchange deployment. I pinged the server that my Outlook is setup to use and used its IP address in the hosts file line above. Finally, I did have to accept the certificate because our IT group has installed a certificate that was not linked to the "autodiscover" name.
(Please note: The AD domain we use is domain.local. Using autodiscover.domain.local in here didn't work. According to the resolution in this article, I had to use the domain we use for email, which was autodiscover.domain.com.)
A fix for 0x8004010F      Josh Erickson   |   Edit   |   Show History
Not sure of the ports and services that need to be added to the firewall lists, but the issue seems to lie with MAPI access to your Enchange 2007 servers.

By turning off the firewall on your Exchange 2007 server that runs the MAPI services the issue will be fixed.
Processing
© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Page view tracker