Backing up mailboxes via PST files
I'm trying to backup the mailboxes on my exchange server 2010 running on server 2008 R2 using the script from Steve Goodman (http://www.stevieg.org/2010/07/using-the-exchange-2010-sp1-mailbox-export-features-for-mass-exports-to-pst/) But when I run the script it gives me the following error: There is no available servers running the Microsoft Exchange Mailbox Replication service. The Sevices: MSExchangeMailboxReplication and NetTcpPortSharing are running and are on automatic. I've installed Update Rollup 3 for Exchange Server 2010 (KB981401) to see if this solves the problem, but it didn't. I have 4 users that I what to back up via a PSTFile, 3 mailboxes (2 users and discover search mailbox) don't work but administrator mailbox does work. I'm stuck, dont know wath to do next.. Help would be appreciated. Cheers
June 24th, 2011 9:23am

Sturme, Have you tried just running the mailbox export request command individually to see if that works? New-MailboxExportRequest -Mailbox <alias> -FilePath \\server\share\alias.pst What are your results when you just run that? Can you include the full message returned by the server and also check the application event logs for any pertinent messages if/when you receive the error? Wes
Free Windows Admin Tool Kit Click here and download it now
June 24th, 2011 11:35am

Hi, If I try it manually it gives me the same error: There is no available servers running the Microsoft Exchange Mailbox Replication service. The log is no different: Cmdlet failed. Cmdlet New-MailboxExportRequest, parameters {Mailbox=frank, FilePath=\\srv-mail\PST\frank.ps}. Event ID 6 Event Data New-MailboxExportRequest {Mailbox=frank, FilePath=\\srv-mail\PST\frank.pst} kp-dmn.local/Users/Administrator S-1-5-21-1052662688-4217413068-2742862853-500 S-1-5-21-1052662688-4217413068-2742862853-500 ServerRemoteHost-Unknown 2208 32 00:00:01.7310990 View Entire Forest: 'False', Default Scope: 'l', Configuration Domain Controller: 'l', Preferred Global Catalog: '', Preferred Domain Controllers: '{ }' Microsoft.Exchange.MailboxReplicationService.RemotePermanentException: The server or share name specified in the path may be invalid, or the file could be locked. ---> Microsoft.Exchange.MailboxReplicationService.RemotePermanentException: The network name cannot be found. --- End of inner exception stack trace --- at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationServiceFault.<ReconstructAndThrow>b__0() at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation) at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationServiceFault.ReconstructAndThrow(String serverName) at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CallService(GenericCallDelegate del, String epAddress, VersionInformation serverVersion) at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationServiceClient.ValidateAndPopulateRequestJob(TransactionalRequestJob requestJob, List`1& entries) at Microsoft.Exchange.Management.RecipientTasks.NewRequest`1.InternalValidate() at Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest.InternalValidate() at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord() 0 Microsoft.Exchange.MailboxReplicationService.RemotePermanentException: The network name cannot be found. any thoughts?
June 27th, 2011 3:02am

Can you post a screenshot for the cmdlet error or copy the entire content in the EMS box? It could help us better understand your problem. It appears you are using a network shared folder to save the exported pst file from the event log. \\srv-mail\PST\frank.pst" & "The server or share name specified in the path may be invalid, or the file could be locked" & "network name cannot be found". ---So try to use a local folder such as c:\pstbackup\frank.pst to see if it is working (of couse make sure you have sufficient permission to create folder on driver C). -Fiona Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
June 27th, 2011 5:06am

Hi, A backup to a PST file via a local path is not possible. This is a screen shot of the error. Cheers
June 27th, 2011 6:58am

Sturme, I believe what Fiona is proposing is to try just exporting to a local drive just once to see if you get any difference in response from the system since the errors point to an issue with accessing the network share. Can you give that a shot and let us know the result? Wes
Free Windows Admin Tool Kit Click here and download it now
June 27th, 2011 2:29pm

If you look in the screen shot that I just posted, you can see that I tried to backup to a local drive. And you can see the result of that command. Cheers
June 27th, 2011 2:55pm

Sturme, My apologies for not looking at your screenshot more closely as I see you tried to back up locally but it was expecting a UNC path. If your local server is named SERVER1 can you try running the endport with the file path as: \\server1\c$\user.pst If this works then we're probably hitting a permissions issue. Can you check the Local Administrators group (and the share permissions) on the server that you're trying to export to (that's not the mail server itself?) If DOMAIN\Exchange Trusted Subsystem isn't listed in both places try adding it and then running the command again. The MRS will run under the identity of the Exchange server and this entry should give it the permissions it needs to create and modify the files on the remote server. HTH, Wes
Free Windows Admin Tool Kit Click here and download it now
June 27th, 2011 2:58pm

Doesn't matter, The location that I'm trying to backup to is located on the same server. I've tried to back up to the C drive and it works like a charm. I've already granted exchange trusted subsystem access to the folder, and I've added them to the administrator group. Still doesn't seem to work. Also what I just found out. If I backup one mailbox the service NetTcpPortSharing stops, even when its on automatic. Then I have to start it manually. Cheers
June 27th, 2011 4:05pm

Sturme, Have you granted permissions both via NTFS and Windows Share or just NTFS? Since it works well with the c$ share the only difference at this point would seem to be the share permissions. If the share permissions are there could you send us a screen shot? If not then could you add them and then try again. That's interesting about the NetTcpPortSharing service. Anything in the event logs that would indicate what requested that it stop and why? Wes
Free Windows Admin Tool Kit Click here and download it now
June 27th, 2011 4:23pm

Yes it was the permission they weren't set right. It works now. Thx But the service is still terminating, event log shows me this: The Net.Tcp Port Sharing Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 300000 milliseconds: Restart the service. Event id 7034 Event data: param1 Net.Tcp Port Sharing Service param2 2 param3 300000 param4 1 param5 Restart the service
June 27th, 2011 4:37pm

Hi Sturme, The screenshot indicates “file path c:\PST\frank.pst isn’t a valid UNC path. We all know that the format for a UNC path is \\server\volume\directory\file, so I still believe it is a permission related issue. Let’s simply the troubleshooting: 1. Try to create a new folder or file in the target folder c:\PST via the user account you run the cmdlet. Doing so could make sure your user account has sufficient permission on folder c:\PST. 2. And then, right click Exchange Management Shell and select “Run as administrator”, then try again. Hope it is useful. Best regards, Fiona LiaoPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
June 30th, 2011 2:01am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics