MSExchange Mailbox Replication warning

Hello All,
Looking for some help here.
Getting these warnings that are referring to a recovery database that was created to restore a mailbox and has since been removed.
The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
Database: Missing database (026eca3b-2899-4c05-9bea-cbc5736fd93a)
Error: Database '026eca3b-2899-4c05-9bea-cbc5736fd93a' doesn't exist.
Simple environment, single mailbox server, no DAG at this point..
What am I missing?
Thanks,
Jason

Hi Jason,
As S.Nithyanandham suggested, please check if the problematic database is removed cleanly using ADSIEdit, since the Microsoft Exchange Mailbox Replication service is still looking for it. If the problematic database exists in ADSIEDit, remove it and then
restart the Microsoft Exchange Mailbox Replication service and check the result.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Similar Messages

EventID: 1006 Source: MSExchange Mailbox Replication

Hi All,
On my Exchange 2010 i see the following Events in the Application Log.
The Mailbox Replication service was unable to process mailbox move requests in a mailbox database.
Database: MDB01
Error: Couldn't find system mailbox 'SystemMailbox{e0e13cb6-bd1c-4a67-b483-3fe8db9d3631}' in Active Directory.
But when i look at the Arbitration Mailboxes it's there.
[PS] C:\Windows\system32>Get-Mailbox -Arbitration | fl Name
Name : FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042
Name : SystemMailbox{A89BCF10-3F08-41C2-AC86-68E35C08D972}
Name : SystemMailbox{e0e13cb6-bd1c-4a67-b483-3fe8db9d3631}
Any ideas out there?
Regards Andres
-- MCSE 2003 MCSA 2003 Messaging MCITP: Enterpise Administrator MCTS: Windows Server 2008 MCTS: Exchange Server 2007 Configuration MCTS: Microsoft SQL Server 2005 VCP - VMWare Certified Professional

Hi Andres,
The arbitration mailboxes in your product environment are not created by a correct way. I suggest you delete all of them and recreate them.
1. Delete those AD accounts.
2. Run Setup.com /PrepareAD. The arbitration accounts will be recreated after this step.
3. Enable those mailboxes with the following commands.
-   Enable-Mailbox –Arbitration –Identity “SystemMailbox{1f05a927-…}”
-   Enable-Mailbox –Arbitration –Identity “SystemMailbox{e0dc1c29-…}”
-   Set-mailbox –Arbitration –Identity “SystemMailbox{e0dc1c29-…}” -DisplayName “Microsoft Exchange”
Then please test the issue again. Thanks,
Elvis

Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database 1006.

