When trying to download the Offline Address Book, it fails with error '0x8004010F object cannot be found'. The article : 905813 seemed to address the problem, but the solution did not work. I have searched TechNet, and not found any further articles. My Outlook clients show no public folders, which I find strange. I moved the 'Public Folder Database' from the Second Storage Group to the first, thinking that would help, but it is still listed in the EMC under the Second Storage Group, but the file path is the First Storage Group, which is even more odd. Any assistance would be greatly appreciated. Paul

What is your topology?Is it SCC? Windows server 2008?

Thanks Tariq, I am using Windows Server 2003, 64bit, and Vista clients.

Hi, I would like to explain that by default the Microsoft Outlook 2007 clients will use the OAB Version 4 and will download their Offline Address Book files from a virtual directory on a web server that has been advertised as a Web Distribution server. Thus, please help me gather the following information: 1. Whether all the Outlook 2007 clients encountered the problem? 2. I would like to explain that some users got error 8004010F when clicking Send/Receive. Sometimes, the error 8004010F is not related to the OAB, but related to the profile or the OST. So, please ensure that the error occurs when downloading OAB file. 3. Run the following command and post the result here: Get-OfflineAddressBook |fl 4. Please check the Mailbox Mode by using following method: a) Tools->Account Settings b) Select the Email Account and click Change c) Click More Settings d) Under Advanced tab, please let me know the Mailbox Mode Mike

Mike, Thanks for your attention to this thread. 1. Yes, all clients are encountering the same problem. 2. Yes, it occurs when downloading the OAB file. 3. Get-OfflineAddressBook | FL Server : PAVIL2AddressLists : {Default Global Address List}Versions : {Version3, Version4}IsDefault : TruePublicFolderDatabase : PAVIL2\Second Storage Group\Public Folder Dat abasePublicFolderDistributionEnabled : TrueWebDistributionEnabled : FalseDiffRetentionPeriod : 30Schedule : {Sun.5:00 AM-Sun.5:15 AM, Mon.5:00 AM-Mon.5:1 5 AM, Tue.5:00 AM-Tue.5:15 AM, Wed.5:00 AM-We d.5:15 AM, Thu.5:00 AM-Thu.5:15 AM, Fri.5:00 AM-Fri.5:15 AM, Sat.5:00 AM-Sat.5:15 AM}VirtualDirectories : {}ExchangeVersion : 0.1 (8.0.535.0)MinAdminVersion : -2147453113AdminDisplayName : Name : Default Offline Address BookDistinguishedName : CN=Default Offline Address Book,CN=Offline Ad dress Lists,CN=Address Lists Container,CN=IP3 Inc,CN=Microsoft Exchange,CN=Services,CN=Con figuration,DC=IP3Inc,DC=localIdentity : \Default Offline Address BookGuid : 2c23bd07-ac70-463e-b6ef-b1bf1e9d775bObjectCategory : IP3Inc.local/Configuration/Schema/ms-Exch-OABObjectClass : {top, msExchOAB}WhenChanged : 8/8/2008 10:22:31 AMWhenCreated : 8/11/2007 3:30:40 PMOriginatingServer : Pavil2.IP3Inc.localIsValid : True 4. Outlook is running in Unicode mode against Microsoft Exchange. Thanks again Mike. Loof forward to your reply. Paul

Hi Paul, From the information, I notice that the Web Distribution is disabled on the Offline Address Book. WebDistributionEnabled: False Paul, please understand that Outlook 2007 needs to have Web Distribution enabled to download OAB. Thus, please enable Web Distribution of the OAB: 1. Open EMC->Organization Configuration->Mailbox 2. Under Offline Address Book tab, double click the Default Offline Address Book 3. Under Distribution tab, please select Enable Web-based distribution and click Ok 4. After that, please right click the Default Offline Address Book and click Update. 5. Then, please check whether the following share folder is created on the OAB generate mailbox server: C:\Program files\Microsoft\Exchange Server\ExchangeOAB 6. If the OAB file is generated, please restart the Microsoft Exchange File Distribution service on the Client Access Server and then check whether the OAB file has been replicated to the C:\Program files\Microsoft\Exchange Server\Client Access\OAB on the Client Access Server. 7. If the OAB file has been replicated to the Microsoft\Exchange Server\Client Access\OAB, please logon on Outlook 2007 to check whether the OAB download issue still persists. Mike

Hi Mike, I was not aware that Web Distribution was required for 'local' clients. Previously, web distribution was enabled for the OAB, but I disabled it to try and resolve the problem. I have followed your instructions, and the Exchange OAB Folder is shared in Exchange Server. The contents of this folder is replicated in the OAB folder of the Client Access folder of Exchange. Specifically, the folders contain a folder with a cryptic numeric name (which I cannot paste here). This folder contains several LZX files, also with cryptic numeric names, and one XML document titled oab. Unfortunately, Outlook clients still fail to download the OAB with the same error message. Curiously, this morning prior to reading your post, I examined the IIS Configuration and found the MSExchangeAutodiscoverAppPool to be stopped with an Unspecified Error. I restarted it, but still no success with the OAB. How is this related? Thanks again for your attention to this post. Paul

Hi Paul, I understand that the OAB has been generated by the Exchange Mailbox Server Role and replicated to the CAS server. Nevertheless, the OAB still cannot be downloaded. In addition, you notice that the MSExchangeAutodiscoverAppPool is stopped. Paul, I would like to explain that the Outlook 2007 needs to connect to Autodiscover service to get the URL for the OAB. Thus, I believe that it is related to the OAB download issue. At this time, please attempt the following method to troubleshoot the issue: Step 1: ===================== 1. Start Outlook, right click the Outlook 2007 icon and click Test E-mail AutoConfiguration 2. Select Use AutoDiscover only 3. Type in the user name and password, click Test 4. Please check whether we can connect to the Autodiscover service and obtain the OAB URL If we cannot connect to Autodiscover service or fail to obtain the OAB URL, please run the following command on the Exchange Server to check the Outlook Web Services Step 2: ====================== Open EMS and run the following command: Test-outlookwebservices |fl Please post the result here By the way, Paul, I understand that you have attempted the steps in the KB905813 to configure the mailbox store point to the correct OAB. I also suggest that you dismount and re-mount the mailbox store to make sure that the change of the OAB for the mailbox store had been taken effect. Please also force AD replication between DCs. Mike

Hello Mike, Thanks again for your help. I was not able to complete Step 1, item 1 of your post. With outlook started, I was not able to find the Test Email Autoconfig option on any Outlook icon, nor was I able to with outlook closed. I did run step 2, and the output is as follows: Id : 1003Type : InformationMessage : About to test AutoDiscover with the e-mail address Administrator@ip3i nc.com. Id : 1007Type : InformationMessage : Testing server Pavil2.IP3Inc.local with the published name https://pa vil2.ip3inc.local/EWS/Exchange.asmx & . Id : 1019Type : InformationMessage : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://Pavil2.IP3Inc.local/Autodiscover/Autod iscover.xml. Id : 1013Type : ErrorMessage : When contacting https://Pavil2.IP3Inc.local/Autodiscover/Autodiscover .xml received the error The underlying connection was closed: An unex pected error occurred on a send. Id : 1013Type : ErrorMessage : When contacting https://Pavil2.IP3Inc.local/Autodiscover/Autodiscover .xml received the error Authentication failed because the remote part y has closed the transport stream. Id : 1006Type : ErrorMessage : Failed to contact AutoDiscover Obviously we are on the right track. I did dismount and remount the mailbox store. Also, IIS reports the MSE Autodiscover AppPool is now stopped with Undisclosed error. The Event Viewer App Log shows the 12014 error, an event 107 warning, and a 4001 error, but I believe those are related todismounting the mailbox store. Thanks again for your attention to this post. I look forward to hearing from you. Paul

Apaullo I am having the EXACT same problem as yourself. Also my "Test-OutlookWebServices | fl" results are identical to yours.I've been running like this for over 9 months because it is not causing connectivity issues for any users. Autodiscover is working like a charm, as well as all Exchange features, except for this error.I'm in the dark on this one.EDIT: I should note that I'm running a hosted Exchange environment.

Hi Paul, After some search regarding the issue, I noticed that the issue may relate to the certificate of the Web Site. (I am able to reproduce your issue after removing the certificate in my test environment) Thus, I suggest that you remove and recreate a certificate for the Web Site to troubleshoot the issue. Note: By default, a self-signed certificate is enabled on the Default Web Site. Nevertheless, according the following article, we recommend that you use a certificate from a public CA for the Autodiscover. The best practice for this is to use a public CA that is trusted by all clients by default. Certificate Use in Exchange Server 2007 http://technet.microsoft.com/en-us/library/bb851505(EXCHG.80).aspx Regarding the Certificate for Autodiscover service, I also suggest that you read the following article: White Paper: Exchange 2007 Autodiscover Service http://technet.microsoft.com/en-us/library/bb332063.aspx After that, please run the command to test the issue again. In addition, regarding the Test E-mail AutoConfiguration, I have provided more detailed steps below: 1). Launch Outlook 2007 using any profile.2). Hold down the CTRL key on your keyboard and click the Outlook icon in the notification area of the Windows taskbar, also known as the notification area.3). In the menu that appears, click Test E-mail AutoConfiguration.4). Enter your E-mail Address and Password (if not logged into the domain) in the respective edit boxes.5). Choose the desired auto configuration methods with Use Autodiscover, clear other selection.6). Click Test. Mike

Mike,I don't wish to hi-jack this thread concerning Paul's problem, but having the same issue as him I'd like to report that testing autodiscover from Outlook 2007 works correctly. Both RPC and HTTP protocols are responding.

Mike, Thanks again for hanging in there. I shortcutted your suggestion and enabled IIS with the Enable-ExchangeCertificate -services IIS commandlet. Ran the Test-OutlookWebServices commandlet and Id : 1003Type : InformationMessage : About to test AutoDiscover with the e-mail address Administrator@ip3i nc.com. Id : 1007Type : InformationMessage : Testing server Pavil2.IP3Inc.local with the published name https://pa vil2.ip3inc.local/EWS/Exchange.asmx & . Id : 1019Type : InformationMessage : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://Pavil2.IP3Inc.local/Autodiscover/Autod iscover.xml. Id : 1018Type : InformationMessage : The SSL certificate on pavil2.ip3inc.local is self-signed. Id : 1013Type : ErrorMessage : When contacting https://Pavil2.IP3Inc.local/Autodiscover/Autodiscover .xml received the error The remote server returned an error: (503) Se rver Unavailable. Id : 1006Type : ErrorMessage : Failed to contact AutoDiscover Of course, testing the Email Autoconfiguration and downloading the OAB still fail. The test email autoconfig log listed several 0x800XXXX errors. Reviewing IIS the certificate is valid, but not trusted. This should be OK as it is self signed. Reviewing the server unavailable problem, I wonder if this is applicable: http://blogs.msdn.com/rakkimk/archive/2007/06/09/problems-with-32-bit-asp-net-2-0-dlls-on-a-windows-2003-server-64-bit.aspx This is starting to converge with my other post regarding my Linux/Qmail send connector. Any assistance is greatly appreciated. Paul

Hi Paul, Thanks for your response and information. From the latest information, the issue seems relate to the MSExchangeAutodiscoverAppPool stopped. I would like to know whether the autodiscover issue can be temporarily solved after starting the MSExchangeAutodiscoverAppPool. If the issue still persists, please also check whether the MSExchangeAutodiscoverAppPool stops again automatically. If the MSExchangeAutodiscoverAppPool stops again, would you please check event log for any related error regarding MSExchangeAutodiscoverAppPool. In addition, please run the following command to check whether the new created self-signed certificate is correct: Get-exchangecertificate <thumbprint of the self-signed certificate> |fl Mike

Mike, Thanks again for your attention to this post. I am relatively confident at this point that the problem rests with my IIS, as I cannot get it to serve a page locally. After restarting and testing as requested, the AutoDiscoverAppPool still shows as running. Checking the event log, the Application and System log shows several errors. The Application log lists 2274 and 2268 , failure to load ISAPI filters C:\Windows\Microsoft.Net\Frameworkv2.0.50727\aspnet_filter.dll 'current configuration only supports AMD64' - thus giving credence to the thread referenced in an earlier post. The System log lists StsAppPool1 error 6824, 5424, 7104, 3960 and 6148 before being automatically disabled. Changing IIS Web Service Extensions to allow All Unknown ISAPI Extensions, restarting W3SVC, and retesting Autodiscover results in the same set of errors, and the AutoDiscoverAppPools stop automatically. The ExchangeCertificate is as follows: AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, Syst em.Security.AccessControl.CryptoKeyAccessRule, System.Se curity.AccessControl.CryptoKeyAccessRule}CertificateDomains : {Pavil2, Pavil2.IP3Inc.local}CertificateRequest : IisServices : {IIS://Pavil2/W3SVC/1}IsSelfSigned : TrueKeyIdentifier : D9720699ACF85960D4B67EE157BB19166F406C2BRootCAType : NoneServices : IMAP, POP, IIS, SMTPStatus : ValidPrivateKeyExportable : FalseArchived : FalseExtensions : {System.Security.Cryptography.Oid, System.Security.Crypt ography.Oid, System.Security.Cryptography.Oid, System.Se curity.Cryptography.Oid}FriendlyName : Microsoft ExchangeIssuerName : System.Security.Cryptography.X509Certificates.X500Distin guishedNameNotAfter : 8/8/2009 4:16:49 PMNotBefore : 8/8/2008 4:16:49 PMHasPrivateKey : TruePrivateKey : System.Security.Cryptography.RSACryptoServiceProviderPublicKey : System.Security.Cryptography.X509Certificates.PublicKeyRawData : {48, 130, 3, 9, 48, 130, 1, 241, 160, 3, 2, 1, 2, 2, 16, 161...}SerialNumber : A178010BE60BD6A44878963C7674DF10SubjectName : System.Security.Cryptography.X509Certificates.X500Distin guishedNameSignatureAlgorithm : System.Security.Cryptography.OidThumbprint : B1FE26279C9BBCF8BB6DC0FA1C97A357447A0A0AVersion : 3Handle : 488261456Issuer : CN=Pavil2Subject : CN=Pavil2 This certificate was cloned from the original self signed. I am still troubleshooting the IIS issues. I am going to revisit the earlier post, as I am using Windows Server 2003 64bit. Again, your assistance is greatly appreciated. Paul

Paul,What are you doing to troubleshoot IIS? I'm in the same boat with my server unable to serve a page locally. I'm not sure where to start troubleshooting.

You know the story; Technet articles, etc. If I find anything that does the trick I will post. What is your environment; server OS? I think the blog that I included in the earlier post is relevant, because I am in Win2003 64bit. Good Luck

Hi Paul, After some researching regarding the issue, I notice that the event 2274 and 2268 may occur that 32-bit version of ASP.NET was running as the previous blog indicated. Please perform the following method to troubleshoot the issue: 1. Click Start, click Run, type cmd , and then click OK. 2. Type the following command to disable the 32-bit mode: cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0 3. Type the following command to install the version of ASP.NET 2.0 and to install the script maps at the IIS root and under: %SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -ir -enableNOTE: This is the same command that is run during Exchange Server Setup 4. Make sure that the status of ASP.NET version 2.0.50727 is set to Allowed in the Web service extension list in Internet Information Services Manager. Note: The build version of ASP.NET 2.0 may differ depending on what the currently released build version is. These steps are for build version 2.0.50727. For more detailed steps, please refer to the following KB article: http://support.microsoft.com/kb/894435/en-us After performing the above steps, please check the Autodiscover issue again. Mike

This just kicked everyone off my server and killed mail transfer. Rebooting didn't fix it.PLEASE HELP!EDIT: The following Application Pools are stopping themselves with an "Unspecified Error"...DefaultAppPoolMSExchangeOWAAppPoolMSExchangeSyncAppPool

Ente wrote: This just kicked everyone off my server and killed mail transfer. Rebooting didn't fix it.PLEASE HELP!EDIT: The following Application Pools are stopping themselves with an "Unspecified Error"...DefaultAppPoolMSExchangeOWAAppPoolMSExchangeSyncAppPoolEmergency resolved. I ran the following command from the above support page after a reboot:%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i

Mike, Like a key in a lock, Autodiscover is working like a charm. OAB downloads like it should. IIS is serving pages as it should. I can't thank you enough for your help, and your patient persistance. You are a true professional and a valuable asset to Microsoft. Paul