locked
New-MailboxImportRequest isn't finishing. Can't work out why. Exchange 2010 SP1 RRS feed

  • Question

  • Exchange 2010 SP1, Windows Server 2008 R2 Enterprise

    username_outlook07.pst (1gb) & username_archive07.pst (3gb)

    First I ran:

    New-MailboxImportRequest -Mailbox "User Name" -FilePath \\exchange_server\e$\PST\username_outlook07.pst -BadItemLimit 50 (added the BadItemLimit after a failure. checked the log later and found the were some emails larger than the limit set in exchange)

    So far so good! Next I ran:

    New-MailboxImportRequest -Mailbox "User Name" -FilePath \\exchange_server\e$\PST\username_archive07.pst -BadItemLimit 50 -IsArchive

    Get-MailboxImportRequest (Shows In Progess, but doesn't seem to finish, even left it overnight, this created 30 odd gb of logs, but still didnt finish)

    Get-MailboxImportRequestStatistics "User Name\MailboxImport" | fl (shows more info, but can't see what the issue is)

    Get-MailboxImportRequestStatistics "User Name\MailboxImport" -IncludeReport | fl >> e:\report.txt (I have this full report, but can't see anything that stands out)

    The section below looks to be where the issues begin:

    17/09/2010 11:07:45 AM [server] Merging folder '/Top of Personal Folders/Outbox' into ' /Top of Information Store/Outbox'.
    17/09/2010 11:07:45 AM [server] Copying 0 items, 0 B (0 bytes). Skipping 1 items, 234 B (234 bytes).
    17/09/2010 11:07:45 AM [server] Merging folder '/Top of Personal Folders/Sent Items' into '/Top of Information Store/Sent Items'.
    17/09/2010 11:09:41 AM [server] Copying 20531 items, 1.185 GB (1,272,500,347 bytes). Skipping 2 items, 6.631 KB (6,790 bytes).
    17/09/2010 11:12:32 AM [server] Stage: CopyingMessages. Percent complete: 17.
    17/09/2010 11:12:32 AM [server] Copy progress: 3272/55243 messages, 248.5 MB (260,616,364 bytes)/2.822 GB (3,030,455,890 bytes).
    17/09/2010 11:17:32 AM [server] Stage: CopyingMessages. Percent complete: 26.
    17/09/2010 11:17:32 AM [server] Copy progress: 7641/55243 messages, 522 MB (547,387,731bytes)/2.822 GB (3,030,455,890 bytes).
    17/09/2010 11:22:33 AM [server] Stage: CopyingMessages. Percent complete: 35.
    17/09/2010 11:22:33 AM [server] Copy progress: 13446/55243 messages, 815 MB (854,591,092 bytes)/2.822 GB (3,030,455,890 bytes).
    17/09/2010 11:25:28 AM [server] The Microsoft Exchange Mailbox Replication service 'server.domain.local' (14.1.218.11 caps:07) is examining the request.
    17/09/2010 11:25:28 AM [server] Connected to target mailbox 'Archive (904f3153-fa24-43ef-aba6-81c8bd7252fa)', database 'MAILSTORE1', Mailbox server 'server.domain.local' Version 14.1 (Build 218.0).
    17/09/2010 11:25:29 AM [server] Request processing started.
    17/09/2010 11:25:29 AM [server] Stage: CreatingFolderHierarchy. Percent complete: 5.
    17/09/2010 11:28:13 AM [server] Couldn't find folder 'Dumpster'.
    17/09/2010 11:28:13 AM [server] Merge initialized for mailbox 'Archive (904f3153-fa24-43ef-aba6-81c8bd7252fa)': 390 folders total. Estimated data size: 55243 items, 2.822 GB (3,030,455,890 bytes).
    17/09/2010 11:28:13 AM [server] Stage: CopyingMessages. Percent complete: 10.
    17/09/2010 11:28:13 AM [server] Copy progress: 0/55243 messages, 0 B (0 bytes)/2.822 GB (3,030,455,890 bytes).
    17/09/2010 11:28:13 AM [server] Merging folder '/Top of Personal Folders [IpmSubtree]' into '/Top of Information Store [IpmSubtree]'.
    17/09/2010 11:28:13 AM [server] Copying 0 items, 0 B (0 bytes). Skipping 1 items, 6.038KB (6,183 bytes).
    17/09/2010 11:28:13 AM [server] Stage: CopyingMessages. Percent complete: 10.
    17/09/2010 11:28:13 AM [server] Copy progress: 0/55243 messages, 0 B (0 bytes)/2.822 GB (3,030,455,890 bytes).
    17/09/2010 11:30:00 AM [server] The Microsoft Exchange Mailbox Replication service 'server.domain.local' (14.1.218.11 caps:07) is examining the request.
    17/09/2010 11:30:00 AM [server] Connected to target mailbox 'Archive (904f3153-fa24-43ef-aba6-81c8bd7252fa)', database 'MAILSTORE1', Mailbox server 'server.domain.local' Version 14.1 (Build 218.0).
    17/09/2010 11:30:01 AM [server] Request processing started.
    17/09/2010 11:30:01 AM [server] Stage: CreatingFolderHierarchy. Percent complete: 5.
    17/09/2010 11:30:11 AM [server] Couldn't find folder 'Dumpster'.
    17/09/2010 11:30:11 AM [server] Merge initialized for mailbox 'Archive (904f3153-fa24-43ef-aba6-81c8bd7252fa)': 390 folders total. Estimated data size: 55243 items, 2.822 GB (3,030,455,890 bytes).
    17/09/2010 11:30:11 AM [server] Stage: CopyingMessages. Percent complete: 10.
    17/09/2010 11:30:11 AM [server] Copy progress: 0/55243 messages, 0 B (0 bytes)/2.822 GB (3,030,455,890 bytes).
    17/09/2010 11:30:12 AM [server] Merging folder '/Top of Personal Folders [IpmSubtree]' into '/Top of Information Store [IpmSubtree]'.
    17/09/2010 11:30:12 AM [server] Copying 0 items, 0 B (0 bytes). Skipping 1 items, 6.038 KB (6,183 bytes).
    17/09/2010 11:30:12 AM [server] Stage: CopyingMessages. Percent complete: 10.
    17/09/2010 11:30:12 AM [server] Copy progress: 0/55243 messages, 0 B (0 bytes)/2.822 GB (3,030,455,890 bytes).

    From then on it just repeats the 12 lines beginning with:

    The Microsoft Exchange Mailbox Replication service 'server.domain.local' (14.1.218.11 caps:07) is examining the request. etc...

    Any help would be greatly appreciated

    • Edited by Grubsy Wednesday, September 22, 2010 5:31 AM Updated
    Wednesday, September 22, 2010 5:28 AM

All replies

    1. Where did these PST files come from, i.e. how were they created
    2. Check your event logs, is by chance the CAS service failing and then auto-starting during the import process?
    3. Anything else happening in the event log to help narrow this down?

    Troy Werelius

    Lucid8

    Thursday, September 23, 2010 3:25 PM
  • 1. They were created in Outlook 2007. I tried creating a new PST file in Outlook 2010 and then I imported the archive PST into this 'new' outlook 2010 PST. I then tried to import the 'new' PST into the exchange archive and it also failed the same way as the original did. I've also run scanpst.exe over the file and tried importing it after that and it made no difference.

    2. I've found a number of Errors, Even ID 4999, Task Category General at the time of the import.

    Watson report about to be sent for process id: 8304, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, MSExchangeMailboxReplication, M.E.MailboxReplicationService.Common, M.E.M.BadMessageRec.Bad, System.ArgumentException, 8546, 14.01.0218.012.
    ErrorReportingEnabled: True

    Watson report about to be sent for process id: 8516, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, MSExchangeMailboxReplication, M.E.MailboxReplicationService.Common, M.E.M.BadMessageRec.Bad, System.ArgumentException, 8546, 14.01.0218.012.
    ErrorReportingEnabled: True

    Watson report about to be sent for process id: 5276, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, MSExchangeMailboxReplication, M.E.MailboxReplicationService.Common, M.E.M.BadMessageRec.Bad, System.ArgumentException, 8546, 14.01.0218.012.
    ErrorReportingEnabled: True

    Update. I've just noticed prior to the above errors each time there is another error:

    Watson report about to be sent for process id: 2328, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, M.E.RpcClientAccess.Service, M.Exchange.StoreProvider, M.M.MapiProp.SaveChanges, M.E.D.Storage.ObjectNotFoundException-19665, 19f-90be, 14.01.0218.011.
    ErrorReportingEnabled: True

    3. Not that I can see. I'm just looking in Windows Logs\Application

    Thanks

    • Edited by Grubsy Monday, September 27, 2010 7:24 AM fix spacing
    Monday, September 27, 2010 7:17 AM
  • Just tried again. Here are the events logged:

    1) Information - MSExchange Mailbox Replication - 1102 - Request

    The Microsoft Exchange Mailbox Replication service started processing a mailbox move for 'RequestGuid (4d271896-e54e-4051-99b9-5bae738dee30), RequestQueue: (bfb1fc4f-19e2-49c7-a6bf-9dd65f9b918e)'.
    Mailbox GUID: 4d271896-e54e-4051-99b9-5bae738dee30
    Source MDB:
    Destination mailbox database: MAILSTORE1
    Move flags: IntraOrg, Pull

    2) Error - MSExchange Common - 4999 - General

    Watson report about to be sent for process id: 2420, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, M.E.RpcClientAccess.Service, M.Exchange.StoreProvider, M.M.MapiProp.SaveChanges, M.E.D.Storage.ObjectNotFoundException-19665, 19f-90be, 14.01.0218.011.
    ErrorReportingEnabled: True

    3) Error - MSExchange Common - 4999 - General

    Watson report about to be sent for process id: 3228, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, MSExchangeMailboxReplication, M.E.MailboxReplicationService.Common, M.E.M.BadMessageRec.Bad, System.ArgumentException, 8546, 14.01.0218.012.
    ErrorReportingEnabled: True

    4) Information - MSExchange Mailbox Replication - 1000 - Service

    The Mailbox Replication service has started successfully.
    Version 14.1.218.11, PID 6020.

    5) Information - MSExchange Mailbox Replication - 1102 - Request

    The Microsoft Exchange Mailbox Replication service started processing a mailbox move for 'RequestGuid (4d271896-e54e-4051-99b9-5bae738dee30), RequestQueue: (bfb1fc4f-19e2-49c7-a6bf-9dd65f9b918e)'.
    Mailbox GUID: 4d271896-e54e-4051-99b9-5bae738dee30
    Source MDB:
    Destination mailbox database: MAILSTORE1
    Move flags: IntraOrg, Pull

    6) Error - MSExchange Common - 4999 - General

    Watson report about to be sent for process id: 6020, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, MSExchangeMailboxReplication, M.E.MailboxReplicationService.Common, M.E.M.BadMessageRec.Bad, System.ArgumentException, 8546, 14.01.0218.012.
    ErrorReportingEnabled: True

    4, 5 & 6 then continue to loop.

    Monday, September 27, 2010 1:06 PM
  • Judging by the content of those 4999s this appears to be an already known issue we are tracking, have a few support cases on, and have been able to repro with some customer PST files. I hope to get an update of some kind on the situation today.


    Microsoft Premier Field Engineer, Exchange
    MCSA 2000/2003, CCNA
    MCITP: Enterprise Messaging Administrator 2010
    Former Microsoft MVP, Exchange Server
    My posts are provided “AS IS” with no guarantees, no warranties, and they confer no rights.
    Monday, September 27, 2010 1:11 PM
  • This sounds as though it could be an issue we discovered last year with NON-Unicode codepage properties within the messages. Much of this in our research came from older messages from previous versions of Exchange where the client was not as diligent when injecting the data into Exchange   We fixed this Lucid8's DigiScope product http://www.lucid8.com/product/digiscope.asp in order to support our 2010 Exchange customers.  

    This was supposed to have been fixed in RU1 and I presumed SP1 as well but it appears to still be rearing its ugly head.   One of our Dev's directed me to this MS article http://support.microsoft.com/kb/977552/ that was born from our discovery early last year.  in short the article states that “Exchange Server 2010 checks the codepage property of the message to determine the encoding that is used for non-Unicode properties of the recipient. If the codepage property has invalid values, the Exchange RPC Client Access service crashes.”

    Anyway I think this is what Brian referenced to being worked on and hopefully they will have a fix soon. There is of course the chance that I am incorrect, but everything you are describing sure looks and smells like the exact same issue.

    Troy Werelius

    Lucid8

    • Edited by Troy Werelius Monday, September 27, 2010 3:41 PM URL change
    Monday, September 27, 2010 3:33 PM
  • Hi Brian,

    Is there allready an update on this thread. i'm facing exactly teh same problem.

    Kind regards,

    Erik

    Wednesday, September 29, 2010 7:36 PM
  • Hi Brian, Also waiting on an update here :)

     

    Cheers

    Thursday, September 30, 2010 4:43 AM
  • Hi folks,

    Due to the nature of the beast I can't publically say everything, but rest assured a great dev is working hard on this and is making good progress. I can't comment on when/if a fix will be released in a certain Update Rollup at this time. If I find out we end up with what is called an Interim Update available I'll make sure I post how to get it here, which will require calling into PSS to obtain it. IUs are quick-fix type updates and don't go through every single last test a normal update goes through, they also must be removed before future Update Rollups or Service Packs are installed.

    There are multiple things going on here that can cause the import to fail, but but the most common issue is older applications weren't always very good about properly writing all of the necessary attributes to items within PSTs. The import routine is expecting to see properly formatted data within the PST and when it doesn't you see it crash with the event IDs above. So while the PST to us humans looks perfectly fine and is usable in Outlook, behind the scenes there may be a bunch of missing or badly formatted attributes on items within it.


    Microsoft Premier Field Engineer, Exchange
    MCSA 2000/2003, CCNA
    MCITP: Enterprise Messaging Administrator 2010
    Former Microsoft MVP, Exchange Server
    My posts are provided “AS IS” with no guarantees, no warranties, and they confer no rights.
    Thursday, September 30, 2010 1:22 PM
  • I have exactly the same -  after New-MailboxImportRequest command - there are some errors in application log and MSExchangeMailboxReplication.exe is crashed/restarted. After Remove-MailboxImportRequest command, when are not active import requests, errors are not generated.

    So, there is a big problem - this is completely new installation and there is no way to import .PST files to Exchange 2010 SP1 organizations from EMC Console.

    My errors from application log:

    Source:        MSExchange Common
    Event ID:      4999
    Task Category: General
    Level:         Error
    Description:
    Watson report about to be sent for process id: 3440, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, MSExchangeMailboxReplication, M.E.MailboxReplicationService.Common, M.E.M.BadMessageRec.Bad, System.ArgumentException, 8546, 14.01.0218.012.
    ErrorReportingEnabled: False

    Source:        Windows Error Reporting
    Event ID:      1001
    Fault bucket , type 0
    Event Name: CLR20r3
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: msexchangemailboxreplication.exe
    P2: 14.1.218.15
    P3: 4c70b675
    P4: System.Xml
    P5: 2.0.0.0
    P6: 4a275e0f
    P7: 298
    P8: 0
    P9: System.ArgumentException

    Source:        MSExchange Mailbox Replication
    Event ID:      1000
    Task Category: Service
    Level:         Information
    The Mailbox Replication service has started successfully.
    Version 14.1.218.11, PID 864.

     

    Wednesday, October 13, 2010 10:20 PM
  • I know MS is working on it, but no idea when it will be completed.  Only options from what I can tell is to; 

    1. Wait......
    2. Use our DigiScope Product since it overcomes the issue http://www.lucid8.com/product/digiscope.asp

    Troy Werelius
    www.Lucid8.com
    Wednesday, October 13, 2010 10:23 PM
  • I'm also having the same problem as above, importing PST files that were exported from a Exchange 2007 SP1 server.

    Am running Exchange 2010 SP1 with the recent Update Rollup 1 installed, but it doesn't look like that's fixed the problem.

     

    If there's any updates from MS, please let us know.

    In the meantime, I'll try importing the PSTs one-by-one inside Outlook.

     

     

    Thanks,

    Peter.

    Saturday, October 16, 2010 4:32 AM
  • I have faced the same issue to with some of my customers and it looks very weird. for example running the import request from the mailbox server crashes the rpc services in most cases importing it from the CAS server works without issues. when at other customers it works flawlessly 

     

    would be keeping a close eye on this thread for any potential hotfix/solution

     


    Full time IT consultant since 1998 mainly on Exchange\ISA\AD MCSE NT4.0,2000/2003, CCNA MCITP: Enterprise Messaging Administrator 2007/2010 MCT since 2001
    Saturday, October 16, 2010 9:01 AM
  • I think there is no codepage problem. I have an open case at Microsoft. My PST's are created in Outlook 2007 or Outlook 2010, with POP3/SMTP account. There is a problem with Tasks in PST file - especially with Task Requests.

     When there is no sent tasks in PST (messages begins with "Task Reguest"), import is working without errors. When there are messages beginning with "Task Requests" subject (which is automatically created by Outlook) in PST, msexchangemailboxreplication.exe process is crashed and import is not completed.

    So, at this moment there is not-working tool to properly import PST's into new, best Exchange 2010 SP1 infrastructure. next time I'll think about Lotus Notes...

    Friday, October 29, 2010 9:22 AM
  • hi,

    in some of my customers that uses all the exchange server roles installed on one server this error can occure.

    if exchange server is installed with typical installation and if you want to export or import mailbox to pst or from pst you can get this error.

    regards,

     


    Mumin CICEK | Exchange - MVP | www.cozumbilisim.com.tr | www.mumincicek.com | www.cozumpark.com
    Friday, October 29, 2010 10:48 AM
  • I found a work around the other day and can't believe I hadn't tried it before.

    In Outlook 2010 -> File -> Open -> Import -> Import from another program or file -> Outlook Data File (.pst) -> then whatever options you like :)

    This imported all emails from the pst with no errors. While this works it isn't really suitable for a large number of users. The user also cannot use outlook while the import is running.

    I can also confirm the DigiScope product Troy is suggesting also works.

    Friday, October 29, 2010 11:31 AM
  • I think import/export mailboxes between .mdb and .pst should be done by integrated tools/command, delivered with system. Without additional external product.

    Additionally: if pst is imported to mdb over manual drag-and-drop folders/messages in Outlook2007, moving Tasks takes longer like other items. And if I export the same mailbox with MailboxExportRequest, and try to import again - everything is fine without errors.

    NOTE: I believe you so your tools works. You want to sell, but I don't want to pay :)

     

    Friday, October 29, 2010 12:50 PM
  • Fair enough :-)
    Troy Werelius
    www.Lucid8.com
    Friday, October 29, 2010 12:53 PM
  • Hello Brian,

    I appreciate that you cannot publicly announce update fixes until fully proven and that you are dealing with x types of legacy messes in PST files. Could you however give an update as of now relating to this case? I am dealing with a large migration of Exchange data from a liquidating company and thus have limited time available to import data to a new system and without a direct PSS line until the new agreement is set up, am limited to being advised to post a problem here for support relating to a known issue. If there is an option to test an 'in development' fix on our non-volatile systems we would be keen to participate or at least to be informed when an interim update is available.

    Regards,

    Andy

    (And to pre-empt any more adverts on this thread, no I don't want to buy a product to fix a standard operation of Exchange. Any of us experiencing this problem could similarly spend money employing someone to import through Outlook)

    Tuesday, November 30, 2010 2:16 PM
  • I, too, have been going through this with Microsoft CSS.

    Happily, they were able to reproduce the error i believe and happily, I notice yesterdays rollup hotfix 2 for Exchange 2010 SP1 (http://support.microsoft.com/?kbid=2425179) contains this:

    The Exchange Mailbox Replication service crashes when you use the "New-MailboxImportRequest" command to import a PST file to an Exchange Server 2010 mailbox
    http://support.microsoft.com/kb/2458005/

    "Consider the following scenario:

    • You use the New-MailboxImportRequest command to import a .pst file to a mailbox in a Microsoft Exchange Server 2010 Service Pack 1 (SP1) environment.
    • An item in the .pst file has a string that contains invalid XML characters. "

    Although I wager a few other people have also reported it and raised it with Microsoft, I've been dealing with them for the past two weeks-ish and was very happy to see that this is in this rollup.

    Installing the Rollup Hotfix 2 now on all of our Exchange servers (we have roles seperated out to ease the load etc) to see if it fixes the issue.

    If it works, then Microsoft, you have my thanks for such a speedy resolution (for me) :)

    Cheers
    Nath.


    Nathan H ICT Messaging & Security Development Officer - CCC (gov)
    Wednesday, December 15, 2010 9:14 PM
  • Good luck with the installs, Nathan. The folks I've spoke to so far have had good luck with imports after applying RU2. You may still run into some legitimately corrupt items within the PSTs (just like with normal mailbox rules), so don't be surprised if you have to increase the -BadItemLimit a bit until you clear that hurdle. An Event 1100 will be logged if the import hits the BadItemLimit for an import.
    Microsoft Premier Field Engineer, Exchange
    MCSA 2000/2003, CCNA
    MCITP: Enterprise Messaging Administrator 2010
    Former Microsoft MVP, Exchange Server
    My posts are provided “AS IS” with no guarantees, no warranties, and they confer no rights.
    Thursday, December 16, 2010 3:53 AM
  • Applying the hot fix breaks OWA. Any suggestions? And still does not fix the import PST issue.
    Thursday, December 16, 2010 12:57 PM
  • It sounds like you may not have installed RU2 from an elevated command prompt. Did you simply double-click the .MSP file? If you did, uninstall RU2, open an elevated command prompt (right-click on Command Prompt, run as administrator), change to the directory holding the .MSP, then type the whole .MSP file name and hit enter.
    Microsoft Premier Field Engineer, Exchange
    MCSA 2000/2003, CCNA
    MCITP: Enterprise Messaging Administrator 2010
    Former Microsoft MVP, Exchange Server
    My posts are provided “AS IS” with no guarantees, no warranties, and they confer no rights.
    Thursday, December 16, 2010 1:13 PM
  • reapplied the update per your instructions, and http OWA works now but not HTTPS. Any ideas?
    Thursday, December 16, 2010 2:53 PM
  • Hi Brian

    Seems with all the excitement, i forgot to actually pop back here and say that its muuuuuuuuuch better now - Mainly due to the service not crashing, which I believe is pretty much why you'd never get to the point where the request would be able to fail - it would just restart and you'd end up never getting to the end.

    That was my immediate concern (i.e. knock on effect from the service crashing and potentially messing up other imports that would have otherwise completed successfully) and why I raised it with MS CSS as soon as I was able to.

    It handles most of the PSTs it couldnt handle before, although it still doesnt seem as rock solid at handling corruption [i dont just mean a bad item as such] as it was in RTM [when it used Outlook for its API] but its workable, and for that, im very greatful.

    Its a bit of a egg on my face situation, with us having to get some temp staff in to help assist with the migrations, only for me to install SP1 a few weeks later and then them have to queue up large amounts of PSTs for me to "babysit".... not the most fun time ever but rewarding that we've got to the stage we are at now (i.e. i can hand it back to them - i'm currently working on a "decent" way that they can import and the system will automate some output logs and auto clear completed requests etc. Ive got it all working....just need to finish it off :)

    @Rusty Pass:

    I believe that there is some way - since SP1 - to reset/repair your OWA directory in Exchange, although I cant remember how offhand.

    Ironically, used to have issues with the OAB pre SP1 - sometimes the security settings on the folder would mess up somehow, i think after a server restart usually, but since SP1, its all been working a treat.

    I did read somewhere that 2010 SP1 can break the redirection of OWA's settings so you'll want to check the IIS Settings there most likely, and dont forget to use the IISRESET command / restart IIS however you normally would too ;)

    What error message do u get when you try https? Have your certificates altered? cud be so many things without knowing the error message ;)

    Cheers
    Nath


    Nathan H ICT Messaging & Security Development Officer - CCC (gov)
    Saturday, December 18, 2010 2:46 AM