Outlook 2k3 0x8004010F "Saving synchronization log"

I keep getting the above error message on a handful of clients.  The only way that I can get it to stop is to disable cache mode and the ost file.  I've even tried recreating a new ost file with no luck.  I've tried numerious things on the net and from Microsoft.  I tried disabling the offline sync of the Address book too.

Remember that this is not system wide but user specific.

Any help?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

This sounds like a permission or encryption problem.

Usually, outlook saves configuration settings and logs to
C:\Documents and settings\user name\application data\Microsoft\Outlook

Check the security settings of this folder aboce and the folder, Outlook stores the OST file (local settings\application data...) and compare them to systems, which will work correctly.

Also I have seen replication errors, if there are corrupted mails within the mailbox


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
User specific... does it follow the user to another machine?
If not, then it is something with that machine.

Follow the three steps to resolve the problem... one will resolve the issue.

1. Recreate Outlook profile - remember to remove the OST file before creating the replacement profile.
2. Recreate Windows Profile
3. Wipe machine

Reinstalling Outlook/Office doesn't usually help.
While wiping the machine may seem a little extreme - I am in the business of resolving problems in the fastest possible way to give a good chance of a success. If the problem doesn't follow the user, then wiping the machine and rebuilding it (which I can do in less than 2 hours from scratch, faster with deployment tools) is the fastest guaranteed solution.

If the problem does follow the user, but isn't system wide then you have to start looking at the account.

If you are using roaming profiles or any other technology that moves user data around with them no matter what machine they are using, then that needs to be disabled for the test of following the user or not to be valid.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.