Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

About 6 months ago we upgraded our excahnge server from 2003 to 2010. i have read http://serverfault.com/questions/95383/0x8004010f-when-downloading-exchange-offline-address-book and found that this issue is the same as what i am having.

I have also read the blog at http://blogs.msdn.com/b/dgoldman/archive/2007/05/09/after-installing-an-exchange-2007-server-in-to-a-mixed-site-the-oab-generation-fails-with-error-9342-and-outlook-clients-fail-to-download-the-oab-with-error-0x8004010f.aspx

The problem is that i cannot use this method because the 2003 exchange server has been decommisioned (properly).

Is there another solution so that this sync error can stop occuring?

Thanks

share|improve this question
add comment

2 Answers 2

I've had to deal with similar issues, which I have been able to resolve, but not definitively enough to give an exact solution. You can start, however, by recreating the OST file. Just close Outlook, delete or rename the OST file, and then open Outlook back up. It will recreate the file. You can also try to completely recreate the mail profile. Finally, you can try to turn logging off (or on and then back off). Here are some instructions for doing that.

If none of that works, try turning off cached mode and see if the error still occurs. That's not a solution, but it might help to see if you should look more into Outlook or Exchange.

share|improve this answer
    
I have ahad a look a bit further and have discovered that the user is not the only person receiving the email. However this user was using folder view which shows sync issues and conflicts. It is actually happening across all users. With recreating the OST it happens when this user logs onto a new machine that they havent logged onto before. So this would be a new profile. –  JohnyV Jun 30 '10 at 22:23
add comment
up vote 0 down vote accepted

I found out that there was a problem from when we removed our old exchange server from the network. The offline address book needed to be recreated. it was done through powershell. I dont know the exact commands but it stopped this error from happening to all users. It wasnt actually outlook at all.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.