• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 944
  • Last Modified:

Export to PST Failed (Exchange 2013)

Hello Guys,

I have an exchange 2013 box I am trying to use the web interface to export a mailbox to PST.
When I am done with selecting the mailbox and the location, I get an error
"The server or share name specified in the path may be invalid or the file could be locked !"

The share name seems ok, since I am able to navigate to it (is is a network share \\ ) and I can create a dummy file there..
In fact it i a QNAP folder .

Please help me troubleshoot the issue. I tried other mailboxes, all are the same..
0
Pierre Ammoun
Asked:
Pierre Ammoun
  • 10
  • 8
  • 6
  • +7
1 Solution
 
timgreen7077Exchange EngineerCommented:
make sure that the exchange account you are using has write access to the share. Also make that the exchange trusted subsystem has access to the share
0
 
AlanConsultantCommented:
Hi Pierre,

I appreciate you are trying this with the GUI, but could you try PowerShell to see if that works:

New-MailboxExportRequest -Mailbox First.Last -FilePath \\Servername\Sharename\First.Last.pst

Open in new window


The path must be a share - not local.

Change First.Last to match the mailbox you want to export.

Try this from an elevated Exchange Management Shell prompt as a domain admin, and make sure the destination has enough space for the entire PST file!

Post back with how that went.

Thanks,

Alan.
1
 
Sandeep KumarAssociate ConsultantCommented:
You can export Exchange 2013 EDB Mailbox to PST easily,
look into https://www.experts-exchange.com/articles/31049/Export-Exchange-2013-EDB-Mailbox-to-PST.html for simple steps, give it a try.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Pierre AmmounAuthor Commented:
Hi Alan,

I tried it , same error.

One more thing. I am trying to save on a QNAP NAS folder. I have given that Folder everyone access read/write
But I could not see the "exchange trusted subsystem". Where can I find this in the QNAP Explorer ?
0
 
AlanConsultantCommented:
Hi Pierre,

Please can you try to a share on another machine - anywhere else should be fine (subject to space).

I just want to be sure if it is related to that specific destination, or something else.

Thanks,

Alan.
0
 
Marshal HubsEmail ConsultantCommented:
This error occurs when the network share that you are using has ran out of space so double check your network share if it still has plenty of space.
You can also use Stellar EDB to PST Converter to export exchange mailboxes (2013) to PST format. The software supports all versions of Exchange Server including 2016, 2013, 2010, 2007, 2003, 2000 etc. You can download the demo version from here: https://www.stellarinfo.com/email-repair/edb-pst-converter.php
0
 
Pete LongTechnical ConsultantCommented:
First create a windows share (elsewhere just to test) , grant the Exchange Trusted Subsystem 'read' and 'write' access and the SYSTEM object full control, then use the PowerShell above (I'm assuming you have given yourself export/import rights already?
See my run though here.

I'm guessing this is rights, (as has already been pointed out), the fact you can't see the Exchange Trusted Subsystem pretty much confirms this.

Pete
0
 
TjnoNetwork AdministratorCommented:
Hi, I got the same problem but in reversed way, when I could not import PST files in NAS device into Exchange mail server. The problem is permission I think. Our solution is copy PST file from NAS device to local location (Exchange server itself) then import them.

In your case, did you try to export to Exchange server itself? Did it work?
0
 
Ajit SinghCommented:
Can you post the entire error content.

Once try just running the mailbox export request command individually to see if that works?

New-MailboxExportRequest -Mailbox <alias> -FilePath \\server\share\alias.pst

It appears you are using a network shared folder to save the exported pst file. So try to use a local folder such as c:\pstbackup\abc.pst to see if it is working.

Export Exchange mailboxes to PST file using Powershell cmdlet:
http://expert-advice.org/exchange-server/export-exchange-mailboxes-pst-file-using-powershell-cmdlet/

How to Convert EDB to PST.

Hope this helps!
0
 
AlanConsultantCommented:
@Ajit:  I don't think you can use 'c:\pstbackup\abc.pst' - it will always fail

You have to do:

New-MailboxExportRequest -Mailbox <Alias> -FilePath \\LocalHost\C$\PSTBackup\Alias.pst

Open in new window


Alan.
1
 
Ajit SinghCommented:
@Alan - Thanks for pointing :)
0
 
