Error 0X8004010F A server (URL) could not be located
I have this on both a test clean Exchange 2007 installation and another one that is part way through migration from Exchange 2003. Using Outlook 2007 (or 2003) on a machine that is not part of the domain gives this sync error. 11:20:06 Microsoft Exchange offline address book 11:20:06 Not downloading Offline address book files. A server (URL) could not be located. 11:20:06 0X8004010 If I join the PC into the domain the error goes away. The OAB is at https://server_name/OAB/64228a00-66ea-4c25-aca0-df6e18a6cbe4/oab.xml I can access this without any problems both internally and externally on the same url both using http and https. I get the pages of XML that you'd expect. I've tried changing the URLs under Server Configuration > Client Access > Offline Addressbook Distribution but nothing I try can make this work on machines that are not in the same domain as the Exchange server. Any ideas??
January 18th, 2007 7:49pm

I have the sam issue with you,but only for outlook 2007. After I references Exchange 2007 Offline Address Book Web Distribution know outlook 2007 need autodiscover Service Connecion Point(SCP),so I create Autodiscover A record in my AD DNS and point to my Exchange 2007 CAS IP.Later,no error anymore in my outlook 2007 OAB sync 0x8004010. Note:Before Autodiscover service can successfully runing,you need config you CAS to use Certificate.For more information please see http://technet.microsoft.com/en-us/library/aa995942.aspx
Free Windows Admin Tool Kit Click here and download it now
January 19th, 2007 9:09am

Hi Jammy,Would that be means I need to create DNS CNAME entry autodiscover and pointing that record into my Exchange Server CAS ?I did ran:Test-OutlookWebservices from Powershell and here's the Error message:Id : 1019Type : InformationMessage : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://<servername>.domain.com.au/Autodiscover/Autodiscover.xml. <?xml version="1.0" encoding="utf-8" ?> - <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">- <Response>- <Error Time="16:15:08.5937500" Id="1433479874"> <ErrorCode>600</ErrorCode> <Message>Invalid Request</Message> <DebugData /> </Error> </Response> </Autodiscover>Id : 1013Type : ErrorMessage : When contacting https://<servername>.domain.com.au/Autodiscover/Autodiscover.xml received the error The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LFId : 1006Type : ErrorMessage : The Autodiscover service could not be contacted.
May 7th, 2008 10:30am

Hi Albert, I'm not sure create CNAME Autodiscover record in your DNS Server can workround this issue. Suggest you replace CNAME record with A record (Autodiscover) and point to Client access server role IP. Besides, you need add Autodiscover FQDN in Client access server certificate when enroll new one(Use New-ExchangeCertificate - Domain parameter).
Free Windows Admin Tool Kit Click here and download it now
May 7th, 2008 2:49pm

Hi Jammy,Do i have to install wild card SSL with these entries:autodiscover.domain.comwebmail.domain.comservername.domain.com?in order for your workaround to be working ? I had created A Record of "Autodiscovery" to point to Exchange Server IP Address.but eventhough I accept that self signed certificate, my Outlook 2007 still give me this error message:"Task 'Microsoft Exchange' reported error (0x8004010F) : 'The operation failed. An object cannot be found.'".
May 8th, 2008 9:36am

Certificates function very differently in Exchange 2007. The most straightforward means of addressing this issue is to get a UCC certificate from one of the few providers that offer them (I used GoDaddy, but it's not been smooth sailing). However, if you want to use self-signed certificates, there's a workaround in which you breakout some of the Exchange subsites as their own websites and issue your own certs for those new sites (see "Microsoft Exchange Server 2007 Implementation and Administration", published by Sybex, starting on page 460). Good luck. Benjamin Rutledge
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2008 7:33pm

To All experts, I've installed the UCC Certificate from COMODO, it has autodiscover.domain.com servername.domain.com imail.domain.com as the SAN, but still the problem exist. here's my track of work so far to get rid of this error: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3302603&SiteID=17 and also http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3383032&SiteID=17 Hope that helps.
June 25th, 2008 6:08am

Sorry to keep answering your question with a question, but let's talk FQDNs... You have imail.domain.com and servername.domain.com on your UCC. Is servername.domain.com your internal or external FQDN? For your certificate to do you any good, you have to have your internal FQDN on the UCC (i.e. servername.internaldomain.local). It's also been recommended by others that you additionally have just your internal domain name (i.e. internaldomain.local) on the UCC. I have not found this to be necessary, but I'm not entirely done with my testing. Additionally, just to let you know, I had some issues with the Autodiscover service. Outlook Anywhere is not as simple as RPC-over-HTTPS used to be with Exchange 2003. Those who use my Exchange server whose clients aren't members of my domain couldn't use NTLM authentication--they had to use Basic authentication. Indications are that my firewall may be alterning the NTLM traffic, but I can't find anything that supports that claim for my specific firewall. Finally, what is the CN of your UCC? It's very important that the CN be the external FQDN that your users will use to connect their Outlook clients to the Exchange server. Hope this helps.
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2008 10:38pm

Capt, servername.domain.com --> internal name FQDN for your statement of "you have to have your internal FQDN on the UCC (i.e. servername.internaldomain.local)." do i have to update my certificate to include servername.internaldomain.local ? at the moment I've got: imail.domain.com autodiscover.domain.com servername.domain.com the CN is imail.domain.com which is the CNAME of the servername.domain.com any idea ? thanks for replying to this case.
August 20th, 2008 9:12am

Albert, Yes. In Exchange 2007, you do have to also have your internal FQDN (servername.internaldomain.local) as one Subject Alternate Name (SAN) on your UCC. It's an entirely new requirement. Good luck. Benjamin
Free Windows Admin Tool Kit Click here and download it now
August 21st, 2008 6:32pm

i solved this problem so , i changed CAS ip for clients. you can see on this link.http://www.nadirterzi.com/ntblog/?p=38
January 14th, 2009 4:07pm

Volcano, your solution works only for machines that are joined to the domain. For workgroup clients, it doesn't. I'm having this problem on Outlook 2007. Any help would be greatly appreciated.Regards
Free Windows Admin Tool Kit Click here and download it now
February 23rd, 2009 6:25pm

I solved my issue by creating a A record in the dns for autodiscover pointing to my CAS.
February 25th, 2009 12:52pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics