I was advised to post this here vs Outlook 2013 regular forum.

Updating Address Book constantly showing / not able to download OAB - I'm worried this is also wasting battery on top of being just flaming annoying to always see.

Hardware:
Lenovo T430 (i5 2.5/8gb ddr3/500gb HDD)

Software:
Windows 7 Professional 64bit (also tried Win8 64bit Enterprise)
Outlook 2013 64-bit (15.0.4420.1017)
Exchange 2010

Running a manual download results in: Task 'username@domain.com' reported error (0x801901F4) - The Operation Failed

Works fine on my 2007/2010 Outlook. 

No errors running the Test E-mail AutoConfiguration 

Connection Status all shows Established with Negotiation / Encryption.

I've not found ANYONE else online with this issue; I found one from the preview period that reported similar issues, and the resolution was to delete the Outlook folder in appdata - this did not resolve it for me.

Consider trying Outlook 32-bit.

Hi,

Please also try Outlook online mode.

To be frank, I do not see the solution as being "Try a 32-bit application in the middle of your otherwise 64-bit environment"

We run 64-bit OS's, the (mostly) newest Exchange, and are field testing Windows 8 Enterprise.  Why would Microsoft release a product that is not compatible with current technology?  Unless you're simply offering trouble shooting steps, then it's possible I could find the 32-bit installer.  

Wendy, by 'online mode' are you saying to not utilize Cached Exchange mode?  

I find this also defeats the purpose of having technology that supports "Offline modes" but not utilizing it due to glitches.  When taking it out of Cached Exchange yes, the error goes away.  Because, it doesn't then cache anything / download offline address books.

Even if your not seeing this anywhere else it does seems to be SSL/EWS related - Is is just your user? Are autodiscover configured on your primary SMTP domain? Do you have a different domain? What does the IIS logs say?

Does Outlook use RCP or reverts back to OA?

You'll have to ask Microsoft.  How about trying Office 32-bit and report back if it works for you?  Then you'll know.

I"m having the same issue. One difference is that we are running exchange 2013 on Server 2012 Std.

Manual download of the address book so far is just hanging with no progress.

Another issue that I'm having that I suspect is related is that my send/receive isn't working properly, I didn't notice until I looked at my phone and saw that I had email on my phone that  hadn't come through in my Outlook client. Hitting the Send/Receive button did not download the new mail either. I had to close outlook and reopen it to get all my mail.

Deleting the Outlook folder in appdata did not work for me either.

I don't know if this will fix your issue, but one thing to try is to find the file C:\Program Files\Microsoft\Exchange Server\V14\OAB\web.config and grant the group Authenticated Users both Read and Read & execute rights on it.

There is no OAB folder under V15 (Exchange 2013). Is there a different solution we should try for Exchange 2013?

Clients seem to work fine for everything except downloading the GAL. Some of the clients are also connected to the other Exchange servers, and they get those GAL's just fine, so problem definitely seems to server-oriented or something peculiar to our configuration. If it matters, our Exchange is running on a 2-server DAG. Could the clients be talking to the wrong server for the GAL and something is getting confused?

Thanks,
Colin

Here's one article on configuring the OAB for web distribution.

https://technet.microsoft.com/en-us/magazine/ff381470.aspx

There are others.

As to the CAS servers being the same as the DAG, there is a potential issue.  This article describes it and how to work around it.

http://blogs.technet.com/b/exchange/archive/2012/10/26/oab-in-exchange-server-2013.aspx

FWIW, there are a lot of 3rd party applications, such as eFax, which don't work with 64 bit Office. As an IT consultant, I've learned over the last several years that it is simply more effective and reliable to only use the 32-bit version of Office, even in 64-bit environments. At some point, there may be an evolution to this, but even two years after you wrote this, it's still the case.

First I would verify that the OAB is associated with all your Exchange Databases. Then I would check your Autodiscover settings (all of them) for a bad setting. I have, on occasion, had to use ADSI Edit to fix Autodiscover as I found settings I could not appear to modify from ECP nor PowerShell.