0x8004010F - Offline Address List Error

Task 'Microsoft Exchange Server' reported error (0x8004010F): 'The operation failed.  An object could not be found.'

That is the error we get on our clients.  I went through some steps before posting that I saw on another person's post with the same error.  Those did not solve my problem.

When I go to ESM and go to the address book I can preview it so I went on to the next step with the walkthrough and it had me add some settings under public folders and OBA, but that did not fix the issue either.  I do not want to configure outlook to not download them, I want to solve the problem on the server.  

It is logging errors 9335 and 9333 with the issue.

I have rebuilt the address list but it did not solve the problem either.

Any help?
Who is Participating?

Have you checked this:
You receive an 0x8004010F error message when you try to synchronize the offline address list on an Exchange Server 2003 server in Outlook 2003

If you have followed steps on another post, then it would help if you indicated either what post it was, or what steps you followed. We are not mind readers.

It is usually down to a missing replica on the OAB system folders.

It would also help if you posted which element of the error log is generating the errors, whether it is the address book or something else.

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

lttechAuthor Commented:
None of those worked....

I am going to look a little further into http://support.microsoft.com/default.aspx?scid=kb;en-us;822444
which will help reset the system folders, but what could come of this (worst case)?
as the KB states

"If you change the administrative group system folder GUID, do not restore previous backups of any public folder store in your Exchange organization. If you do so, you may cause duplicate system folders to be created, cause existing system folders to be destroyed, cause the system folder server's public database to stop replicating permanently, or prevent other public stores in the site from accepting replicas of system folders. To correct such problems, you may have to remove and rebuild public folder stores on some or all servers in your Exchange organization. "
lttechAuthor Commented:
Sembee those are the exact instructions I followed before.  The application element of event viewer is logging the errors.
lttechAuthor Commented:
I will give the KB a try and see if it clears it up....
usally restarting the Information store service and running a fresh rebuild can help before you try anything else.
what is the description for the event ?

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.

All Courses

From novice to tech pro — start learning today.