Exchange 2010: Unable to Export mailbox using New-MailboxExportRequest

Good Morning, Experts!

So, I am attempting to export some Mailboxes using Exchange Powershell and the New-MailboxExportRequest process. However, whenever I attempt to export the mailbox, I get the following error:

"There aren't any available servers running the Mailbox Replication Service"

I have verified the following:

- The Exchange 2010 Server Microsoft Exchange Replication service is running. The server has been rebooted a couple of times since first encountering this error, so the Service has been restarted numerous times.

- The Target server (where the .PST files are being exported to) has the Net. Tcp Port Sharing Service, and that service is Started. Restarting the service does not help.

- Running Test-MRSHealth results in the following output:

Check: Service Check
Passed: True
Message: The Mailbox Replication Service is running.
IsValid: <Exchange Server>
ObjectState: New

Check: RPCPingCheck
Passed: False
Message: The RPC endpoint for the Microsoft Exchange Mailbox Replication service
couldn's respond: The call to 'net.tcp://<Exchange Server>/Microsoft.Exchange.MailboxReplicationService' failed.
Error details: Access is denied..  --> Access is denied..
Identity: <Exchange Server>
IsValid: True
ObjectState: New

Check: QueueScanCheck
Passed: True
Message: The Microsoft Exchange Mailbox Replication service is scanning mailbox database queues for jobs.
Lase scan age: 00:06:47.2226905.
Identity: <Exchange Server>
IsValid: True
ObjectState: New

I am part of the Domain Admins and Enterprise Admins groups, and the target file share has Full Control access for the Exchange Servers and Exchange Trusted Subsystem groups, as well as the Administrators group.

Any assistance would be greatly appreciated! Thank you in advance.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
Did you also assign yourself or a group that you are part of to the "Import Export Role"? This is also required to run the command New-MailboxExportRequest cmdlet.

WoodraxAuthor Commented:
Yes, the following command has already been run on my account:

New-ManagementRoleAssignment –Role “Mailbox Import Export” –User “username”

I have run the Get-ManagementRoleAssignment -Role "Mailbox Import Export" -GetEffectiveUsers command, and can see my name listed.
Will SzymkowskiSenior Solution ArchitectCommented:
Can you confirm what Service Pack versions all of your Exchange servers are running? Also what RU are they running as well?

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

WoodraxAuthor Commented:
Exchange 2010 SP 3, Rollup 8
Will SzymkowskiSenior Solution ArchitectCommented:
Have you tried looking in the logs on the mailbox database server? ALL services on ALL Exchange servers are started? Have you also checked that all of the App Pools have also been started properly?

I am assuming that you are running this on your remote machine? If you try to run this commnad directly from the Exchange server does it work?

Check those things and post back.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
WoodraxAuthor Commented:
Bingo! Looks like running the command directly from the server resolved the issue. Will have to dig deeper, and see why this is the case.

You are an Exchange Ninja, Will. Thank you very much for your assistance.

WoodraxAuthor Commented:
I very much appreciate the very quick responses from Will. Thanks again for a great solution, Experts Exchange community.
Will SzymkowskiSenior Solution ArchitectCommented:
Excellent! Glad I could help!

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.