Outlook 2007 keeps updating inbox in cached exchange mode

I have an executive level user that has recently encountered a pretty strange problem with Outlook 2007 in cached exchange mode.  He's got a pretty big mailbox - about 4 gigs - which recently started a constant "updating inbox" sync routine even when he doesn't have any new messages available on the server. Unfortunately this pretty much renders Outlook useless for him performance-wise so the sooner the better in getting this issue resolved since i've had him set up in webmail the last few days while i've been troubleshooting.

Here's what we've tried so far:

* creating a new mail profile
* deleting and resyncing a fresh OST
* modifying some antivirus settings  -- we run ESET antivirus, and we checked the option to "disable checking upon inbox content change" after some research. this helped to speed the sync process up but it still continually starts and stops the sync.
* ran a repair of office
* uninstalled and reinstalled Outlook

At this point I'm beginning to think it's not a local issue at all and that it's something on the server, likely mailbox corruption. I ran a test PST export of his mailbox and in the Exmerge logs I am seeing thousands of records like this:

[21:55:35] Error copying message with subject 'Your Junk Mail Digest: xxxx@xxx.com' in folder '\Inbox'. (MAPI_W_PARTIAL_COMPLETION)

My question now is on the next step. If I run utilities such as ESEUTIL and/or ISINTEG, will that help to clean up the corrupted items in his mailbox? Is there a better way to identify corrupted items in a mailbox then just running Exmerge?

Thanks in advance for any help you can provide.

Who is Participating?
CompanionCubeConnect With a Mentor Commented:
Move the mailbox to a different mailbox store and try again - safe
Export the mailbox, delete the mailbox from the store, create a new mailbox, and Import back - caution!
Clean up the mailbox - time!
tombozzoAuthor Commented:
We are running the standard version of Exchange 2003 so we only have 1 information store. Seeing as this is the case, my next option should be to try and export, delete, and re-import the mailbox?

Is there any merit to running ESEUTIL / ISINTEG to try and fix corruption in the store?
Was trying to limit the disruption for ALL users to fix just ONE user ;-)

Before doing anything, please be sure you have a full Exchange Store BACKUP.

I would leave the ESEutil and ISInteg tools for last...


"Repairing Exchange databases with Eseutil and Isinteg can cause lost data in the Exchange databases you repair. For this reason, copy the database files you are repairing before attempting the repair process. (For information about how to copy your database files, see "Moving or Copying the Existing Versions of the Database Files That You Are Restoring (Optional)" in Recovering an Exchange Database.) Because you cannot undo changes that were made to a database during the repair process, only use Eseutil and Isinteg as a last resort. As discussed earlier, it is recommended that you recover a damaged database by restoring a backup set instead of repairing a database"
Have you tried creating separate PST data files for some of the bulk.  You could move by year or month, etc.  Burn the PST's to disk for archive.  Then recreate the mail profile at the users PC.  This would allow for the adjustment on whether to cache the mailbox during setup.   Then logon with the new profile and sync the folders.  If it runs smoothly you could then choose the new profile as the new default profile.
tombozzoAuthor Commented:
The solution ended up being to "Export the mailbox, delete the mailbox from the store, create a new mailbox, and Import back".  I hadn't done this in awhile so a word of advice to anyone trying this: be sure to jot down all the information about that mailbox prior to deleting (like system aliases). You want to be sure to recreate the mailbox with EXACTLY the same info as was previously stored, otherwise you'll run into some headaches.

From another source: "Before you recreate a user you need to get the legacyexchangedn parameter on
the user object (can be found using adsiedit). After recreating the mailbox you can add this legacyexchangedn as a new X500 address to the user object.

This legacyexchangedn address is the address Outlook uses and stores in its
autocomplete cache."

Anyhow, thanks to those of you who contributed.

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.