For years, I’ve been importing and exporting mailboxes with relatively no problems, when I started getting this error when exporting a number of mailboxes: [PS] C:\Windows\system32>New-MailboxExportReqeust john.doe -FilePath \\server\share\john.doe.pst Unable to open PST file ‘\\server\share\john.doe.pst’. Error details: Header file length is zero. If this file is from a previously failed pst export, please delete the file and resume the export. + CategoryInfo : NotSpecified: (0:Int32) […]
When you run this cmdlet: New-MailboxExportRequest <username> -FilePath \\servername\sharename\username.pst …and you get this error message: Couldn’t connect to the source mailbox. + CategoryInfo : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemotePermanentException + FullyQualifiedErrorId : B1C4188,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest …the most common problem is that the source mailbox has been hidden from the GAL. Oddly, it doesn’t happen with every mailbox that is hidden. It is probably a combination of factors, such […]
The New-MailboxExportRequest (and New-MailboxImportRequest) cmdlet requires a UNC path for the FilePath parameter. In other words, you can’t use “New-MailboxExportRequest -Mailbox MailboxName -FilePath C:\output.pst”. You have to use “New-MailboxExportRequest -Mailbox MailboxName -FilePath \\servername\sharename\output.pst”. However, if the share and NTFS permissions aren’t set correctly on the destination path, you could get an error like this one. [PS] C:\Windows\system32>New-MailboxExportRequest -Mailbox MailboxName -FilePath \\servername\sharename\output.pst Unable to open PST […]