Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2000
  • Last Modified:

Exchange 2010 Import PST > 2 GB

Hello,

Trying to import PST to newly created mailbox. Using New-MailboxImportRequest cmdlet. This kicks off and Queues but fails shortly thereafter.

Event Log:

Unable to read folder ID '40354'. Check the PST file for possible corruption. --> Page map offset (60652) is greater than buffer length (8192)

Get-MailboxImportRequestStatistics shows:

FailureCode                   : -2146233088
FailureType                   : RecipientNotFoundPermanentException
FailureSide                   :
Message                       : Error: Cannot find a recipient that has mailbox GUID 'fd90c91d-28e6-41f1-ac2d-69e7947ef99c'.

It's a 10GB PST that I exported using New-MailboxExportRequest. Only thing I found was that it was a size issue but limit is greater than 10GB and this was exported using Exchange 2010.

A little background: I deleted this user after backing up PST. A remote user has need to access so simple thing to do seemed to be re-create mailbox and import and share with remote user.  Perhaps, this is why it cannot find recipient as GUID is different.

Any ideas?
0
ecosys
Asked:
ecosys
  • 5
  • 4
1 Solution
 
NiceCuppaTeaCommented:
New-MailboxImportRequest -Mailbox 'IDENTITY OF NEW MAILBOX eg John.Smith' -FilePath 'C:\yourpst.pst'

Should do it, are you entering a guid instead of mailbox identity?

Have you tried to open a copy of the pst file in outlook to see if its still intact?
0
 
ecosysAuthor Commented:
Yep. That's the command I'm using.

New-MailboxImportRequest -FilePath "\\PST Exports\user.pst" -mailbox user

Opened it no issue from Outook client.
0
 
NiceCuppaTeaCommented:
Is the failure immediate or part way through processing?

Check permissions, from technet.....
"You need to grant read/write permission to the group Exchange Trusted Subsystem to the network share where you'll export or import mailboxes. If you don't grant this permission, you'll receive an error message stating that Exchange is unable to establish a connection to the target mailbox."

Or as i normally do if its a temporary file that's being imported then deleted (everyone/all)
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
Pete LongTechnical ConsultantCommented:
This happens because you exported a PST file either using ExMerge or an older version of Outlook and it's too big. Make sure it's well under 2GB, ot use a newer version of Outlook to export this mailbox.

Exchange 2010 (Post SP1) Bulk Importing Mail From pst Files


PL
0
 
ecosysAuthor Commented:
I see it hit the Queued state and then it fails.

I've exported the PST to this share already so permissions are okay.

I created another user with mailbox and tried to export to this mailbox. I thought maybe because the mailbox I deleted was same name as the mailbox I created.  
Now I get:

FailureType                   : UnableToReadPSTFolderPermanentException
FailureSide                   : Source
Message                       : Error: Unable to read folder ID '40354'. Check the PST file for possible corruption. --
                                > Page map offset (60652) is greater than buffer length (8192)
FailureTimestamp              : 6/3/2013 11:28:28 AM


I didn't export using exmerge. I used cmdlet from Exchange 2010 PS to export.
0
 
NiceCuppaTeaCommented:
sure sounds like permissions to me, try setting  everyone/all permissions on the file (make sure its not open in outlook) and running the import again.

If that fails then run the following PS cmd then post the report....

Get-MailboxImportRequest | Get-MailboxImportRequestStatistics -IncludeReport | fl >report.txt
0
 
ecosysAuthor Commented:
Hmm. I changed the share to "Everyone" - read/write. It looked like it was going to work but it failed.

RunspaceId                    : d28f8b6f-0e55-4cfd-9daf-3dc2d16b4607
Name                          : MailboxImport1
Status                        : Failed
StatusDetail                  : FailedOther
SyncStage                     : CreatingFolderHierarchy
Flags                         : IntraOrg, Pull, Suspend
RequestStyle                  : IntraOrg
Direction                     : Pull
Protect                       : False
Suspend                       : True
FilePath                      : \\filer1\PST Exports\mp.pst
SourceRootFolder              : 
SourceVersion                 : Version 0.0 (Build 0.0)
TargetAlias                   : mppst
TargetIsArchive               : False
TargetExchangeGuid            : 7e539b2d-f027-474f-aa0c-be6d1c4450ed
TargetRootFolder              : 
TargetVersion                 : Version 14.1 (Build 338.0)
TargetDatabase                : EM1 Database
TargetMailboxIdentity         : e.local/EAD/Users/NY/MP PST
IncludeFolders                : {}
ExcludeFolders                : {}
ExcludeDumpster               : False
ConflictResolutionOption      : KeepSourceItem
AssociatedMessagesCopyOption  : DoNotCopy
BatchName                     : 
BadItemLimit                  : 0
BadItemsEncountered           : 0
QueuedTimestamp               : 6/3/2013 11:49:27 AM
StartTimestamp                : 6/3/2013 11:56:36 AM
LastUpdateTimestamp           : 6/3/2013 11:56:38 AM
CompletionTimestamp           : 
SuspendedTimestamp            : 
OverallDuration               : 00:21:16
TotalSuspendedDuration        : 
TotalFailedDuration           : 00:14:05
TotalQueuedDuration           : 00:07:08
TotalInProgressDuration       : 00:00:02
TotalStalledDueToHADuration   : 
TotalTransientFailureDuration : 
MRSServerName                 : 
EstimatedTransferSize         : 0 B (0 bytes)
EstimatedTransferItemCount    : 0
BytesTransferred              : 0 B (0 bytes)
BytesTransferredPerMinute     : 
ItemsTransferred              : 0
PercentComplete               : 5
PositionInQueue               : 
FailureCode                   : -2146233088
FailureType                   : UnableToReadPSTFolderPermanentException
FailureSide                   : Source
Message                       : Error: Unable to read folder ID '40354'. Check the PST file for possible corruption. --
                                > Page map offset (60652) is greater than buffer length (8192)
FailureTimestamp              : 6/3/2013 11:56:38 AM
FailureContext                : --------
                                Operation: IMailbox.EnumerateFolderHierarchy
                                OperationSide: Source
                                PST (\\filer1\PST Exports\mp.pst)
                                PropTags: [0x80210003(NamedProp); 0x80220102(NamedProp); ContentCount; MessageSizeExten
                                ded; AssocContentCount; AssocMessageSizeExtended; LocalCommitTimeMax; DeletedCountTotal
                                ; PfProxy]
IsValid                       : True
ValidationMessage             : 
OrganizationId                : 
RequestGuid                   : ca16aaa3-238b-404f-baa7-a91ac28a5e64
RequestQueue                  : EM1 Database
Identity                      : RequestGuid (ca16aaa3-238b-404f-baa7-a91ac28a5e64), RequestQueue: (a05bc70f-e36b-4743-b
                                666-329f2646c713)
Report                        : 

Open in new window

0
 
NiceCuppaTeaCommented:
This thread on technet seems to suggest it may be due to a hotfix installed in outlook.....

http://social.technet.microsoft.com/Forums/en-US/exchangesvradminlegacy/thread/1a979543-c4f8-4504-8870-95612c81b181

Try removing the mentioned hotfixes and see what happens
0
 
ecosysAuthor Commented:
I couldn't get this working. It was within 15 days - I just reconnected the disconnected mailbox.
0
 
ecosysAuthor Commented:
It's not the solution to the problem but a valid workaround.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now