• Home
  • Topics
    • Office 365
    • Teams
    • SharePoint
    • Exchange 2019
    • Exchange 2016
    • Exchange 2013
    • Hybrid
    • Certificates
    • PowerShell
    • Migration
    • Security
    • Azure
  • Blog
  • Podcast
  • Webinars
  • Books
  • About
  • Subscribe
    • Facebook
    • Twitter
    • RSS
    • YouTube

Practical 365

You are here: Home / Exchange Server / Exchange 2010 Local Move Request Fails with No Available Mailbox Replication Service Error

Exchange 2010 Local Move Request Fails with No Available Mailbox Replication Service Error

August 14, 2011 by Paul Cunningham 4 Comments

When you attempt to create a new local move request in Exchange Server 2010 to move a mailbox you may encounter this error:

There are no available servers running the Microsoft Exchange Mailbox Replication service.

Mailbox move requests are handled by the Microsoft Exchange Mailbox Replication service which is part of the Client Access server role. In order for a move request to be successfully created at least one Client Access server within the same Active Directory site must have a running Mailbox Replication service.

Start the MRS on at least one Client Access server. If it will not start the issue may be that the Net.Tcp Port Sharing service is disabled on the Client Access server. If that is the case then run the following command on the Client Access server in a PowerShell window.

1
PS C:\> Set-Service NetTcpPortSharing -StartupType Automatic

Restart the Client Access server, or manually start the MRS, and then retry the move request again.

Exchange Server Client Access, Exchange 2010, Mailbox

Comments

  1. Fawad Ameer says

    May 22, 2014 at 5:02 pm

    Dear Paul,

    i am facing error in Move request “Failed in 15%” in some mailbox while i moving them into another DB and some mailbox become move successfully in same DB.

    Error: MapiExceptionCallFailed: Unable to synchronize manifest. (hr=0x80004005, ec=-1119)
    Diagnostic context:
    Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=239]
    Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=727][latency=358]
    Lid: 23226 — ROP Parse Start —
    Lid: 27962 ROP: ropIncrCfg [112]
    Lid: 27962 ROP: ropUpldStStrmBegin [117]
    Lid: 27962 ROP: ropUpldStStrmEnd [119]
    Lid: 27962 ROP: ropUpldStStrmBegin [117]
    Lid: 27962 ROP: ropUpldStStrmEnd [119]
    Lid: 27962 ROP: ropUpldStStrmBegin [117]
    Lid: 27962 ROP: ropUpldStStrmEnd [119]
    Lid: 27962 ROP: ropUpldStStrmBegin [117]
    Lid: 27962 ROP: ropUpldStStrmEnd [119]
    Lid: 27962 ROP: ropFXSrcGetBufferEx [156]
    Lid: 17082 ROP Error: 0xFFFFFBA1
    Lid: 23137
    Lid: 21921 StoreEc: 0xFFFFFBA1
    Lid: 27962 ROP: ropExtendedError [250]
    Lid: 1494 —- Remote Context Beg —-
    Lid: 1238 Remote Context Overflow
    Lid: 32865
    Lid: 41897 StoreEc: 0x80040117 PropTag: 0x67A61014
    Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040
    Lid: 32865
    Lid: 41897 StoreEc: 0x80040117 PropTag: 0x67A61014
    Lid: 13300 StoreEc: 0xFFFFFBA1
    Lid: 46077 dwParam: 0xA5D0B
    Lid: 46121 StoreEc: 0xFFFFFBA1
    Lid: 36333
    Lid: 44841 StoreEc: 0xFFFFFBA1
    Lid: 38697 StoreEc: 0xFFFFFBA1
    Lid: 50093 StoreEc: 0xFFFFFBA1
    Lid: 47457
    Lid: 10213 StoreEc: 0xFFFFFBA1
    Lid: 28256
    Lid: 9189 StoreEc: 0xFFFFFBA1
    Lid: 22500
    Lid: 25058 StoreEc: 0xFFFFFBA1
    Lid: 22844
    Lid: 3742 StoreEc: 0xFFFFFBA1
    Lid: 23296
    Lid: 2526 StoreEc: 0xFFFFFBA1
    Lid: 20912
    Lid: 24504 StoreEc: 0xFFFFFBA1
    Lid: 24148 StoreEc: 0xFFFFFBA1
    Lid: 23796
    Lid: 2478 StoreEc: 0xFFFFFBA1
    Lid: 1750 —- Remote Context End —-
    Lid: 26849
    Lid: 21817 ROP Failure: 0xFFFFFBA1
    Lid: 32758
    Lid: 16586 StoreEc: 0xFFFFFBA1
    Lid: 22518
    Lid: 28874 StoreEc: 0xFFFFFBA1
    Lid: 29516
    Lid: 31820 StoreEc: 0xFFFFFBA1

    Reply
  2. Nik Patel says

    October 25, 2011 at 6:59 am

    i have just encountered this error and replication services are running. Any other ideas?

    Reply
    • Paul Cunningham says

      October 27, 2011 at 8:18 pm

      Perhaps some other issue. Any evidence in your event logs?

      Reply
      • Nik says

        October 27, 2011 at 10:21 pm

        Thanks Paul but a reboot solved the issue! – never underestimate the powerr of a wintel reboot.

        Thanks for replying.

        Reply

Leave a Reply Cancel reply

You have to agree to the comment policy.

Recent Articles

  • The Practical 365 Weekly Update: S2, Ep 8 – What to expect in 2021, Solarigate, TLS in Exchange and new Teams updates
  • Security updates released for Exchange and SharePoint Servers 2010 to 2019
  • The Practical 365 Weekly Update: S2, Ep 7 – Urgent Exchange security updates, new Teams features launch
  • How to train your users against threats with Attack Simulation Training
  • Fall 2020 roundup of compliance updates
Practical 365

Related Posts

Related Posts

Training Courses

  • Configuring and Managing Office 365 Security
  • Office 365 Admin Playbook
  • Exchange 2016 Exam 70-345
  • Managing Exchange Mailboxes and Distribution Groups in PowerShell
  • More Training Courses...

Recommended Resources

  • Office 365 Security Resources
  • Office 365 Books
  • Exchange Server Books
  • Exchange Server Migrations
  • Exchange Analyzer
  • Digicert SSL Certificates

About This Site

Practical 365 is a leading site for Office 365 and Exchange Server news, tips and tutorials. Read more...

Find out more about advertising with us.

Contact us


Subscribe to our newsletter
  • Facebook
  • Twitter
  • RSS
  • YouTube

Copyright © 2021 Quadrotech Solutions AG · Disclosure · Privacy Policy
Alpenstrasse 15, 6304 Zug, Switzerland