Link to home
Start Free TrialLog in
Avatar of Gfoulon
GfoulonFlag for France

asked on

Exchange2010 - Error 0x80040107 during New-mailboximportrequest

Hello,

During 2003 to 2010 Exchange migration, we split large mailbox in several EXMERGE <2Gb PST files by specifing dates intervals.
And no errors is shown in EXMERGE export logs from EXCHANGE2003.

But during the import process (through New-mailboximportrequest), the log show a lot of 0x80040107 for several messages with the following details below.
(sorry french version, so description in french, but error is 0x80040107 MapiExceptionInvalidEntryId and not copied because baditem).

The field <sender>,<recipient>,<subject>,<messageClass> report garbaged characters like "¿¿¿¿¿¿¿¿¿"...

These messages can be read if the PST is opened through OUTLOOK and If copy in a new PST, the import work fine but too many PST to do manually.

Does anyone already get this error message during PST import ?
Thanks for your help.

Here are the details :
Un élément endommagé a été détecté lors de l'opération de déplacement. Il n'a pas été copié vers la boîte aux lettres de destination.
<baditem errorType="MapiExceptionInvalidEntryId" errorCode="0x80040107" flags="0x00000000" id="00000000B5066E9D3B38AF42B230E51D7BC4E31184002000">
<folder id="00000000B5066E9D3B38AF42B230E51D7BC4E31182800000">Boîte de réception</folder>
<sender>?????????</sender>
<recipient>???????</recipient>
<subject>??›?????????</subject>
<messageClass>????</messageClass>
<size>9195</size>
<dateSent>03/09/2011 18:16:36</dateSent>
<dateReceived>03/09/2011 18:16:36</dateReceived>
<errorMessage>MapiExceptionInvalidEntryId: Unable to save changes. (hr=0x80040107, ec=-2147221241)
Diagnostic context:
  Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=100]
  Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=60][latency=15]
  Lid: 23226   --- ROP Parse Start ---
  Lid: 27962   ROP: ropSetProps [10]
  Lid: 27962   ROP: ropSaveChangesMessage [12]
  Lid: 17082   ROP Error: 0x80040107
  Lid: 18273  
  Lid: 21921   StoreEc: 0x80040107
  Lid: 31418   --- ROP Parse Done ---
  Lid: 21457  
  Lid: 19665   StoreEc: 0x80040107</errorMessage>
<errorContext>--------
Opération : IMessageProxy.SaveChanges
--------
Opération : IMessageProxy.SaveChanges
OerationSide: Target
Primaire (2ef26bed-8381-4872-b423-96015f0d08b7)</errorContext>
</baditem>
Avatar of Glen Knight
Glen Knight
Flag of United Kingdom of Great Britain and Northern Ireland image

This is because of corrupt items in the mailbox.

Add the -BadItemLimit switch and give it a value of 50, if that doesn't work, increase it to 100.
Avatar of Gfoulon

ASKER

Yes, we already switch to -BadItemLimit 2000,  but my concern is more that these items are correctly exported from Exchange2003 by EXMERGE as Outlook can display it and copy them to another PST file.
Outlook will not display corrupt items, Exmerge will export them but they will not be visible anyway.
Avatar of Gfoulon

ASKER

The email in the differents examples are correctly displayed (we identified them through the date/time) and if we then create a copy these in a new PST the New-mailboximportrequest work fine.
ASKER CERTIFIED SOLUTION
Avatar of Gfoulon
Gfoulon
Flag of France image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
where did you find this information? That's the first I have heard of it and I have done quite a few imports/exports this way.
Avatar of Gfoulon

ASKER

As I can open correctly the PST file with all messages in Outlook, I make a import in Outlook of the PST generated by EXMERGE, and the import of this new PST do no more or bad-items.
Both exchange are french version, by the way, don't know if link or not but email sender name considered as bad-item (MapiExceptionInvalidEntryId) seem to have french accentuated characters and are local Exchange2003 mailbox.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.