Outlook 2007 Error During Send and Receive:The operation failed. An object could not be found.

Mindwatering Incorporated

Author: Tripp W Black

Created: 03/08/2009 at 06:02 PM

 

Category:
Microsoft Server
Mail / SMTP

Issue:
User receives a message when sending and receiving mail with his/her Exchange server. Sending and receiving mail is actually successful.
Error message:
Microsoft Exchange Server reported error (0X8004010F) The operation failed. An object could not be found.

Solution:
This is an off-line address list issue. (Default Offline Address List). There is a server side and a client side. The corruption may be on the client side only or you may have to do both sides.

To fix in Exchange 2007:
1. Open the Exchange Management Console.
2. Under Organization Configuration, click Mailbox.
3. In the Tools section on the right, under Default Offline Address List, click Update.
4. In the regeneration are-you-sure dialog, click Yes.

To fix in Exchange 2003:
1. Open the Exchange System Manager
2. Expand Recipients, click Offline Address Lists.
3. Right click Default Offline Address List, click Rebuild.
4. In the regeneration are-you-sure dialog, click Yes.

In Outlook 2003:
You need to replace the corrupt one. Perform the following:
Tools -> Send Receive --> Download Address Book --> click Download It.

This can also give same error message (with different numbers???) when:
  • An Archive Folder is corrupt or not available on the server anymore.
--> Example fix:
Create a new profile (bad -> clears all your customizations)
or
To remove the folder in Outlook, remove the folder name in regedit.
1. Start regedit
2. Search for the folder name as displayed in Outlook - it will likely be in a similar location to:
[HKEY_USERS\\ Software\Microsoft\Windows NT\ CurrentVersion\Windows Messaging Subsystem\ Profiles\\
3. Export the entire key of this PST folder.
4. Delete the entire key.
5. Close regedit
  • Outlook Form is corrupt.
--> Example fix:
FRMCACHE.DAT is corrupt. Rename to FRMCACHE.000. Outlook should create a new FRMCACHE.DAT resolving the problem. Search to find the problem.

previous page

×