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.
StratericAsked:
Who is Participating?
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.

imkotteesSenior Messaging EngineerCommented:
Hi,

As per my knowledge RU4 is not yet released for Exchange Server 2010 SP3.

Please try reverting the change and check.
Gareth GudgerSolution ArchitectCommented:
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?
StratericAuthor Commented:
From one database to another in same DAG.  All servers are SP3 RU4.
Simon Butler (Sembee)ConsultantCommented:
@imkottees Exchange 2010 SP3 Rollup 4 was released in the latest patch Tuesday updates.

http://www.microsoft.com/en-gb/download/details.aspx?id=41480

Removing the rollup would be the first thing I would try. Ensure that the requests are flushed. It could be a bug with the rollup, but I haven't heard anything (although few will do changes over the holiday period).

Simon.

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
StratericAuthor Commented:
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.
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
Exchange

From novice to tech pro — start learning today.