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

Status
Not open for further replies.
G

Grubsy

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 look 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).
 
T

Troy Werelius

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

Troy Werelius

Lucid8
 
G

Grubsy

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

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

Thanks
 
G

Grubsy

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.
 
B

Brian Day MCITP

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.
 
T

Troy Werelius

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/ 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
 
E

Erik Van Tricht

Hi Brian,

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

Kind regards,

Erik
 
B

Brian Day MCITP

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.
 
S

szyja

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.
 
H

huntit

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.
 
L

lAdK

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
 
S

szyja

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...
 
T

Troy Werelius

I hear and understand your frustration level on this issue, but I do have to say the Exchange 2010 overall rocks as does the MS team that is working hard to plug these holes. The issue doesn't have as much to do with how the PSTs were created, but how the data was originally ingested into the Exchange database. Some clients allowed data to be formatted incorrectly and the older versions of Exchange allowed them to do so.

Outlook can handle these issues from a user perspective (i.e. they see no visual representation of the problem) but alas Exchange 2010 and the supporting services knows these are incorrect and refuses to let them into the database which overall is a good thing, however, now they have to work out a fix to correct these anomalies upon ingestion. So if the data is incorrectly formatted in the legacy db, exporting it to PST retains those same issues.

I am sure MS will have a fix for your issue as soon as possible, but again I understand the frustration, but man you really don't want to go to Lotus Notes...

NOTE: We have been helping many other customers overcome issues like these via the use of our DigiScope product and so far it has a 100% success rate. If you would be willing to send us one of the PST files that is exhibiting this behavior we would be happy to run it through an recovery process in our lab to ensure its recoverable via DigiScope and even show you that it works via a WebEx session.
Troy Werelius
www.Lucid8.com
 
M

Mumin CICEK [MVP]

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
 
G

Grubsy

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.
 
S

szyja

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 :)
 
Status
Not open for further replies.
Top