(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. Then logon with the new profile and sync the folders.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. If it runs smoothly you could then choose the new profile as the new default profile.I ran a test PST export of his mailbox and in the Exmerge logs I am seeing thousands of records like this:  Error copying message with subject 'Your Junk Mail Digest: [email protected]' in folder '\Inbox'.
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.
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...
Expand all | Collapse all Symptoms If you are using Microsoft Office Outlook 2003 in online mode together with a ma...
If you are using Microsoft Office Outlook 2003 in online mode together with a mailbox that is located on a Microsoft Exchange Server 2010 server, you may notice the following symptoms: • Outgoing e-mail messages stay in the Outbox for up to 1 minute.
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?
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.
Exchange databases with Eseutil and Isinteg can cause lost data in the Exchange databases you repair.