Exmerge Problem

1. offizieller Beitrag

    hallo erstmal,
    hab schon oft bei euch mitgelesen und melde mich jetzt mal selber mit einer frage.


    ich habe ein exmerge problem, habe schon alle eure artikel dazu gelesen, aber keine lösung für mein problem gefunden.


    zur eingrenzung des problemes:
    .)ausführender user hat die entsprechenden berechtigungen, auch die am postfachspeicher.
    .)das sprachproblem kann ich ebenfalls ausschliessen.


    hier ein auszug aus dem log:
    [14:19:23] Merging data from file 'D:\EXCHANGEBACKUP\EXCHANGE\CHRISTIAN.PST' to mailbox 'Christian' ('CHRISTIAN') on server 'SERVER01'.
    [14:19:23] Error configuring message service (MSPST MS) (MAPI_E_EXTENDED_ERROR) (CMapiSession::CreateEMSPSTProfile)
    [14:19:23] Errors encountered. Copy process aborted for mailbox 'Christian' ('CHRISTIAN').


    mfg
    christian

    • Offizieller Beitrag

    Hallo,


    überprüfe doch mal folgendes:


    1.)


    1. The problem is that Common Migration Tool (CMT) http://www.binarytree.com is creating
    .pst files in Unicode format.
    2. By default, CMT creates Outlook 2003 (Unicode) .pst files.
    3. You can configure CMT to create Outlook 97-2002 (ANSI) .pst files.
    4. ExMerge cannot import Unicode .pst files - it can only work with ANSI .pst
    files.
    5. There is a bug in CMT that creates an .xml file that causes some of the .pst
    files to be created in Unicode format rather than ANSI format.
    6. Once the .pst files are created in ANSI format, ExMerge 2003 can successfully
    import them into Exchange 2003 SP1.



    2.)


    The trick with this particular case was acknowledging the MAPI_E_EXTENDED_ERROR
    section of the log. This is not discussed specifically in any of the above
    articles. For this case the root cause was due to a invalid PST file of the same
    name as the selected mailbox being exported existing in the target export
    directory. We confirmed the file was invalid by running LIST from the debugging
    tools in hex mode against it. Because the existing PST could not be opened as part
    of the export process and the MAPI UI error dialogues are surpressed it would
    simply fail.


    RESOLUTION


    Remove the invalid PST file from the target directory, choose a different target directory.



    3.)


    The mailbox limit had been reached and we couldn't import any more information into
    the mailbox. We removed the mailbox limit and we were able to import the full
    contents of the .pst file into the mailbox. Ensure that the mailbox cache has been
    given time to clear so that the new mailbox limit takes effect.