Michael foransoftware developperCommented:
This expert suggested creating a Gigs project.
Wonderful exchange EDB recovery has ability to speedily remove inaccuracy from Exchange mailbox database and convert EDB file into PST file with all massage formats. Exchange EDB recovery give option to show preview of recovered mailboxes. This option satisfied you in working process of the software.
Don’t be upset when your EDB file has been corrupted because I recommend that in this situation you can online download Exchange Server Recovery Software. With the help of this software you can successfully recover corrupted EDB file and convert EDB them into PST file and other formats like MSG, EML, vCard, vCal, MBOX and EMLX and vCard with accurate massage formats.

More details visit:  Export EDB to PST Software free

Exchange EDB to PST Software
0
 
AlanConsultantCommented:
Hi Pierre,

Did you try as I suggested above?

Either to a another share, or even locally - one of these:

New-MailboxExportRequest -Mailbox First.Last -FilePath \\Servername\Sharename\First.Last.pst

New-MailboxExportRequest -Mailbox First.Last -FilePath \\LocalHost\C$\Temp\First.Last.pst

Open in new window


Just be 100% sure there is plenty of space on the destination drive - at least twice the reported total size of the mailbox to be sure.


Alan.
0
 
Pierre AmmounAuthor Commented:
Yes I did and it gave me the same error !
0
 
AlanConsultantCommented:
How big is the mailbox and how much empty space on the C:\ drive of the Exchange Server?

Thanks,

Alan.
0
 
Pierre AmmounAuthor Commented:
The mailbox is around 20GB and I have on Drive C: around 300GB free
0
 
timgreen7077Exchange EngineerCommented:
you have to create a share and use \\sharename\file.pst
also give exchange trusted subsystem permissions
0
 
Pierre AmmounAuthor Commented:
Dear timgreen,

Already tried this and it did not work !
0
 
timgreen7077Exchange EngineerCommented:
Please send the cmdlets so I can see what you are typing.
0
 
Pierre AmmounAuthor Commented:
New-MailboxExportRequest -Mailbox pammoun -FilePath \\Srv1\Sharedpst\Pammoun.pst

pammoun being the mailbox I am trying to export
srv1 my server
and sharedpst is a sharedfolder over the network that has exchange trusted subsystem permissions  along with everyone !
0
 
timgreen7077Exchange EngineerCommented:
that looks good. now please tell me the exact error you get when you attempt to run with these cmdlets you just sent.
0
 
timgreen7077Exchange EngineerCommented:
Also make sure you give your self import/export permissions in the ECP
0
 
Pierre AmmounAuthor Commented:
In the Get-MailBoxExportRequest , I get Failed !

The weird thing is that the error comes "only" for few mailboxes.. Other mailboxes do give "Completed" Status.
0
 
timgreen7077Exchange EngineerCommented:
Use the below cmdlets to generate a log so see why it failed.

Get-MailboxImportRequest | Get-MailboxImportRequestStatistics -IncludeReport | fl > \errorlog.txt

I would first suggest clearing the completed requested, and the copy and paste these cmdlets and create a report in order to see
why it failed.
Note: Only clear the successfully completed import request only. Don't clear the failed ones, and the run the cmdlets.
The log will be placed in whatever directory your powershell session is currently in.
0
 
Pierre AmmounAuthor Commented:
Hi,
I need to specify what I did.

