asked on
Exchange 2010 Move Requests stuck as Queued after SP3 RU4 install
Installed Exchange 2010 SP3 and subsequently Rollup 4. After installation, new move requests remain queued indefinitely. Have tried the following:
1. Re-prepping AD (setup /p)
2. Checking the MRS configs on each CAS server (config file parameters are set to 5 simultaneous moves)
3. Verified health of all DBs and copies for source and destination
4. Rebooted all CAS servers
5. Moved all databases back and forth between DAG nodes.
6. Increased MRS logging to Expert level but nothing appears in Event Viewer except for stop and start of MRS service.
7. Checked move request logs
8. Checked Exchange permissions inheritance on all OUs and objects.
9. Targeted move requests to specific CAS servers with -MRSServer
While the mailboxes are flagged with move parameters in AD, the CAS servers do not seem to be picking up the move request.
In all cases, the request remains queued and the only verbage in the request logs is "<Date/Time> <user DN> created move request".
I'm half tempted to tear out Rollup 4 but would prefer not to.
Any suggestions would be most appreciated.
1. Re-prepping AD (setup /p)
2. Checking the MRS configs on each CAS server (config file parameters are set to 5 simultaneous moves)
3. Verified health of all DBs and copies for source and destination
4. Rebooted all CAS servers
5. Moved all databases back and forth between DAG nodes.
6. Increased MRS logging to Expert level but nothing appears in Event Viewer except for stop and start of MRS service.
7. Checked move request logs
8. Checked Exchange permissions inheritance on all OUs and objects.
9. Targeted move requests to specific CAS servers with -MRSServer
While the mailboxes are flagged with move parameters in AD, the CAS servers do not seem to be picking up the move request.
In all cases, the request remains queued and the only verbage in the request logs is "<Date/Time> <user DN> created move request".
I'm half tempted to tear out Rollup 4 but would prefer not to.
Any suggestions would be most appreciated.
Exchange
Last Comment
Strateric
Where are you moving from? Another 2010 server, another database on the same server, an older version of Exchange. If an older version of Exchange it may not recognize the latest rollup on 2010. Also, I assume all your 2010 servers are on this rollup now?
ASKER
From one database to another in same DAG. All servers are SP3 RU4.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Removed RU4 from one of the CAS servers and targeted that CAS for MRS and the moves went through without issue. Targeted another CAS that still had RU4 and problem still persisted. Ultimately removed RU4 from all the CAS and MBX servers.
As per my knowledge RU4 is not yet released for Exchange Server 2010 SP3.
Please try reverting the change and check.