Mailbox move requests remain in Queued status

My server is part of a two member DAG.  DAG shows to be healthy.  I have turned logging up to Expert level but no useful data is generated (only shows that the move request was created; no problems are indicated)
Server is Exchange 2010 SP 3 

Hi,
Please check the database copy status under management tab on source database and target database. This can be that one or more of those databases you are moving mailboxes to has a failed or suspended copy and its failing the DataMoveReplicationConstraint
check.
Refer to this blog about Exchange 2010 Mailbox Moves and Mailbox Resiliency
http://blogs.technet.com/b/exchange/archive/2011/05/06/exchange-2010-mailbox-moves-and-mailbox-resiliency.aspx
In addition, please check the event log on the Client Access server running the instance of the Microsoft Exchange Mailbox Replication service that's processing the failed move request.
Best Regards.

Similar Messages

  • New mailbox move request Exchange 2010 : queued

    I have deployed new Exchange 2010 server in Exchange 2003 Organization.  It is simple setup one Exchange 2003 and   New Exchange 2010.
    I was trying to move mailbox from Exchange 2003 to 2010 and it has status of QUEUE “indefinetly”.. I have tried several mailboxes  and result is the same.
    Then I decided to create new database on Exchange 2010 sever. I have crate new mailbox on Exchange 2010 sever, send and receive some emails. And then try to move mailbox to new database. Same results.
    I run test MSR replication and is ok.
    I have increase msr LOGGING TO Maximum, no errors. I have rebooted server several times, no differences…

    Hi,
    Based on the description, status of mailbox move request from Exchange 2003 to Exchange 2010 is "indefinitely".
    Please make sure mailbox databases in Exchange 2010 and Exchange 2003 are mounted.
    Have you moved mailbox using the New-MoveRequest with the BadItemLimit and the AcceptLargeDataLoss parameters? If not, it's worth to do it again. Before you create a new move request, please check if there is any previous move request. If there is, please
    clear the previous move request and then move the mailbox.
    If the issue persists, please try to move mailbox to another database in Exchange 2003 and then move to Exchange 2010 to check the result.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Problem transport requests remain in queue

    Hello
    I have problem as transport requests remain in queue of QAS and does not advance in approwal list. Problem began  after /usr/sap/trans was full
    Now trnasport are imported correcly but remain in queue of QAS and does not advance in approwal list. Problem began

    Hi Jan,
    Talk to your Basis team as this is basic config.This is happening because import queue is inconsistant. Check this thread - STMS: Transport Requests Forever Stuck to Running
    Regards,
    Sen

  • Exchange 2013 shell mailbox move requests showing up on 2010 hub server

    We're in the process of migrating from exchange 2010 to 2013. All servers are patched and up to date. We have two 2010 CASs (one for external OWA use only) and a mailbox cluster. Our exchange 2013 setup is almost a mirror with the exceptions of how the exchange
    server roles have changed.
    Any new-moverequest commands entered from the either of our exchange 2013 CAS servers fail to show up in the EAC/recipients/migration page.
    If the local move request is done in the EAC the batch(es) show up just fine.
    The more perplexing part is: while I was going through a 2010 hub (looking for a different issue) I noticed ALL the batches/mailbox moves that weren't showing up in the 2013 EAC were listed in the 2010 move request section.
    I can't get any info on the moves in the 2010 console (because they're 2013 jobs) but i can get statistics and such from a 2013 shell.
    any ideas?

    Are you running ex2013SP1 CU6? Can you try to update n check?
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • How to remove failed mailbox move request

    Hi all,
    Exchange 2010 SP1
    i canceled or move failed on several mailboxes.  How can I move these mailboxes again since
    they still have move request checked?
    Thank you.

    Hi JaneHHH,
    Here are some examples:
    To just remove the failed moverequests in EMS, RUN Get-Moverequest -MoveStatus Failed | remove-moverequest
    Move all moverequests in EMS, RUN get-moverequest | remove-moverequest
    You can of course also remove them in EMC, but a simple right-click the once you want to move in EMC|Recipient Configuration|Move Requests and choose "Clear Move Requests"
    :Martina
    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.

  • Data Request remains in yellow status after RSAPO_CLOSE_TRANS_REQUEST

    Dear all,
    I am working on BI 7.0 and I need to load data from a Real-Time Cube (in planning mode) to a Standard Cube. I am using a Process Chain with a program which calls function module RSAPO_CLOSE_TRANS_REQUEST providing the technical name of the Real-Time cube to this function module. I see that this function module works in general, because afterwards I see the number of data records transferred and added appearing in the data request. However, the status of the data request is still yellow. In order to load the data from this cube to another it has to be in green. It is not acceptable to do this manually, it has to be automated. Data entry on the Planning Cube is via a BI-IP Query. The data arrives correctly in the cube, when checking the InfoCube content the data appears to be fine.
    I have used this function module in many projects without such a problem. Does anyone have an idea why the data request is not set in green status?
    I have also tried to use the function modules RSAPO_SWITCH_TRANS_TO_BATCH and RSAPO_SWITCH_BATCH_TO_TRANS to convert from Planning mode to normal mode and then back from normal to planning mode. The result is the same, data request remains yellow.
    Many thanks for your help
    Claas

    Thanks Rishi,
    I have tried this with the standard Process Chain steps to switch the mode, but the issue remains. It first switches the Cube to Load-Mode, I see data records in the request being added to the cube, the next step tries to switch the cube back into Planning mode, This step now gives an error because the data request is in yellow status, so the cube cannot be switched back to planning.
    Error Message:
    Request APO_R4EX2HO4TYDLBCNQPQY82K8ZOJ(0000020181) is yellow or red in InfoCube DRI_P301; cannot switch to planning
    Message no. RSM068
    The Problem is that after the Cube was switched to Load-mode the request is still yellow.
    I do not understand why data records get added to the cube but the request does not get turned into green status. Any more ideas?
    Cheers
    Claas
    Edited by: Claas Bartels on Aug 29, 2009 10:29 PM

  • MailBox Move Request Statistics

    Hello,
    I am performing some mailbox moves on one of our systems here in testing for a migration. I believe I need to increase the number of CPUs on the virtual machine I am using but wanted to ask to be sure. Currently we have one of the return values of Get-MoveRequestStatistics
    for a user showing as:
    TotalStalledDueToWriteCpu              : 00:22:36
    Does this mean the move is waiting on CPU?
    Thank you,
    Brent

    Hello Brent,
    Yes, this does potentially indicate the CPU resource issue on your VM.
    Also couple of points to note from virtualization best practice/recommendation prospective...
    Many hardware virtualization products allow you to specify the number of virtual processors that should be allocated to each guest virtual machine. The virtual processors located in the guest virtual machine share a fixed number of logical processors in
    the physical system. Exchange supports a virtual processor-to-logical processor ratio no greater than 2:1, although we recommend a ratio of 1:1. For example, a dual processor system using quad core processors contains a total of 8 logical processors in the
    host system. On a system with this configuration, don't allocate more than a total of 16 virtual processors to all guest virtual machines combined.
    When calculating the total number of virtual processors required by the host machine, you must also account for both I/O and operating system requirements. In most cases, the equivalent number of virtual processors required in the host operating system for
    a system hosting Exchange virtual machines is 2. This value should be used as a baseline for the host operating system virtual processor when calculating the overall ratio of physical cores to virtual processors. If performance monitoring of the host operating
    system indicates you're consuming more processor utilization than the equivalent of 2 processors, you should reduce the count of virtual processors assigned to guest virtual machines accordingly and verify that the overall virtual processor-to-physical core
    ratio is no greater than 2:1.
    Refer:
    Exchange 2013 Virtualization
    Blog |
    Get Your Exchange Powershell Tip of the Day from here

  • Exchange 2010 to 2013 migration: Mailbox move requests are journaled.

    Hello,
    I've installed Exchange 2013 into Exchange 2010 infrastructure
    [ single Exchange 2010 server; single AD site; AD = 2003 ],
    Exchange 2010 has 2 databases:
    1. Database with users mailboxes;    Journaling YES: Journal account.
    2. Database with 1 mailbox for Journal user mentioned above:     Journaling NO.
    Exchange 2013 has 1 database:
    1. Database with moved users mailboxes;    Journaling YES: Journal account.
    I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !
    I logged into Journal mailbox by OWA and didn't see any duplicate messages concerned with this mailbox user...
    I'd like:
    * to understand technically what happened,
    * to avoid unnecessary growth of Journal Database.
    I'd like not to switch off journaling for all users during mailbox move.
    best regards Janusz Such

    Hello Winnie,
    your understanding is not correct:
    I move mailboxes from first DATABASE which is journaled;
    second database is dedicated solely for Journal user's mailbox and is not touched now.
    Thank you for PS commands; I'll use them...
    best regards Janusz Such
    Hi Janusz,
    Sorry for my delay. In your original posting, "I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !"
    My understanding is that when you move mailbox from Exchange 2010 Database 1 to Exchange 2013 database, the journal mailbox in Exchange 2010 Database 2 is incleased. Is it right?
    Generally, the mailbox move would not be journaled unless there is any new email bening sent to the mailbox during the migration. Please run the commands in my original posting to check the statistics about it, and refer to Ed Crowdly's suggestion to use
    Journal rule instead of database journal as a workaround.
    Regards,
    Winnie Liang
    TechNet Community Support

  • [SOLVED] Mailbox import requests stuck in 'queued' state

    We have a small Exchange 2013 environment with one server having all roles. I try to import archive mailboxes from an Exchange 2010 environment. It has worked quite well for a while. However, all import requests are now 'stuck' in 'queued' state. Restart
    of Replication service, transport service and even server reboot didn't help.
    When I run
    get-mailboximportrequest | Get-MailboxImportRequestStatistics -Includereport | fl
    I observe that PositionInQueue value tells me that there are 85 import requests waiting :
    ItemsTransferred                       :
    PercentComplete                        : 0
    CompletedRequestAgeLimit               : 30.00:00:00
    PositionInQueue                        : 85/90 (Position/Queue Length)
    InternalFlags                          : None
    FailureCode                            :
    There should be no requests waiting as I removed all requests in advance before I issued new import requests:
    get-mailboximportrequest | Remove-MailboxImportRequest
    How can I really reset an import queue by zeroing PositionInQueue ?
    Any suggestions/tips?

    Hi,
    Glade to hear the good news. Thanks for your update.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact 
    [email protected]
    Belinda Ma
    TechNet Community Support

  • Mailbox move request missing

    Dear Forum Members,
    We have two Exchange 2013 servers, with two databases in a DAG configuration. Now one of them appears to be almost full, so we decided to move one 4Gb mailbox to the other database. This should be kind of routine job, but after I create the migration task,
    it completes without any error, but the total number of migrated mailboxes are zero! It looks like as if I never selected that mailbox for migration, furthermore, it looks like an empty migration job :O
    Has already anyone seen this behaviour? I can't really find information about this anywhere.
    Thank you really for your help,
    Best Regards,
    Chrsitian

    Hi Chrsitian,
    How about the result if moving the mailbox via EMS command?
    New-MoveRequest -Identity "UserName" -TargetDatabase "DBName" -BadItemLimit 100 -AcceptLargeDataLoss
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Niko Cheng
    TechNet Community Support

  • Mailbox move request error

    Hi
    I moved 95 mailboxes from 2003 to 2010 without errors, but the last one are stopped with:
    Failed
    Error:
    Active Directory operation failed on sth-ad01.xxxxx.br. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
    Active directory response: 00002098: SecErr: DSID-03150E48, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
    Exchange Management Shell command attempted:
    'xxxxx.br/MyBusiness/Users/useralias' | New-MoveRequest -TargetDatabase 'Mailbox Database 1591777605'
    If I go to 2003 DC, on the User's Exchange Advanced tab, Mailbox Rights,
    Exchange Servers have a DENY on Full Mailbox Access, but it's not possible to remove that (inherit).
    Any Ideas?
    This topic first appeared in the Spiceworks Community

    Hi
    I moved 95 mailboxes from 2003 to 2010 without errors, but the last one are stopped with:
    Failed
    Error:
    Active Directory operation failed on sth-ad01.xxxxx.br. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
    Active directory response: 00002098: SecErr: DSID-03150E48, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
    Exchange Management Shell command attempted:
    'xxxxx.br/MyBusiness/Users/useralias' | New-MoveRequest -TargetDatabase 'Mailbox Database 1591777605'
    If I go to 2003 DC, on the User's Exchange Advanced tab, Mailbox Rights,
    Exchange Servers have a DENY on Full Mailbox Access, but it's not possible to remove that (inherit).
    Any Ideas?
    This topic first appeared in the Spiceworks Community

  • Exchange crash during move request, new DB in dirty shutdown

    I had a hardware failure (storage controller in VM environment) during a mailbox move request to a new DB.  After fixing that and rebooting, the old database came up and is fine which is great.  The new database is in a dirty shutdown state right now with a few completed but most are still queued or in progress.  If I try to remove the request on the completed mailboxes it has a message along the lines of, couldn't connect to mailbox database, it could be dismounted.  Do you want to orphan the move request for user XYZ?
    Will this cause any problems?  I would like to remove the move requests and proceed recovery and repair of the dismounted DB.  Thoughts?
    Thanks,
    Josh
    This topic first appeared in the Spiceworks Community

    Hi,
    Thank you for sharing the resolution.
    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. Thanks Gen Lin-MSFT

  • Should cancelled mailbox moves result in any moved mail data removed from target server?

    I was moving mailboxes from 1 DB to another. 3 out of 120 were left running for 12 hours; they were the biggest ones and it was very slow to process the items. There were also reports of slowness on the server so I had no choice but to cancel the moves.
    My question is should cancelled mailbox moves result in any moved mail data being removed from the target database? It doesn't appear that my disk as increased in space again so I'm wondering if it's there as whitespace maybe? There is an event logged to say
    the mailbox has been deleted from the target.
    Would appreciate if someone can clear this up and possibly explain exactly what occurs during this type of scenario.
    Thanks.

    Hi,
    Thank you for your kindly remind.
    In Exchange 2000, 2003 and 2007 mailboxes become unavailable during movement, when a mailbox move takes place, the mailbox isn't actually moved, it's just copied to the destination location. Once that copy has finished, AD is updated to point to the new location
    and the old mailbox is deleted from the source EDB file.
    The most different between Exchange 2010 and legacy version in move mailbox is that allows end-users to be online in their email accounts. On completing the move users just needs to reopen their Outlook clients.
    Mailbox Move Requests are a new feature set of Exchange 2010 and requires running a series of Cmdlets to perform asynchronous online mailbox moves with the help of a service agent called Mailbox Replication Service (MRS). MRS is available on all Exchange 2010
    Client Access Servers.
    Best Regards,
    Allen Wang

  • PSA load remains in yellow status.

    Hi Gurus,
    I have created a generic datasource based  on function module.
    I have replicated the datasource in  SAP BI dev instance.
    I have even checked the extractor checker in R/3 and it shows 381 records.
    On BI side I am loading data upto PSA.When I execute the infopackage for full load in the monitor screen I could see
    "381 out of 0 records".The request remains in yellow status.
    The idoc status in source system side is 03 and on BI side is 53.
    I dont get any error message.Even I am not seeing idocs with red status in SM58 tcode.No logs are seen in sm21.
    I even asked the basis team to check for RFC connection SM59 and partner profile.Every thing looks fine .
    This loading issue is only happening with this specific datasource(ie datasource created on function module).
    For other datasources load are carried out fine.
    Has anybody faced a similar issue?.Please help in this regard.

    seems the load is hung bcoz of thehung IDOCs.
    Process the idocs manually. after
    check the below things
    --> Check weather the source system job finished or not?
    If the job is finished check the TRFCs are processed or not?
    In the monitor screen - menu bar --environment -->job overview (to check the job) -->TRFcs - to check the TRFCs.
    Check for short dumps using transaction ST22.
    -->Check for the Idocs in BD87 and if there are any IDOCs got stuck process them manually.
    To process Idocs first change the status of request to red and try to process them in the background.

  • Local move requests stuck with status "queued" at 0% completion

    Hello all,
    I'm running Exchange server 2010 SP3 with no aditonal RU.
    Suddenly we are unable to perform local move requests of mailboxes between databases.
    The requests will turn up in the list at Recipient "Configuration\Move Requests" but remain the with status Queued with 0% completion.
    It does not matter if the move request is initiated by EMC of the Shell.
    I cant find a solution so if someone has some advise that would be great,
    I tried the following:
    - Restarted the Mailbox Replication service on the CAS server
    - Rebooted the Mailbox, CAS and Edge server
    - Run a Test-MRSHealth check against the CAS
    - Checked all logs but there are no related entries
    - Checked my admin account permissions
    - Checked if it is related to certain mailboxes and source and destination databases which isn't the case
    What else can I do or check?
    Kind regards,
    Alex

    Hi,
    You mentioned you checked the event log, but there was no related events.
    Have you tried to use the get-moverequest | get-moverequeststatistics cmdlet to check result?
    If no, please run this command to see if there is any clues that can be used to narrow down this issue.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

Maybe you are looking for