I cleared all the Export Request I had with the command
Get-MailboxExportRequest  | Remove-MailboxExportRequest
Removing ALL pending requests. Then I checked with
Get-MailboxExportRequest
that it is displaying nothing.
Then I went to the shared folder and deleted ALL the PSTs there. There were many with very small size.
The folder is empty.
Then I Issues the command to export Everything (all mailboxes).
Then I waited some time and then
Get-MailboxExportRequest -Status Completed | Remove-MailboxExportRequest
I deleted the Completed.
I was left with the remaining "Failed" !!
I am uploading the error I am getting based on this command
Get-MailboxExportRequest | Get-MailboxExportRequestStatistics -IncludeReport | fl > \errorlog.txt

Now 2 things  I noticed that might help.
1-the same mailbox that failed now, did not fail earlier (in a different attempt).
2-Could it be because I am queuing all the email boxes (around 200 and total size of 100GB) and that my share is an external HDD (USB) ?
The external is on another physical server and is mapped.
Thanks
errorlog.txt
0
 
AlanConsultantCommented:
Hi Pierre,

If it was due to a large number of exports, then you would not have gotten the error when exporting a single mailbox as you did above.

Also, you confirmed above that you have tried this on more than one external share, and also the local C:\ drive, so there is no realistic probability that this is due to the destination.

The command you are using works for some mailboxes, so there is nothing wrong with the command either.

That only leaves the mailboxes themselves.

You also state that a mailbox that previously exported okay, later failed.

That all says to me that you have some process running that is causing the problem.

Can you disable any / all third-party software you have installed on your Exchange Server such as, but not limited to, anti-virus or spam filtering, then try again with a mailbox that was failing, and post back the result of that test.

Thanks,

Alan.
0
 
timgreen7077Exchange EngineerCommented:
I was looking at the logs and you have different errors from your export attempts. you have network errors, destination not found errors, and an excessive amount of corrupt mail items. It seems that different things are happening when you attempt the exports.  I would suggest adding the -baditemlimit parameter along with the -acceptlargedataloss. Set the -baditemlimit to 200 (-baditemlimit 200), and only add the -acceptlargedataloss. If you already added the -baditemlimit and its over 50 then you will need to add the -acceptlargedataloss parameter also.

Note: Also please make sure that you don't have any anti-virus software running and if so please disable it while you perform the export.

This is how your cmdlets should look.
New-MailboxExportRequest -Mailbox pammoun -FilePath \\Srv1\Sharedpst\Pammoun.pst -baditemlimit 200 -acceptlargedataloss

Also make sure that outlook doesn't have the mailbox open when exporting. Export the mailbox that isn't currently being used by a user in outlook or OWA.
0
 
Pierre AmmounAuthor Commented:
Dears,

I have nothing running on the server. No antivirus.
All I have is the following:
Firefox
Office 2016
Teamviewer
0
 
Pierre AmmounAuthor Commented:
I tried to run 3 mailboxes that failed one after the other and they completed successfully.
I ran that command
New-MailboxExportRequest -Mailbox pammoun -FilePath \\Srv1\Sharedpst\Pammoun.pst -baditemlimit 200 -acceptlargedataloss
But I have 3 problems now :-)
* How come that if I run then separately the complete successfully ? (I chose the biggest Mailboxes !)
* It is difficult for me to know which user is having his outlook open or OWA. I have many users that live abroad and in different time zones !
  Can't I export their mailboxes if it is open ?

* Using the flag acceptlargedataloss  : What really does it mean ? is my EDB Corrupt ? How do I fix it ? How do I "clean" or check my EDB(s) for consistency ? There used to be isinteg, but I think it is not recommended anymore ? Any alternative ?
Thanks.
0
 
timgreen7077Exchange EngineerCommented:
Acceptlargedataloss works with baditemslimit parameter. If you have have over 50 baditems or corrupt mail items, the move will fail unless you add the acceptlargedataloss parameter also.

Sometimes I have had issues when exporting mailboxes that the user was actively using. I would get an error showing the mailbox was locked but once they closed outlook it was successful.

Have you tried exporting your own mailbox to a pst? Try it and see if successful.
0
 
tom luiesCommented:
0
 
Pierre AmmounAuthor Commented:
This is the only solution that provided a work around !
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

  • 10
  • 8
  • 6
  • +7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now