Troubleshooting Auto Accept Agent
Topic Last Modified: 2006-06-29
This topic contains information to help you troubleshoot issues that may occur when you use Auto Accept Agent.
The following table describes the messages that are logged in the Application event log by Auto Accept Agent.
Auto Accept Agent messages
| Symbolic Name | Type | Description |
|---|---|---|
|
GeneralException |
Error |
An exception occurred when processing <url> in resource mailbox <mailbox name>. Auto Accept Agent did not process the request. |
|
ConfigurationException |
Error |
An exception occurred when reading configuration information whereas processing <url> in resource mailbox <mailbox name>. The default configuration settings were applied. (This error does not prevent requests from being processed.) |
|
ItemProcessingException |
Error |
An exception occurred when processing <url>. The exception information is: <exception information>. |
|
EventSinkConstructionException |
Error |
An exception occurred when constructing an event sink object for Auto Accept Agent. The exception information is: <exception information>. (This error is an initialization error.) The sink is not processing requests. |
|
DeleteItemException |
Error |
An exception occurred when deleting item <url>. The exception information is: <exception information>. |
|
Exchange OLE DB provider (EXOLEDB) |
Error |
An exception occurred when a resource mailbox is deleted but is still registered with Auto Accept Agent. For more information about resolving the error, see Unregistering Deleted Resource Mailboxes from Auto Accept Agent. |
The information shown in the following table can help you in monitoring the performance of Auto Accept Agent.
Auto Accept Agent performance counters
| Performance counter | Description |
|---|---|
|
Events |
The total number of events submitted to Auto Accept Agent for processing. |
|
Pending Events |
The number of events that have not yet been processed by Auto Accept Agent. |
|
Requests Submitted |
The total number of meeting requests submitted to Auto Accept Agent for processing. |
|
Requests Processed |
The total number of meeting requests processed by Auto Accept Agent. |
|
Requests Failed |
The total number of failures that occurred when Auto Accept Agent was processing events. |
|
Accepted |
The total number of meeting requests accepted by Auto Accept Agent. |
|
Declined |
The total number of meeting requests declined by Auto Accept Agent. |
|
Cancelled |
The total number of meeting cancellations processed by Auto Accept Agent. |
|
Average Time in Queue |
The running average of time between delivery of the item and the processing of the item, in milliseconds. |
|
Average Time to Process |
The running average of the agent's processing time per item, in milliseconds. |
Auto Accept Agent includes a response code in every response it sends. The response code explains why a request was accepted or declined. The following table provides the response codes and their corresponding definitions.
Auto Accept Agent response codes
| Response code | Definition |
|---|---|
|
0 |
Declined single meeting because of a scheduling conflict. |
|
1 |
Declined recurring meeting because of a scheduling conflict or conflicts. |
|
2 |
Declined single meeting because it is outside the booking window. |
|
3 |
Declined recurring meeting because all instances are outside the booking window. |
|
4 |
Accepted single meeting. |
|
5 |
Accepted recurring meeting without conflicts. |
|
6 |
Accepted recurring meeting with conflicts. |
|
7 |
Declined recurring meeting because it did not specify an end date. |
|
8 |
Declined recurring meeting because its end date is outside the booking window. |
|
9 |
Unexpected error occurred when processing request. |
For more information about Auto Accept Agent, see the following topics in the guide:
