Messaging Records Management Errors and Events
Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
Applies to: Exchange Server 2007, Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3
Messaging records management (MRM) generates events that you can view in Event Viewer. This enables you to troubleshoot and verify the performance of the managed folder assistant. Event Viewer tracks the following kinds of events in the following order, based on importance:
Error events
Warning events
Informational events
For more information about Event Viewer, see Checking the Event Viewer.
MRM Errors and Events
The following tables provide lists of events that you can use to troubleshoot MRM. The logging types include the following:
Events labeled as LogAlways are always logged individually.
Events labeled as LogPeriodic are logged only once in any five-minute period, not every time they occur. This helps to prevent excessive log entries.
MRM events in the Managed Folder Assistant category
| Event ID | Category | Event type | Logging | Value or description |
|---|---|---|---|---|
10001 |
Managed Folder Assistant |
Error |
LogAlways |
The Managed Folder Assistant failed to provision mailbox <display name, mailbox GUID, legacy DN> because of corrupt data in the Active Directory. Exception details: <details>. To correct this, please run the Get-ManagedFolder command and fix the errors reported. |
10002 |
Managed Folder Assistant |
Error |
LogAlways |
There was an invalid update to managed folder <folder> in Active Directory. You may resolve this by deleting and recreating the managed folder object. |
10003 |
Managed Folder Assistant |
Error |
LogPeriodic |
Could not get the server configuration object from Active Directory. <Exception details>. Check for domain controller network connectivity issues or incorrect DNS configuration. |
10004 |
Managed Folder Assistant |
Error |
LogAlways |
The retention policy for folder <folder> in mailbox <mailbox> will not be applied. The managed folder assistant is unable to process managed content setting <content setting> for the managed folder <managed folder>. The RetentionAction is MoveToFolder but a destination folder was not specified. Please specify a destination folder. |
10005 |
Managed Folder Assistant |
Error |
LogAlways |
Retention policy will not be applied to folder <folder> in mailbox <mailbox>. Unable to process Managed Content Setting <content setting> for the Managed Folder <managed folder>. The RetentionAction is MoveToFolder but the destination folder <folder> is the same as the source folder <folder>. Please specify a destination folder that is different from the source folder. |
10006 |
Managed Folder Assistant |
Error |
LogAlways |
Unable to apply the managed content setting on folder <folder> because the folder was not found in mailbox <mailbox>. |
10007 |
Managed Folder Assistant |
Error |
LogAlways |
The managed folder assistant will not process mailboxes on database <database> because one or more managed folders in Active Directory have invalid data. Please verify all the managed folders contained in the managed folders container in Active Directory. Exception details: <details> |
10008 |
Managed Folder Assistant |
Error |
LogAlways |
The retention policy folder <folder> in mailbox <mailbox> will not be applied. The managed folder assistant is unable to process managed content setting <setting>. The RetentionAction is MoveToFolder but there was a failure creating the folder hierarchy under the destination folder. Root destination folder: <folder>. Attempted to create subfolder <folder> under <folder>. Error: <error> |
10009 |
Managed Folder Assistant |
Error |
LogAlways |
The managed folder assistant skipped processing all databases on the local server because it could not read the audit log parameters from Active Directory. It will try again later in the schedule window. Current database: <database> |
10010 |
Managed Folder Assistant |
Error |
LogAlways |
The managed folder assistant skipped processing all databases on the local server because the audit log is enabled but the path to the audit log is missing in Active Directory. It will try again later in the schedule window. Current database: <database> |
10011 |
Managed Folder Assistant |
Error |
LogAlways |
The managed folder assistant could not configure the audit log. It will stop processing the current database: '%1'. It will try again later in the schedule window. Exception details: <details> |
10012 |
Managed Folder Assistant |
Error |
LogAlways |
The managed folder assistant did not write to the audit log. It will stop processing the current database: <database>. It will try to write to the audit log again later in the schedule window. Exception details: <details> |
10013 |
Managed Folder Assistant |
Warning |
LogAlways |
The managed folder assistant was unable to provision the managed default folder <folder> in mailbox <mailbox> because it was not found in the mailbox. |
10014 |
Managed Folder Assistant |
Error |
LogAlways |
The managed folder assistant was unable to create the managed root folder <folder> in mailbox <mailbox> because the mailbox has several folders with the same name. |
10015 |
Managed Folder Assistant |
Error |
LogAlways |
The managed folder assistant detected a cycle among the policies in mailbox <mailbox> that will enforce retention by moving items to a destination folder and then back to the source folder. The policies involved are: <policies> |
10016 |
Managed Folder Assistant |
Error |
LogPeriodic |
Managed content setting <setting> will not be applied to mailbox <mailbox> because the AgeLimitForRetention is not greater than 0. |
10017 |
Managed Folder Assistant |
Error |
LogAlways |
An exception occurred in the managed folder assistant while it was processing Mailbox: <mailbox> Folder: Name: <folder name> Id: <folder ID> Item: Ids: <IDs>. Exception: <exception>. |
Messaging Records Management events in the Assistants category
| Event ID | Category | Event type | Logging | Value or description |
|---|---|---|---|---|
9004 |
Assistants |
Warning |
LogAlways |
Service <service>. <service> failed to process mailbox <mailbox>. The following exception caused the failure: <exception> |
9014 |
Assistants |
Warning |
LogAlways |
Service <service>. Unable to process schedule changes. The following exception caused the failure: <exception> |
9017 |
Assistants |
Information |
LogAlways |
Service <service>. <service> for database <database> is entering a scheduled time window. There are <number> mailboxes to process. |
9018 |
Assistants |
Information |
LogAlways |
Service <service>. <service> for database <database> is exiting a scheduled time window. <number> out of <number> mailboxes were successfully processed. <number> mailboxes were skipped due to errors. <number> mailboxes were processed separately. <number> mailboxes were not processed due to insufficient time. Note The managed folder assistant will resume where it left off the next time it runs. |
9019 |
Assistants |
Warning |
LogPeriodic |
Service <service>. Unable to save progress for <service> on database <database>. (The assistant was unable to save where it stopped so that it could resume there when it restarts.) The following exception caused the failure: <exception> |
9020 |
Assistants |
Warning |
LogAlways |
Service <service>. <assistant name> failed to start for database <database>. The following exception caused the failure: <exception> |
9021 |
Assistants |
Information |
LogAlways |
Service <service>. <service> for database <database> is processing an on-demand request. There are <number> mailboxes to process. |
9022 |
Assistants |
Information |
LogAlways |
Service <service>. <service> for database <database> has finished an on-demand request. <number> out of <number> mailboxes were successfully processed. <number> mailboxes were skipped due to errors. |
9023 |
Assistants |
Warning |
LogAlways |
Service <service>. <service> failed to start time window processing on database <database>. The following exception caused the failure: <exception> |
9025 |
Assistants |
Information |
LogAlways |
Service <service>. <service> skipped <number> mailboxes on database <database>. Mailboxes: <mailboxes> |
9026 |
Assistants |
Warning |
LogAlways |
Service <service>. <service> failed to start on-demand processing on database <database>. The following exception caused the failure: <exception> |
9027 |
Assistants |
Error |
LogAlways |
Service <service>. <service> caused the process to terminate <number> times while processing mailbox <mailbox> on database <database>. This mailbox will no longer be processed in the requested time window or on-demand request. The following exception caused the failure: <exception> |
9028 |
Assistants |
Warning |
LogAlways |
Service <service>. <service> caused the process to terminate <number> times while processing mailbox <mailbox> on database <database>. The following exception caused the failure: <exception> |
9033 |
Assistants |
Warning |
LogAlways |
Service <service>. <service> for database <database> received an on-demand request. However, there are no mailboxes to process. |
9034 |
Assistants |
Information |
LogAlways |
Service <service> halted time based operations for managed folder assistant on database <database>. |
9035 |
Assistants |
Warning |
LogAlways |
Service <service>. <assistant name> was unable to process <number> mailboxes because insufficient time. |
9037 |
Assistants |
Error |
LogAlways |
Service <service>. An exception was encountered while processing a RPC. Method: <method>, Exception: <exception> |
For More Information
To learn more about MRM, see Understanding Messaging Records Management.
For information about managing MRM, see Managing Messaging Records Management.