Topic Last Modified: 2010-11-12
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager includes a performance data collection engine that is used to query performance counter objects on computers running Exchange 2010. For this Operations Manager rule, data is collected by using the performance counter specified in the Details table.
To review the value of the performance counter that generated this alert, in Operations Manager, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Object Name |
MSExchangeIS* |
Counter Name |
RPC Request Timeout Detected |
Sample Interval |
60 |
Server Role |
Ex14. Mailbox |
Critical Error Threshold |
0.5 |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Mailbox/Information Store |
Rule Name |
The Exchange store has deadlocked. |
Explanation
One indication of an unhealthy Exchange store is that threads are either deadlocked or otherwise not making any progress. If there are more than five threads on a single mailbox, 10 threads on a single database, or 20 threads on a single server that has not made progress in one minute, a time-out is reported on the server. The performance counter that indicates detected timeouts is MSExchangeIS\ RPC Request Timeout Detected.
The Exchange store also writes the following events to the server:
- 10025 - reports a time-out on the Exchange server
- 10026 - reports a time-out on the database
- 10027 - reports a time-out on an individual mailbox
If the time-out is detected on a single mailbox, the mailbox is considered potentially poisonous, and it is handled in a similar manner as a crash. This done by increasing the CrashCount. This action makes the mailbox susceptible to being quarantined.
User Action
There is as yet no supplementary user action content specifically written to help resolve this Exchange 2010 Management Pack alert. Your attempt to get user action content for this alert helps us prioritize the Exchange Server 2010 Management Pack alerts for which we will be providing detailed User Actions. Here are some recommended next steps to learn more about this alert:
- Review the Application log and System log on your computers
running Exchange 2010 for related events. For example, events that
occur immediately before and after this alert provide more
information about the root cause of this error.
- Research your issue by using self-support options. From the
navigation pane of the Exchange Server Solutions Center page, click Self
Support Options to use the following and other self-help
options.
- Search the Microsoft Knowledge Base. For example, search the
Knowledge Base for key words in the Rule Name for this alert. If
the alert was triggered by an event, search for the Event Source
and event ID associated with this alert.
- Visit and access the content available from the Exchange 2010 Forum Web site. You can also post a
question at that Web site.
- Visit and access the content available from the Exchange Server Community Web site.
- Search the Microsoft Knowledge Base. For example, search the
Knowledge Base for key words in the Rule Name for this alert. If
the alert was triggered by an event, search for the Event Source
and event ID associated with this alert.
- Research your issue by using other resources. From the
navigation pane at the Exchange Server Solutions Center page, click Key
Resources or other options to learn about other resources.
- Resolve your issue by using assisted support options. From the
Exchange Server Solutions Center page, click
Assisted Support Options to contact a Microsoft support
professional. Your organization may have a specific procedure on
directly contacting Microsoft Technical Support. Consider reviewing
your organization's guidelines to get that information. If you do
contact support, please have the event ID information available,
and if possible, be prepared your application and/or system logs to
be sent to Microsoft.
For More Information
If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.