Tech Man
asked on
Event 1013, MSExchange Mailbox Replication
Event 1013, MSExchange Mailbox Replication
In my Exchange 2016 CU8 environment started noticing this Event every 20+ hours
The Microsoft Exchange Mailbox Replication service was unable to synchronize Active Directory data with the request.
DB:d8383c31-6233-44b4-8ebd -4f0361bdd d78
RequestType:Sync
RequestGuid:
Failure:
Cannot find Template Tenant.
Stack trace:
at Microsoft.Exchange.Data.Di rectory.AD SessionSet tingsFacto ry.FromCon sumerOrgan ization()
at Microsoft.Exchange.Data.Di rectory.AD LatencyTra cker.Measu reSettings CreationTi me(Func`1 settingsCreationFunc, String memberName)
at Microsoft.Exchange.Data.Di rectory.AD SessionSet tings.From ConsumerOr ganization WithDataba seScope(AD ObjectId databaseId)
at Microsoft.Exchange.Mailbox Replicatio nService.A DInconsist encyCheck. EnsureClou dCacheRequ estCorrect ness(Reque stJobProvi der rjProvider, Guid dbGuid)
at Microsoft.Exchange.Mailbox Replicatio nService.A DInconsist encyCheck. <>c__Displ ayClass39_ 0.<CleanAD OrphanAndI nconsisten cyForReque sts>b__0()
at Microsoft.Exchange.Mailbox Replicatio nService.C ommonUtils .ProcessKn ownExcepti onsWithout Tracing(Ac tion actionDelegate, FailureDelegate processFailure)
Any ideas ?
In my Exchange 2016 CU8 environment started noticing this Event every 20+ hours
The Microsoft Exchange Mailbox Replication service was unable to synchronize Active Directory data with the request.
DB:d8383c31-6233-44b4-8ebd
RequestType:Sync
RequestGuid:
Failure:
Cannot find Template Tenant.
Stack trace:
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Mailbox
at Microsoft.Exchange.Mailbox
at Microsoft.Exchange.Mailbox
Any ideas ?
Did you try to restart mrs service? Also, did your AD undergo chagrs recently such as domains removed? The issue probably requires troubleshooting efforts on the AD part.
Hi,
Normally this kind of events you are experiencing, it is after one database was removed from the exchange environment.
You have a DAG or databases do not belong to different nodes?
Regards
Valentina
Normally this kind of events you are experiencing, it is after one database was removed from the exchange environment.
You have a DAG or databases do not belong to different nodes?
Regards
Valentina
ASKER
This environment is a stand-alone server Exchange 2016, no DAG.
No changes in AD
I started seeing this after upgrading to CU8
Thanks
No changes in AD
I started seeing this after upgrading to CU8
Thanks
Hi,
Have you tried to restart Microsoft Exchange Mailbox Replication service as Michelangelo told you?
After restarting, you continue to have the same message?
Regards
Valentina
Have you tried to restart Microsoft Exchange Mailbox Replication service as Michelangelo told you?
After restarting, you continue to have the same message?
Regards
Valentina
ASKER
Sorry, yes, I tried restarting the service and entire server- no luck!
Do you have hybrid set up ??
ASKER
No, it is not a hybrid..
standalone exchange environment.
standalone exchange environment.
Hi,
Check if you have any move request.
Get-MoveRequest
Remove all the move request. Verify even if you have any batch
Regards
Valentina
Check if you have any move request.
Get-MoveRequest
Remove all the move request. Verify even if you have any batch
Regards
Valentina
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.