HI all,
I ran into a problem with one of the servers in my DAG. Due to a backup failure, the log partition filled up and the Exchange database went offline on this particular server. The DAG continued to function on the other server. So this particular
DB01 had only some test accounts in it so I removed the database copy. Unfortunately the removal must not have completed correctly.
After recovering the needed space in the partition, I tried to recopy the database and it failed. So I deleted the entire database from the active server and it successfully removed it from the active server. Now on both the servers the database
is not showing, however I'm receiving the error below which indicates to me that the service still thinks the database exists. I am also getting event 4113 Database redundancy health check failed for the database copy as it shows there is only one copy
of the database (failed redundancy) but there should be zero copies.
This database no longer exists in AD as I have verified this with ADSI so it must have something on the exchange server that is still telling the service the database exists.
Can you point me to the location to clean this up?
Log Name:      Application
Source:        MSExchange Mailbox Replication
Date:          02/25/2011 2:00:07 PM
Event ID:      1006
Task Category: Service
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      email1.domain.com
Description:
The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
Database: DB01
Error: MapiExceptionUnknownUser: Unable to open message store. (hr=0x80004005, ec=1003)
Diagnostic context:
    Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=243]
    Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=200][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropLogon [254]
    Lid: 17082   ROP Error: 0x3EB
    Lid: 26937
    Lid: 21921   StoreEc: 0x3EB
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 22086
    Lid: 27206
    Lid: 17990
    Lid: 16966   StoreEc: 0x8004010F
    Lid: 31433   StoreEc: 0x8004010F
    Lid: 8620    StoreEc: 0x3EB
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849
    Lid: 21817   ROP Failure: 0x3EB
    Lid: 26297
    Lid: 16585   StoreEc: 0x3EB
    Lid: 32441
    Lid: 1706    StoreEc: 0x3EB
    Lid: 24761
    Lid: 20665   StoreEc: 0x3EB
    Lid: 25785
    Lid: 29881   StoreEc: 0x3EB
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchange Mailbox Replication" />
    <EventID Qualifiers="32772">1006</EventID>
    <Level>3</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-02-25T22:00:07.000000000Z" />
    <EventRecordID>181576</EventRecordID>
    <Channel>Application</Channel>
    <Computer>email1.domain.com</Computer>
    <Security />
</System>
<EventData>
    <Data>DB01</Data>
    <Data>MapiExceptionUnknownUser: Unable to open message store. (hr=0x80004005, ec=1003)
Diagnostic context:
    Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=243]
    Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=200][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropLogon [254]
    Lid: 17082   ROP Error: 0x3EB
    Lid: 26937
    Lid: 21921   StoreEc: 0x3EB
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 22086
    Lid: 27206
    Lid: 17990
    Lid: 16966   StoreEc: 0x8004010F
    Lid: 31433   StoreEc: 0x8004010F
    Lid: 8620    StoreEc: 0x3EB
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849
    Lid: 21817   ROP Failure: 0x3EB
    Lid: 26297
    Lid: 16585   StoreEc: 0x3EB
    Lid: 32441
    Lid: 1706    StoreEc: 0x3EB
    Lid: 24761
    Lid: 20665   StoreEc: 0x3EB
    Lid: 25785
    Lid: 29881   StoreEc: 0x3EB     </Data>
</EventData>
</Event>

Hi
This error occurs because the MailboxReplicationService (MRS) currently caches Mailbox Database information past the lifetime of some databases.
Restarting the service will clear the cache.
Maybe it is the simplest way to solve it.
If it doesn’t work, you can try cmd to check it.
Get-MailboxDatabase : Can you find the database which you delete?
Remove-MailboxDatabase -Identity "MyDatabase": You can try to delete database if you can see the database.

The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error

Since demoting a child domain a few days ago, Exchange 2013 is still trying to contact it and as a result generating errors in the application event logs. I had a similar problem which I solved by removing some old migration batches, now I have a problem
with the Microsoft Exchange Mailbox Replication service.
The event logged is:
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '0b6c0f5a-0563-48e2-8b97-e0781c6cc69a'
Database GUID: '23258311-ad29-41c2-a842-522f48baa267'
Error: Unable to read from Active Directory. --> The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Unable to find a suitable directory server for
domain 'admin.riddlesdown.local'.. --> Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Exchange Active Directory Provider could not find an available domain controller in domain admin.riddlesdown.local. This event may be caused by network connectivity issues or
configured incorrectly DNS server.
The domain doesn't exist in AD Sites and Services, I have removed all traces from DNS but this is still occurring. When I run Get-ADServerSettings | fl it reports no trace of the domain or a DC that was previously in it.
How can I stop these events occurring and is it likely to be causing something else not to work correctly.
We are running Exchange 2013 CU1

No, that didn't work. Here are more details:
Source: MSExchange ADAccess (EventID: 2130)
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Exchange Active Directory Provider could not find an available domain controller in domain admin.riddlesdown.local. This event may be caused by network connectivity issues or configured
incorrectly DNS server.
Source: MSExchange ADAccess (EventID: 2119)
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Error DNS_ERROR_RCODE_NAME_ERROR (0x8007232B) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain admin.riddlesdown.local
The query was for the SRV record for _ldap._tcp.dc._msdcs.admin.riddlesdown.local
Common causes of this error include the following:
- The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller
at set intervals. This computer is configured to use DNS servers with following IP addresses:
10.59.100.7
10.59.100.8
fec0:0:0:ffff::1Microsoft.Exchange.Directory.TopologyService.exe
fec0:0:0:ffff::2Microsoft.Exchange.Directory.TopologyService.exe
fec0:0:0:ffff::3Microsoft.Exchange.Directory.TopologyService.exe
- One or more of the following zones do not include delegation to its child zone:
admin.riddlesdown.local
riddlesdown.local
local
. (the root zone)
Source: MSExchange Mailbox Replication Service (EventID: 1121)
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '87f4b926-0621-43d3-afeb-fe475ee6d850'
Database GUID: '23258311-ad29-41c2-a842-522f48baa267'
Error: Unable to read from Active Directory. --> The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
--> Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
Something is cause the Exchange server to go looking for our old domain, but what and why?

Exchange Co-existing Migration not completing (Event ID's 1006 - Mailbox Replication, 2002 - Exchange Migration)

Hi Guys,
a few issues all relating to AD/Exchange Setup, Causeing migration issues.
quick overview:
1. installed new server (Server 2012 R2), installed exchange 2013 install completed properly, issues logging into ecp and owa, ssl certs werent created, created manually didnt solve. - scrapped that server deleted from adsi exchange administration servers
(time spent troubleshooting was 5 days)
2. fixed ca issues, re-installed server installed exchange 2013, /preparead ,system mailboxes created migration mailbox created, create mailbox db, system mailboxes are there if checked with get-mailbox -arbitration
Try to migrate, migration mailbox not found in organization (accounts were there, made sure change user password on logon was not ticked on the account and never expire was ticked, account was disabled like it should be too so no go.
delete all system accounts from ad, recreate with /preparead, enable them according to articles:
http://technet.microsoft.com/en-us/library/gg588318%28v=exchg.150%29.aspx
http://www.telnetport25.com/2013/01/quick-tiprecovering-from-a-missing-migration-mailbox-in-exchange-2013/
http://social.technet.microsoft.com/wiki/contents/articles/5317.recreate-and-enable-missing-arbitration-user-accounts-and-mailboxes-in-exchange-server-2010.aspx
http://social.technet.microsoft.com/wiki/contents/articles/6874.how-to-recreate-system-mailbox-federatedemail-discoverysearchmailbox-in-exchange-2010.aspx
get-mailbox -arbitration found all mailboxes, check w/o -arbitration and discovery mailbox was there too.
3. Tried migration again no errors in ecp, migration not starting, encountered above error id's
Error 2002 - MSExchange Migration
error info ('Migration.MigrationMailboxNotFoundException|The migration mailbox for the organization is either missing or invalid.
Error 1006 - MSExchange Mailbox Replication (ps: no dag's setup yet either)
-> error info ('The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
Database: CL1-3_Main-DB
same error for each db on the server with different mailboxes
Error: Couldn't find system mailbox '6d5f301b-7323-47c1-85eb-a76a01b9b3c0' in Active Directory.')
Error: Couldn't find system mailbox 'f6ba51f8-c076-42e9-b00f-014a1c6b3634' in Active Directory
Error: Couldn't find system mailbox 'SystemMailbox{eae9aad5-0984-440d-b37c-7a399961e171}' in Active Directory.
Error: Couldn't find system mailbox '8c6d0335-af32-41e3-86b1-e4c15fd14a23' in Active Directory.
SystemMailbox{eae9aad5-0984-440d-b37c-7a399961e171}' is in Active Directory and mail enabled according to above articles.
also received this error id 1006 - MSExchangeDiagnostics
error info ('The performance counter '\\CL1-3\LogicalDisk(HarddiskVolume17)\Free Megabytes' sustained a value of '207.00', for the '15' minute(s) interval starting at '8/22/2014 7:12:00 AM'. Additional information: None. Trigger Name:DatabaseDriveSpaceTrigger.
Instance:harddiskvolume17')
I don't want to reinstall again as i feel that would just add wood to the fire... can anyone help diagnose this?
been trying to fix this myself for over a month.
Thanks!!

Hi,
Even if you think re-installation is annoyed, I still suggest perform the re-installation.
Because fix this issue also annoyed.
Remove the Exchange server and use ADSIedit to clear it up.
Also remove the Windows server 2012 from AD.
Then re-install Windows server 2012 and Exchange 2013 server via articles from TechNet.
Thanks

The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error. Event 1121

Hello all,
We migrated our Exchange server from 2003 to 2010. After the mailbox move requests were finished we had one that was stuck. We basically skipped it as we had a lot of other things to finish over the weekend. Here we are a year later, the old exchange server
is gone and so is an old DC. I am receiving an error every four minutes in event viewer.
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '3e46b7cb-2ac0-42c1-98e8-57517a19ee40'
Database GUID: '5c6c573b-4f45-4ce3-b296-11cf69c2e2b6'
Error: Unable to find 'OLD Domain Controller' computer information in domain controller 'OLD Domain Controller' to perform the suitability check. Verify the fully qualified domain name..
I have checked in EMC for move requests. None are listed. I have checked the DCs listed in EMC properties. Old DC is not listed.
I also ran these commands in shell to attempt to cancel the stuck request.
Get-MoveRequest -MoveStatus Completed;Pending;InProgress;Failed;CompletedWithWarning;Suspended;Queued;CompletionWithProgress : Remove-MoveRequest
NO changes. Still throwing error. Any suggestions? I also tried using the guid and shell to look at the move request. Systems replies no such request.

Hello,
Please try to restart iis services to check the result.
If the issue persists, I recommend you ping you DC server on your exchange server to check if your exchange server can communicate with your DC server.
If there are other DCs, please try to use set-adserversettings cmdlet to specify a DC for your exchange server.
Set-AdServerSettings
http://technet.microsoft.com/en-us/library/dd298063(v=exchg.150).aspx
Besides, please install the lasted rollup to check the result.
Cara Chen
TechNet Community Support

The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error. : Error: An Active Directory Constraint Violation error occurred

Hello,
We have a multi domain parent child AD domain infrastructure and now we upgraded our exchange from Exchange 2007 to Exchange 2013. Since last few days, we see the below error on the mailbox server event viewer.
EVENT ID : 1121
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '93a7d1ca-68a1-4cd9-9edb-a4ce2f7bb4cd'
Database GUID: '83d028ec-439d-4904-a0e4-1d3bc0f58809'
Error: An Active Directory Constraint Violation error occurred on <domain controller FQDN>. 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-0315286E, #1:
Our Exchange setup is in parent domain, but we keep on getting this error for various domain controllers in each child domain in the same site. We then configured one of the parent domain domain controller on Exchange. Still we are getting this error for
the configured parent domain DC.
Verified the AD replication and there is no latency or pending stuffs.
Any support to resolve this issue will be highly appreciated. Thank you in advance.
Regards,
Jnana R Dash

Hi,
In addition to Ed's suggestion, I would like to clarify the following things for troubleshooting:
1. Please restart IIS at first.
2. If the issue persists, please ping your DC on your Exchange server to check if Exchange can communicate with DC.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

DCDirectory - DSA Replication warning

Hi,
I'm getting this DSA Replication warning in my Event viewer. "DSA REPLICATION[18]Proc. 1021 Sev 14."
"DSA has been lost." Does anyone know what this means and if it's something I should be concerned about?

Yes, you should be concerned. This is telling you the pub's DCDirectory can not communicate with one or more of the subscribers to replicate it's data. This can eventually cause issues with Directory on the pub, best case.
Have you removed or reloaded any subscribers in the cluster recently? If yes then you need to get rid of the old replication agreements. If not you most likely have an issue with name resolution.
I can not stress this enough, MAKE SURE YOU BACKUP DCD & ENSURE YOU HAVE ALL NAME RESOLUTION ISSUES RESOLVED BEFORE YOU UTILIZE THIS PROCEDURE!
Look to this link to resolve your issue. This link needs the CCM releases updated but it IS valid for all 3.x & 4.x versions. If you do not feel comfortable executing then please pen a TAC case, as you have potential to loose all of your directory configuration.:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a008012b3c3.shtml
Mike

Exchange 2013 Mailbox Replication Service not installed

I have two Exchange 2013 Exchange CA servers running in a HA/Load Balance environment. Both are missing the Mailbox Replication Service. I didn't have any errors at any point during my installation. I look at the list of services on the
server and they're simply not there.
If I go to c:\program files\Microsoft\Exchange Server\v15\Bin the exe and config files are there. I tried just clicking the exe, but nothing changed. I need to be able to import mailboxes, so this is critical. I'm sure it is critical for
other reasons too.
Anything I can do here?

Hey,
It's a default behavior in Exchange 2013. Mailbox Replication service runs on MBX server role. You can review architecture of Exchange 2013 on below mentioned link.
http://blogs.technet.com/b/marwahasamir/archive/2012/08/28/what-s-new-in-exchange-2013.aspx
Pls mark this as answer if it resolves your issue. Thanks.
Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

PST Import to archive mailbox - Stays in queue until i restart the microsoft exchange mailbox replication service

Good Day all,
Stretched dag between site a and site b. Cas array at each site. Mailboxes primarily are located in site a unless there is a major outage then the dag flips to site b. setup two archive databases, one in site A on a non replicated partition
of the dag server and one in site B on a separate mailbox only server.
All exchange servers are patched to the latest sp and rollup.
site a has no issues at all, everything i import queues up and processes with no problems
at site b two imports will process and then stop until i restart the microsoft exchange mailbox replication service on the cas server. No errors no nothing just lots of move request sitting in the queue.
considering i have an insane amount of psts to import there does anyone have any suggestions besides setting up a task to restart the imicrosoft exchange mailbox replication service every 15 minutes?
thanks for your help in advance

Yeah I know from my research when I was setting up the dag you were not a fan of the stretched DAG but it works for us really well and passed all fail over tests that we ran on it <knocking on wood>.
Yes its running but it stops working after one session. I have had success in raising the transfer count from 2 to 5 but I can't really go much higher without taking down the server. the problem is when I am transferring someone with hundreds
of PSTs I have to babysit it...which sucks..
anyway, thanks for your help and have a great day :)

Exchnage Mailbox corrupted warning

Hi guys
I am in the middle of a migration from exchange 2007 (on SBS) to exchange 2013 (on windows server 2012)
1- I installed exchange 2013 and everything is working ok
2-started migrating test users from exchange 2007 to 2013 and its working just fine
issues:
am having an exchange warning on MEC (SBS) ==> "The value of property 'RecipientTypeDetails', 536870912, is not defined in the Enum type 'RecipientTypeDetails'."
even if I run the get-mailbox command from EMS (SBS) I get the same warning in yellow ==>
WARNING: Object ma.local/MyBusiness/Users/SBSUsers/DiscoverySearchMailbox
{D919BA05-46A6-415f-80AD-7E09334BB852} has been corrupted and it is in an
inconsistent state. The following validation errors have occurred:
WARNING: The value of property 'RecipientTypeDetails', 536870912, is not
defined in the Enum type 'RecipientTypeDetails'.
can someone please help
Thanks

Hi,
Thanks for your sharing. Besides that, I would like to make sure that there's no error on Exchange 2013, since we would migrate from Exchange 2007 to Exchange 2013 and this error on Exchange 2007 can be ignored.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Creating exact mailbox replication

We are using Exchange Server 2007 SP2. We have one user for whom we want exactly replicated mailbox. That is if there are 10 mails in Sent Items, 4 in Inbox and 2 in Deleted, then same should be the case with the replicating mailbox.
We tried doing this with transport level mail forwarding, however all mails gets forwarded to Inbox of the replicating mailbox. We want to move any mail sent by our user to Sent Items of the replicating mailbox. Is such configuration possible? If not in 2007
is it possible in other versions?

Hi,
From your description, I would like to verify if you want to achieve the following thing:
Let user A see all the items in user B's mailbox.
If yes, you can grant user A full access permission to user B's mailbox using the following cmdlet.
Add-MailboxPermission -Identity "user B" -User "user A" -AccessRights Fullaccess -InheritanceType all
If I have misunderstood your concern, please let me know.
Best regards,
Amy Wang
TechNet Community Support

MSExchangeIS Mailbox Store warning

Hi All,
Today connection to exchange was lost in outlook (I could ping exch server). So after enabling exchange debug mode I found out:
When a session is lost, these warnings are generated, please see pictures
below. Does anyone know if it's db about to brake ?

This should help
http://social.technet.microsoft.com/Forums/exchange/en-US/927854e1-8d28-44d4-9e29-adae51ca483a/event-id-1114-table-was-marked-as-in-use-while-releasing-a-database-session
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Mailbox move stuck

Hello,
I'm trying to move mailboxes from Exchange 2007 to 2013. The move request seems to be stuck in the "Syncing" mode.
Exchange 2007 environment consists of CAS and MBX servers, Exchange 2013 has both roles on the same machine.
Mail traffic between servers, to/from internet works without issues.
Where would I start to troubleshoot it?
Thanks.
Memento Mori

Have increased diagnostic logging for mailbox move:
Set-EventLogLevel -Identity "MSExchange Mailbox Replication\Mailbox Move" -level high
Set-EventLogLevel -Identity "MSExchange Mailbox Replication\Service
" -level high
Getting the following exception:
2014-01-05T03:07:29.678Z,15,MigrationServicelet,Information,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.5739226, job 1:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:ExchangeLocalMove:Staged:4:[email protected]:SyncStarting:1/5/2014
1:26:13 AM::"
2014-01-05T03:07:34.732Z,15,MigrationServicelet,Information,",,",ProcessCacheEntry: beginning processing /o=test/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=b31d04e95d224880be9d3330b66dddef-Migra
2014-01-05T03:07:35.372Z,15,MigrationServicelet,Information,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.5744619, job 1:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:ExchangeLocalMove:Staged:4:[email protected]:SyncStarting:1/5/2014
1:26:13 AM::"
2014-01-05T03:07:40.427Z,15,MigrationServicelet,Information,",,",ProcessCacheEntry: beginning processing /o=test/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=b31d04e95d224880be9d3330b66dddef-Migra
2014-01-05T03:07:41.066Z,15,MigrationServicelet,Information,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.589772, job 1:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:ExchangeLocalMove:Staged:4:[email protected]:SyncStarting:1/5/2014
1:26:13 AM::"
2014-01-05T03:07:46.136Z,15,MigrationServicelet,Information,",,",ProcessCacheEntry: beginning processing /o=test/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=b31d04e95d224880be9d3330b66dddef-Migra
2014-01-05T03:07:46.745Z,15,MigrationServicelet,Error,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,[email protected]","MigrationJobItem.SetTransientError: job a19d0cec-1b9b-472f-b849-5cd6f8a065d1:[email protected]:Syncing, at Microsoft.Exchange.Migration.MrsAccessorBase.HandleException[T](String
commandString, Exception ex) at Microsoft.Exchange.Migration.RunspaceAccessorBase.HandleException[T](String commandString, Exception ex, ICollection`1 ignoreExceptions) at Microsoft.Exchange.Migration.RunspaceAccessorBase.RunCommand[T](PSCommand
command, ICollection`1 ignoreExceptions) at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionSnapshot(ISubscriptionId subscriptionId) at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionStatus(ISubscriptionId
subscriptionId) at Microsoft.Exchange.Migration.SubscriptionHandlerBase.<>c__DisplayClass3.<GetJobItemsForActiveSubscriptionCheck>b__2() at Microsoft.Exchange.Migration.ItemStateTransitionHelper.RunBatchOperation(MigrationJob
job, IEnumerable`1 jobItems, IMigrationDataProvider dataProvider, Nullable`1 failedStatus, Action batchOperation)||Microsoft.Exchange.Data.Storage.Management.MigrationTransientException|Couldn't find a move request that corresponds to the specified identity
'domain.loc/Admins/test'.|InnerException:ManagementObjectNotFoundException:Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.|Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: Couldn't
find a move request that corresponds to the specified identity 'domain.loc/Admins/test'. at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData
optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError, ExchangeErrorCategory errorCategory) at Microsoft.Exchange.Configuration.Tasks.RecipientTaskHelper.ResolveDataObject[TDataObject](IConfigDataProvider dataSession, IConfigDataProvider
globalCatalogSession, ADServerSettings serverSettings, IIdentityParameter identity, ObjectId rootId, OptionalIdentityData optionalData, String domainController, CategorizedGetDataObjectDelegate getDataObjectHandler, TaskVerboseLoggingDelegate logHandler, ErrorLoggerDelegate
errorHandler) at Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()|"
2014-01-05T03:07:46.745Z,15,MigrationServicelet,Warning,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,[email protected]",Set TransientError: Syncing:1/5/2014 2:41:56 AM:Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.
--> Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.: count 10 original time 01/05/2014 02:41:56
2014-01-05T03:07:46.760Z,15,MigrationServicelet,Warning,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,[email protected]","NotifyOfTransientException: at Microsoft.Exchange.Migration.MrsAccessorBase.HandleException[T](String commandString, Exception ex)
at Microsoft.Exchange.Migration.RunspaceAccessorBase.HandleException[T](String commandString, Exception ex, ICollection`1 ignoreExceptions) at Microsoft.Exchange.Migration.RunspaceAccessorBase.RunCommand[T](PSCommand command, ICollection`1
ignoreExceptions) at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionSnapshot(ISubscriptionId subscriptionId) at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionStatus(ISubscriptionId
subscriptionId) at Microsoft.Exchange.Migration.SubscriptionHandlerBase.<>c__DisplayClass3.<GetJobItemsForActiveSubscriptionCheck>b__2() at Microsoft.Exchange.Migration.ItemStateTransitionHelper.RunBatchOperation(MigrationJob
job, IEnumerable`1 jobItems, IMigrationDataProvider dataProvider, Nullable`1 failedStatus, Action batchOperation)|transient error occurred for job items:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:[email protected]:Syncing||Microsoft.Exchange.Data.Storage.Management.MigrationTransientException|Couldn't
find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.|InnerException:ManagementObjectNotFoundException:Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.|Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException:
Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'. at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID,
OptionalIdentityData optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError, ExchangeErrorCategory errorCategory) at Microsoft.Exchange.Configuration.Tasks.RecipientTaskHelper.ResolveDataObject[TDataObject](IConfigDataProvider dataSession,
IConfigDataProvider globalCatalogSession, ADServerSettings serverSettings, IIdentityParameter identity, ObjectId rootId, OptionalIdentityData optionalData, String domainController, CategorizedGetDataObjectDelegate getDataObjectHandler, TaskVerboseLoggingDelegate
logHandler, ErrorLoggerDelegate errorHandler) at Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()|"
Memento Mori

Exchange 2013 CU2 - MapiExceptionRecoveryMDBMismatch

I have run a 'New-MailboxRestoreRequest' to restore a mailbox from a mounted recovery database. In the Application Event Log, from the 'MSExchange Mailbox Replication' source, I get the following:
The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
Database: RecoveryDB
Error: MapiExceptionRecoveryMDBMismatch: Unable to open message store. (hr=0x80004005, ec=1165)
Diagnostic context:
Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=132]
Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=248][latency=0]
Lid: 52176 ClientVersion: 15.0.712.17
Lid: 50032 ServerVersion: 15.0.712.6014
Lid: 23226 --- ROP Parse Start ---
Lid: 27962 ROP: ropLogon [254]
Lid: 17082 ROP Error: 0x48D
Lid: 26937
Lid: 21921 StoreEc: 0x48D
Lid: 27962 ROP: ropExtendedError [250]
Lid: 1494 ---- Remote Context Beg ----
Lid: 61208 StoreEc: 0x8004010F
Lid: 57721 StoreEc: 0x8004010F
Lid: 50608
Lid: 45768 StoreEc: 0x48D
Lid: 56872 dwParam: 0xFE
Lid: 42712 StoreEc: 0x48D
Lid: 10786 dwParam: 0x0 Msg: 15.00.0712.012:DOMAIN-EX13MB01
Lid: 1750 ---- Remote Context End ----
Lid: 26849
Lid: 21817 ROP Failure: 0x48D
Lid: 26297
Lid: 16585 StoreEc: 0x48D
Lid: 32441
Lid: 1706 StoreEc: 0x48D
Lid: 24761
Lid: 20665 StoreEc: 0x48D
Lid: 25785
Lid: 29881 StoreEc: 0x48D
Any ideas?

Hi,
The user AD account maybe deleted or disabled and recreated with a new mailbox. It now may have a new GUID. Restore would fail as the GUID is not available.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

MSExchange Mailbox Replication warning

Similar Messages

Maybe you are looking for