Link to home
Start Free TrialLog in
Avatar of tabran
tabran

asked on

Exchange 2010 OAB Never Downloads to Outlook

I have a recently deployed Exchange 2010 server, currently co-existing with a Exchange 2003 server that will soon be decommissioned.  All mailboxes have been migrated to 2010, as have replicas of all Public Folders.  Problem is, I have a few misc Outlook clients (2003-2010) that are not receiving updates to the Offline Address Book.  For example, a Outlook 2010 client that I tested, doing a manual Send/Receive of OAB results in the progress stalling at "Processing."  Knowing that for Outlook 2007-10 the OAB is downloaded from Exchange 2010's Default Website's OAB directory, I tried opening https://SERVERNAME/OAB to which I received a 500.19 - Internal Server Error.  (The requested page cannot be accessed because the related configuration data for the page is invalid.)  I thought I found my answer when I came across this article:  http://www.confusedamused.com/notebook/oab-never-downloads-for-outlook-2007-clients-with-exchange-2007-on-server-2008/

I had, in fact, setup redirection for my default website per TechNet:  http://technet.microsoft.com/en-us/library/aa998359.aspx  and was careful to disable redirection for the OAB virtual directory.  But when I followed the article's suggestion, and from Windows Explorer modified the Security Permissions for the web.config file in the C:\Program Files\Microsoft\Exchange Server\ClientAccess\OAB folder to add Authenticated Users read and read and execute permissions, I still had the OAB issue, and my redirection stopped working for the entire default website.  Per one of the comments on the ConfusedAmused article, I even tried adding the same permission to the NETWORK SERVICE account to the same results.  I'd be grateful to any suggestions on how to resolve my issue.

Thanks in advance,

T
Avatar of MegaNuk3
MegaNuk3
Flag of United Kingdom of Great Britain and Northern Ireland image

If it is only a few clients with the issue and others are working fine, then it seems like a client side issue to me.

Try closing outlook then deleting the local OAB files in the profile
Avatar of tabran
tabran

ASKER

Thanks for the suggestion MegaNuk3,  

To test, I opened one of the affected user's Outlook (2003) profile directories \Documents and Settings\<Windows alias>\Local Settings\Application Data\Microsoft\Outlook\ and deleted *.OAB.  (Note that the time stamp on these files showed they hadn't been updated since the Exchange 2010 migration.)  I then re-opened Outlook and tried a Send Receive of the OAB with the same results:  A stall on "Processing" on the progrss bar.  (see image)  In addition, a check of the directory showed no recreated OAB files.

Next, I tried creating a new/separate mail profile on the same PC (leaving the existing one in place) and waited for all the first time offline syncing (new OST, etc) to complete.  I still found no OAB files in the Outlook directory.  Forcing and Send Receive of the OAB produced the same results, another stall of the progress bar.

I happy to try any additional suggestions.  Many thanks!
-T

 User generated image
Try creating a new test user with a mailbox, log onto the machine with the issue and create an outlook profile and see if it is able to download the OAB.

If it can then that rules out the machine as being the issue
Avatar of tabran

ASKER

I created a new, native, Exchange 2010, mail user.  Then created a new Outlook profile for the user on the same test workstation:  Same results--No OAB file and stall on Send Receive of OAB.  Looks to me like it is a server issue, specifically with the web-based distribution of the OAB as it looks like my issue is limited to Outlook 2007-10 clients.  (I had misreported above that my test workstation was Outlook 2003, when it was actually 2007.)  Again it seems to me like I should be able to open  https://SERVERNAME/OAB from a web-browser without getting an error...
Are all Outlook 2007 / 2010 clients affected?

What happens if you go into EMS and do:
Test-outlookwebservices | fl
Avatar of tabran

ASKER

Yes, it appears that all Outlook 2007/10 clients are affected.

Test-outlookwebservices | fl  resulted in:  "WARNING: An unexpected error has occurred and a Watson dump is being generated: Failed to fine the mailbox.  Mailbox = 'extest_5115f74fd3f04@DOMAIN'
Try
Test-OutlookWebServices "<valid internal email address/ alias>" | fl
For example:
TestOutlookWebServices "me@Microsoft.local" | fl

It might also be worth looking in \\<OAB generating server>\OAB to see if the files  in there are recent, they should be less than 24 hours.

How many CAS servers do you have?
Do start-->Run-->\\<OAB generating server>\OAB and press enter, this is different to checking the URL because the URL points at the CAS server and the location above points at the OAB Generation server, which is normally a mailbox server.
Avatar of tabran

ASKER

The web services test completed with all SUCCESS or normal sounding informational responses, including those dealing specifically with OAB and the autodiscover.

The \\SERVER\ExchangeOAB share and it's contents look normal and current, with recent time stamps.  (Note that the name of the share in my instance is ExchangeOAB, not OAB)

This is the only CAS server for the domain, excluding the legacy Exch2003 server, which is yet to be decommissioned.  This 2010 server has all the roles so it is generating and distributing the OAB.

Thanks for your continued help

Note that
Ok, do
Get-offlineAddressbook |fl
And post the result after substituting your server names etc.

If you go here on your CAS:
C:\Program Files\Microsoft\Exchange Server\ClientAccess\OAB\<GUID> folder are all the files recent including the OAB.XML ?
ASKER CERTIFIED SOLUTION
Avatar of tabran
tabran

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks for the update and final solution. Feel free to close/delete the question.

Have you tried turning SSL on the OAB VD back on? Are you using a self signed cert or 3rd party one?
Avatar of tabran

ASKER

Yes, I have since turned SSL back on and it still seems to work.  I am using a 3rd party UCC cert.

Thanks again
No problem, I'll keep an eye out for issues like this.
Avatar of tabran

ASKER

Called MS tech support