Wednesday, March 05, 2008

Microsoft Exchange 0x8004010F error

I had a friend call me asking me about a problem that he was having where he did a migration of users from one exchange server to another and removed the original exchange server from the domain.
He removed the server properly through demotions but the outlook clients would always give an 0x8004010F error when they did a send and receive.
This error relates to the offline address book that the server holds for clients, when he moved the users the address book was still caching entries from the original server.

Error Message:

When you try to synchronize the offline address list on a Microsoft Exchange Server “0x8004010F An object could not be found”

If you try to send an e-mail message after you receive this error message, you may receive the following error message in Outlook 2003:
Task ‘Microsoft Exchange Server’ reported error (0x8004010F): ‘The operation failed. An object could not be found.’

I’ve linked to the KB article below that you need to finish off, but basically you need to follow the steps below first.
Exchange System Manager -> Offline Address Lists -> (Delete) “Default Offline Address List”
Once this has been removed you will need to add it again, this is done with the following steps:
Right Click “Offline Address Lists” -> New -> Offline Address List -> make the name “Default Offline Address List” ->
Choose your offline address list server as the exchange server -> click next -> Select the address list as the “default global address list” -> Next**
-> Finish

**Note the message here where it says “The Public folder that will contain this Offline Address List will be created during store maintenance period on [servername]. Therefore this Offline Address List will not be available to clients until that time.
- This message indicates that the rebuild will not occur until the maintenance cycle and for most people that will mean, come back tomorrow.

This KB Link is only relevant if the above did not fix your issues, depending on how you went about the removal the below may or may not be applicable.
MS KB Link
Microsoft KB 905813

Posted by admin in • Exchange
Page 1 of 1 pages