Geeks With Blogs
Timothy Wright

So you just bought a shiny new Microsoft Exchange Server 2007 and got it all installed with everything working.
Outlook Web Access is a joy for all of the company users and the rediculously simple Outlook 2007 autodiscover configuration is making you look like a rock star.
You even get yourself a SANs certificate to overcome the problem with Outlook.

Then it happens....
Someone hits the little Send/Receive button in Outlook and the thing just hangs or you get the ubiquitous 0x8004010F error.
'Microsoft Exchange' reported error (0x8004010F) : 'The operation failed. An object cannot be found.'

After a little bit of research you're thinking... Noooo! The offline address book is broken or corrupt some replication has failed, but, of course, all diagnostics say you have the happiest Exchange server in the world.

Now what did I miss????

Well the answer to that question is probably nothing. You've just run into another one of those.. hmm... Lets call them, "Undocumented Features!".

In my case, everything was configured properly and then I stumbled upon this forum post where the final response gave me the solution I needed.

It was simply a matter of read permissions on a couple of files/folders.
Had to grant read permission on the webconfig and other content in my OAB virtual directory.

So for anyone else chasing their tail on this one. I hope this helps.

Posted on Thursday, March 5, 2009 11:11 AM | Back to top

Comments on this post: Exchange OAB Outlook Sync Trouble

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Timothy Wright | Powered by: