Topic Last Modified: 2010-07-06
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.
14.0 (Exchange 2010)
MSExchange Resource Booking
Microsoft Exchange Server/Exchange 2010/Mailbox/Assistants
MSExchangeAssistants Failed Requests - Resource Booking
This event indicates that many resource booking requests have failed. In this scenario, meeting room bookings or updates may not be processed for certain users. These users may experience the following symptoms:
- A meeting room update or cancellation is sent to a resource.
However, the user does not receive a response.
- The item in the booked resource is moved to the Deleted Items
folder in Microsoft Office Outlook. However, the item has not been
updated or removed from the booked resource.
The Assistant Infrastructure is part of the hosting application installation on servers that host the Mailbox server role. The Assistant Infrastructure is the component in Microsoft Exchange Server 2010 that separates message processing business logic from the information store. The separation of business logic from the store has the advantage of reducing the load on the store. This makes it easier to implement changes in business logic design and testing. Some of this business logic includes the following features:
- E-mail retention
- Resource scheduling
- Automated out-of-office messages
- Automated calendaring features
To handle business logic processing, the Assistant Infrastructure uses event-based assistants known as Mailbox Assistants. Event-based assistants process tasks that are based on events from the information store. In this scenario, the Assistant Infrastructure passes notifications to the appropriate assistant to perform a particular action or actions. The following assistants are event-based assistants:
- Resource Booking Assistant
- OOF Assistant
- Calendar Attendant
To handle resource booking requests, the Assistant Infrastructure uses the Resource Booking Assistant.
When the Assistant Infrastructure is started by a hosting application, one of the objects that is created in memory is the DatabaseManager. This object is responsible for running all assistants, managing threads, handling errors, and monitoring databases. When the DatabaseManager object starts, it creates the following objects:
- OnlineDatabase: This object manages per-database objects
and data that is common to all assistants.
- EventController: This object is the controller for
- EventPoller: This object polls the messaging database
and passes events to the EventDispatcher objects.
- PoisonControl: This object records crash information to
- EventDispatcher: There is one of these objects for every
mailbox in the mailbox database. The EventDispatcher threads
for each mailbox notify the appropriate event-based assistant to
process the particular action.
For event-based activities, the following generalized sequence of events occurs:
- The EventPoller polls the messaging database for events to
process. When an event occurs, the EventPoller creates an entry in
the Watermark Table in the information store. This table is used to
track the status of the event.
- The Assistant Infrastructure generates a thread for the
EventDispatcher for the appropriate mailbox.
- The EventDispatcher thread notifies the appropriate event-based
assistant to process the particular activity.
If the Resource Booking Assistant cannot process a request for any reason, this alert is generated.
To resolve this problem, do one or more of the following:
- Review the Application log and System log on your Exchange 2010
servers for related events. For example, events that occur
immediately before and after this event may provide more
information about the root cause of this error.
- To review detailed information about the cause of this problem,
use the Operations Console in Operations Manager. For more
information, see the "Introduction" section in this topic.
- Examine the event log entries for each Assistant Infrastructure
and for every corresponding Assistant to determine the exception
type. You may have to increase diagnostics logging to generate
additional events. Any event generated in the Application log will
include the exception type. You can use this type to determine
whether the failure represents is a permanent error or a transient
error. Additionally, you can use this information to determine
whether the failure is a database failure, a server failure, or a
- Collect performance information for all the Assistant
Infrastructure counters by using the MSExchange Assistants
object. Also, collect performance data for the particular Assistant
object. There is one instance for every hosting application per
database on the server. The instance name contains the service name
of the hosting application's service together with the database
name. Additionally, there is a total instance for each hosting
application. The "total" captures consolidated values for every
counter for all assistants that are hosted by the application.
- Verify that the databases are mounted. Assistant instances are
tied to databases. When a database is dismounted, the corresponding
assistant instances are removed.
- Use the Exchange Troubleshooting Assistant (ExTRA) to obtain
Event Tracing for Windows (ETW) traces. For more information, see
the following Scotch's Blog article, Another Method of Obtaining ExTRA Traces. To obtain
the Exchange Troubleshooting Assistant, see Microsoft Exchange Troubleshooting Assistant v1.1.
- Examine the watermark information in the configuration folder
of the mailbox database's system mailbox. The Assistant
Infrastructure saves event watermarks to indicate the most recent
events that were successfully processed.
- The Per Mailbox Watermark indicates the most recent event that
was successfully processed for each mailbox.
- The Per Database Watermark shows the lowest numbered event that
was successfully processed for any mailbox in the mailbox
- The Per Mailbox Watermark indicates the most recent event that was successfully processed for each mailbox.
- Resolve your issue by using self-support options, assisted
support options, and other resources. You can access these
resources from the Exchange Server Solutions Center. From this page,
click Self-Support Options in the navigation pane to use
self-help options. Self-help options include searching the
Microsoft Knowledge Base, posting a question at the Exchange Server
forums, and others. Alternatively, in the navigation pane, you can
click Assisted Support Options to contact a Microsoft
support professional. Because your organization may have a specific
procedure for directly contacting Microsoft Technical Support, be
sure to review your organization's guidelines first.
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.