ExMerge may fail since it using MAPI the same as Outlook so it is possible that ExMerge will choke the same as Outlook. I would run an offline defrag against your database which is 100% safe and harmless (it will take some time - A very rough estimate is 1 hour for every 5GB). This will create a new database and will rewrite all the messages which means it will rewrite the corrupt message at the JET level, not MAPI.
Here is how to do an offline defrag:
Stop the information store service:
In Control Panel, double-click Services.
Click the Microsoft Exchange Information Store service, and then click Stop. If a dialog box is displayed that states that additional services will be stopped, note the services that will be stopped, and then click OK.
Defragment the public and private information stores by using one of the following methods, as applicable:
In Exchange Server 5.5, to defragment the private information store, type eseutil /d /ispriv at a command prompt, and then press the ENTER key. To defragment the public information store, type eseutil /d /ispub at a command prompt, and then press the ENTER key.
In Exchange 2000, there is no /ispriv, /ispub, or /ds switch. You must specify the file name by typing the following at a command prompt
eseutil /d d:\path\file_name.edb
and then pressing the ENTER key.
Start the information store service:
In Control Panel, double-click Services.
Click the Microsoft Exchange Information Store service, and then click Start.
Start any additional services that were stopped when you performed step 1.
Perform a full online backup of the information store databases.
Let me know if you need more clarification...
Main Topics
Browse All Topics





by: VahikPosted on 2004-02-24 at 19:08:41ID: 10447339
http://support.microsoft.c om/default .aspx?scid =kb;en- us; 328202