Exchange Exchange
A community dedicated to Exchange and related technology.

MAPI_W_PARTIAL_COMPLETION

rated by 0 users
Not Answered This post has 0 verified answers | 2 Replies | 1 Follower

Chach posted on 08-10-2005 12:06 AM

Good evening.  I have been fighting a corrupt NT 4.0 server with a corrupt Exchange 5.5 server running on it.  Tried migrating to SBS2003 with its wizards by creating PST files from the old Exchange server.  (New Server is accepting email from the web, just cant import old emails) However, neither Exmerge nor the SBS wizards could import them. 

Tried running PST repair utility from Office CD, still didnt work. 

Tried using ExMerge to create new PST from old server using the 2 step process.  After running an hour, that task completed sucessfully.  However after launching the second step of the process, 5 of the 6 imports failed.  The ExMerge Thread 0&1 logs show literally thousands of errors with the statement "MAPI_W_PARTIAL_COMPLETION".  Only thing I've been able to find from Microsoft is pertaining to having the Anti-Virus service running on the old server.  As far as I can tell, it is NOT running any anti-virus services... but it IS suffering a lot of corruption.

Anyone of you Grand Masters out there have any other possible explanations?  Or, at least, any ideas as far as alternatives for my client, like an Exchange recovery service?  Thanks in advance!

  • Filed under:
  • | Post Points: 0

All Replies

Top 10 Contributor
Points 3,290
Can you open the PSTs with Outlook?
If you can't you will probably need to rerun the exmerge export, however you will want to check the MAPI.dll versions to make sure you have a matching version with your ExMerge version.

Also make sure the PSTs aren't marked Read-Only on the file system as you can't open RO PSTs.

Are the PSTs you are trying to import larger than 1.8GB? If they are they are corrupt and will need to be exported in smaller chunks as non-unicode based PSTs still have a max size of just under 2GB.

- Joel

  • Filed under:
  • | Post Points: 0

Thanks for the good tips!Cool  The PST's I generated (with ExMerge and with the SBS utility) would not import into Outlook.  The biggest PST's were broken into pieces, no one piece was bigger than 1.3 GB.  PST's were not read-only.

The process with Exmerge and the built-in utility would start, then get quite a ways into the process before failing.  And I noticed that it was doing it on the same user at the same spot.  Very frustrating. 

I've decided that the old Exchange store is near-hopelessly corrupted and is STILL full of virus impregnated attachments.  What I wound up doing is (one user at a time) pointing Outlook back at the old server, slowly exporting data into PST files THRU OUTLOOK, then pointing Outlook at the new server and importing the data back up to the new server.  This worked for all the clients except one.  (Care to guess which one?)  She now has Outlook set up with the option to choose profiles when starting.  She can either look at her old emails on the old server, or send/receive emails on the new server.  She is going to have to move emails over manually. 

I noticed while copying emails over manually that she is getting a barrage of virus alerts that no one seems to care about.  That should give you some idea of the people I'm dealing with at this place. 

I'll have to chalk this one up as a learning experience.  I'll be sure to run more careful tests and have the user sign an Exchange waiver next time I propose a contract like this.  Thanks for your help again.

  • Filed under:
  • | Post Points: 0
Page 1 of 1 (3 items) | RSS
© 2003-2008 NamedPipes Consulting. All other company and product names are property of their owners.
Powered by Community Server (Non-Commercial Edition), by Telligent Systems