MSExchange Mailbox Replication Error 1121

By | January 28, 2015

I recently had a interesting issue where I was seeing the 1121 error below in the Application log on one of my Exchange 2013 servers every minute.


Log Name: Application
Source: MSExchange Mailbox Replication
Date: 14/01/2015 2:23:34 p.m.
Event ID: 1121
Task Category: Request
Level: Error
Keywords: Classic
User: N/A
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '60b5375b-0f27-4561-a0f2-af428dd3c501'
Database GUID: '43ce3977-2c7f-4c6a-937b-b94966c81122'
Error: An Active Directory Constraint Violation error occurred on Additional information: The name reference is invalid.
This may be caused by replication latency between Active Directory domain controllers.
Active directory response: 000020B5: AtrErr: DSID-03152CB1, #1:
0: 000020B5: DSID-03152CB1, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 9fc1287c (msExchMailboxMoveSourceMDBLink)
--> A value in the request is invalid..

The reference to “msExchMailboxMoveSourceMDBLink” was the only indication the error related to a mailbox move request. Frustratingly, no requests showed up from running Get-MoveRequest.

After some ineffective troubleshooting I eventually found the solution from Exchange MVP Jeff Guillet. The error message he shows in his article is different to mine, but the fix is the same.

I had to run the following command:

Remove-MoveRequest -MoveRequestQueue '43ce3977-2c7f-4c6a-937b-b94966c81122' -MailboxGuid '60b5375b-0f27-4561-a0f2-af428dd3c501'

I still don’t know the cause of the problem, but I have a suspicion it followed a reverse mailbox move from Exchange 2013 (CU6) to Exchange 2007 (SP3 RU13).

Hopefully this helps if you ever come across the same issue.

3 thoughts on “MSExchange Mailbox Replication Error 1121

  1. DrWellyKen

    Good to know we have just migrating from the same 07 and 13 platforms 🙂

  2. Josh

    They for the heads up. Anyway to clear all of them without specifying the GUID? I have thousands of these. I am going through them 1 by 1, but it is a process.

  3. Paul

    Thanks for this. Had the same problem in my domain after a Ex 2003 & 2007 migration to EX 2013. The above command fixed the constant stream of errors on the Ex 2013 server.


Leave a Reply to Paul Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.