Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, October 11, 2017 2:11 PM
Hello
New install of Exchange 2016. Coexisting with 2010 and migrating users over to 2016. Seeing these performance counter warnings in Event viewer.
Log Name: Application
Source: MSExchangeDiagnostics
Date: 10/11/2017 9:05:14 AM
Event ID: 1006
Task Category: Triggers
Level: Error
Keywords: Classic
User: N/A
Computer: <server>
Description:
The performance counter '\\<server>\MSExchange Assistants - Per Database(msexchangemailboxassistants-us-a-f)\Event Dispatchers Catching Up' sustained a value of '1,416.00', for the '30' minute(s) interval starting at '10/11/2017 12:35:00 PM'. Threshold breached since '10/2/2017 1:35 PM'. None Trigger Name:EventDispatchersCatchupQueueTrigger. Instance:msexchangemailboxassistants-us-a-f
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeDiagnostics" />
<EventID Qualifiers="49156">1006</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-10-11T13:05:14.000000000Z" />
<EventRecordID>281005</EventRecordID>
<Channel>Application</Channel>
<Computer><server></Computer>
<Security />
</System>
<EventData>
<Data>\\<server>\MSExchange Assistants - Per Database(msexchangemailboxassistants-us-a-f)\Event Dispatchers Catching Up</Data>
<Data>1,416.00</Data>
<Data>30</Data>
<Data>10/11/2017 12:35:00 PM</Data>
<Data>None</Data>
<Data>EventDispatchersCatchupQueueTrigger</Data>
<Data>msexchangemailboxassistants-us-a-f</Data>
<Data>10/2/2017 1:35 PM</Data>
<Data>100</Data>
</EventData>
</Event>
How I Can troubleshoot this?
Thanks
Phil
All replies (2)
Thursday, October 12, 2017 8:12 AM âś…Answered
Hi Phil,
This event was triggered by Performance Counter: "Event Dispatchers Catching Up", this counter shows the number of event dispatchers that are in catchup state. You can try to restart the MSExchangeMailboxAssistants Service to check if any helps, or create multiple databases on Exchange server 2016 and migrate the mailboxes to these databases dispersively to check if any helps.
If your Exchange server doesn't have any performance issues, it's recommended to safely ignore this error events or disable this monitor counter by the following steps:
1.Open this file in notepad: C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Diagnostics.Service.exe.config
2.Change "ExchangeJobs.Triggers.EventDispatchersCatchupQueueTrigger" from "True" to "False".
Hope this helps,
Best Regards,
Niko Cheng
TechNet Community Support
Please remember to mark the replies as answers.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, October 12, 2017 2:07 PM
Thank you. I will keep an eye on this after the migrations to see if it goes away.