The Out of Office Assistant failed to parse the scheduled Out of Office information from one or more mailboxes. The corresponding scheduled Out of Office information is %1.

Details
Product: Exchange
Event ID: 3002
Source: MSExchangeMailboxAssistants
Version: 8.0
Symbolic Name: OOFInvalidScheduleLine
Message: The Out of Office Assistant failed to parse the scheduled Out of Office information from one or more mailboxes. The corresponding scheduled Out of Office information is %1.
   
Explanation

This Error event indicates that time-based Out of Office (OOF) Assistant could not parse the scheduled OOF information from one or more mailboxes. The OOF Assistant can be either an event-based assistant or a time-based assistant. The event-based assistant starts to process mailboxes on the occurrence of an event, such as on a change of OOF information in one or more mailboxes. The time-based assistant processes the mailboxes periodically after specific time intervals. This event may be caused if the time-based OOF Assistant does not parse the scheduled OOF information from one or more mailboxes because of internal errors.

   
User Action

To resolve this error, take the following steps:

  • Increase the diagnostic logging level of the OOF Assistance category on the MSExchangeMA service. After you increase the diagnostic logging level, you will see more events that are specific to this error in the Application log. These related events may help you find the root cause of this error. To increase the diagnostic logging level, follow the steps shown here:

    Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved. Before editing the registry, back up any valuable data.

    1. Start Registry Editor (regedit).

    2. Locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMA\Diagnostics

    3. In the results pane, change the Value data of OOF Assistant key to 5.

    4. Exit Registry Editor.

  • Restart Microsoft® Exchange Mailbox Assistants service from the Services console.

If you cannot resolve this error using the options suggested here, contact Microsoft Product Support Services. For more information, visit the Microsoft Help and Support Web site.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

There are too many contacts for external Out of Office messages for user: %1, so they are being truncated to %2. The Out of Office Assistant automatically sorts the Contacts list and truncates it to the maximum number of contacts allowed.

Details
Product: Exchange
Event ID: 3003
Source: MSExchangeMailboxAssistants
Version: 8.0
Symbolic Name: OOFTooManyContacts
Message: There are too many contacts for external Out of Office messages for user: %1, so they are being truncated to %2. The Out of Office Assistant automatically sorts the Contacts list and truncates it to the maximum number of contacts allowed.
   
Explanation

This Error event indicates that one or more users have more than the maximum allowed number of external contacts in their Contacts list. By default, the maximum allowed number of external contacts for configuring external Out Of Office (OOF) reply is 2,000.

   
User Action

To resolve this error, make sure that users who want to configure external OOF reply do not exceed the maximum allowed number of external contacts in their Contacts list. The Microsoft® Exchange OOF Assistant automatically sorts the Contacts list and truncates it to the maximum number of contacts allowed.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Microsoft Exchange ActiveSync has been loaded: Process ID: [%1].

Details
Product: Exchange
Event ID: 3002
Source: Server ActiveSync
Version: 6.5
Message: Microsoft Exchange ActiveSync has been loaded: Process ID: [%1].
   
Explanation

This Information event indicates that Microsoft Exchange ActiveSync has been loaded on an Exchange Server computer.

   
User Action
  • No user action is required. However, if one or more of your mobile device clients cannot synchronize their mobile devices with the Exchange Server computer, do one or more of the following:

  • Review the Application log for Server ActiveSync Warning or Error events. Use the information in those event descriptions to diagnose the root cause of the problem.

  • Review the following resources:

Related:

Unable to start the replication agent on Public Folder Store “%2”. Error %1

Details
Product: Exchange
Event ID: 3001
Source: MSExchangeIS
Version: 8.0
Symbolic Name: msgidReplStartError
Message: Unable to start the replication agent on Public Folder Store “%2”. Error %1
   
Explanation

This Error event indicates that Microsoft Exchange was unable to start the replication agent on the public folder store.

   
User Action

If the problem persists, try one or more of the following:

  • Review the Application log for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this event.

  • If this event seems to be causing mailflow interruptions or other problems in your Exchange environment, contact Microsoft Product Support. For information about contacting support, visit the Contact Us page of the Microsoft Help and Support Web site.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Microsoft Exchange has added the string “ncacn_HTTP:6004” to the following registry key entry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters\NSPI Interface Protocol Sequences. You must restart the server before you can use it for Outlook Anywhere.

Details
Product: Exchange
Event ID: 3002
Source: MSExchange RPC Over HTTP Autoconfig
Version: 8.0
Symbolic Name: UpdatedNSPIKey
Message: Microsoft Exchange has added the string “ncacn_HTTP:6004” to the following registry key entry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters\NSPI Interface Protocol Sequences. You must restart the server before you can use it for Outlook Anywhere.
   
Explanation

This Warning event indicates that Exchange has configured the server’s Active Directory for Outlook Anywhere operation. For the configuration to take effect, the server must be restarted.

   
User Action

To resolve the issue, restart the server.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Unable to initialize the Content Filter agent: %1

Details
Product: Exchange
Event ID: 301
Source: MSExchange Antispam
Version: 8.0
Symbolic Name: ContentFilterNotInitialized
Message: Unable to initialize the Content Filter agent: %1
   
Explanation

This Error event indicates that the Content Filter agent cannot start. This error may be triggered by multiple causes. Therefore, the method by which you resolve this error will depend on what triggered this event in your particular Exchange environment. For information about the Content Filter agent in Microsoft Exchange Server 2007, see Content Filtering.

   
User Action

To resolve this error, follow one or more of these steps:

  • Run the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. Use the Toolbox node of the Exchange Management Console to run these tools now.

  • Review the Application log 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.

  • If you experience mail flow interruptions or other problems in your Exchange environment after you try to resolve this issue, contact Microsoft Customer Support. For information about how to contact support, visit Microsoft Help and Support.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Fail when writing to log file

Details
Product: Exchange
Event ID: 9502
Source: MSExchangeIS
Version: 8.0
Symbolic Name: msgidJetLogWriteFail
Message: Fail when writing to log file
   
Explanation

This event indicates that the Microsoft® Exchange Information Store service did not write to a transaction log file. The Exchange Information Store service calls the Extensible Storage Engine (ESE). The ESE tried to write to a log file when this event was encountered. When the event occurs, the affected storage group goes offline and all the databases in the storage group will be dismounted. Users who have mailboxes on the dismounted databases will be unable to send or receive e-mail.

   
User Action

To resolve this issue, follow one or more of these steps:

  • Look for related ESE events in the Application log. The related ESE events will give you the specific reasons and detailed error information to help you resolve this problem.

  • Run the Database Recovery Management tool to obtain more information and help with solving the issue. The tool is part of the Exchange Troubleshooting Assistant and can be found in the Toolbox of the Exchange Management Console.

  • If the issue persists, contact Microsoft Customer Support. For information about how to contact support, visit Microsoft Help and Support.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Error code %1 when preparing for Snapshot.

Details
Product: Exchange
Event ID: 9609
Source: MSExchangeIS Public Store
Version: 6.5.6940.0
Component: Microsoft Exchange Information Store
Message: Error code %1 when preparing for Snapshot.
   
Explanation

This problem can occur if all the following conditions are true when the Volume Shadow Copy Service requestor in the third-party backup program uses Volume Shadow Copy Service to back up or to restore selected Exchange Server 2003 storage groups:

  • You use volume mount points for Exchange Server 2003 data storage.
  • The volume that you try to back up has multiple globally unique identifiers (GUIDs) in the mount-manager database.
  • The volume mount point refers to a GUID that is not the first GUID for the volume in the mount-manager database.
   
User Action

A supported hotfix is now available from Microsoft that resolves this error. For information about obtaining this hotfix, see Microsoft Knowledge Base article 838864 “A backup or a restore operation of Exchange 2003 storage groups fails with event IDs 9609 and 9611 when you use Windows Server 2003 Volume Shadow Copy Service” (http://go.microsoft.com/fwlink/?linkId=3052&kbid=838864).

Related:

Error code when preparing for Snapshot.

Details
Product: Exchange
Event ID: 9609
Source: MSExchangeIS
Version: 6.5.7638.0
Component: Microsoft Exchange Information Store
Message: Error code <%1> when preparing for Snapshot.
   
Explanation

This problem can occur if all the following conditions are true when the Volume Shadow Copy Service requestor in the third-party backup program uses Volume Shadow Copy Service to back up or to restore selected Exchange Server 2003 storage groups:

  • You use volume mount points for Exchange Server 2003 data storage.
  • The volume that you try to back up has multiple globally unique identifiers (GUIDs) in the mount-manager database.
  • The volume mount point refers to a GUID that is not the first GUID for the volume in the mount-manager database.
   
User Action

A supported hotfix is now available from Microsoft that resolves this error. For information about obtaining this hotfix, see Microsoft Knowledge Base article 838864 “A backup or a restore operation of Exchange 2003 storage groups fails with event IDs 9609 and 9611 when you use Windows Server 2003 Volume Shadow Copy Service” (http://go.microsoft.com/fwlink/?linkId=3052&kbid=838864).

Related:

The logon server could not be found.

Details
Product: Windows Operating System
Event ID: 2215
Source: System
Version: 5.0
Symbolic Name: NERR_LogonServerNotFound
Message: The logon server could not be found.
   
Explanation

This message should occur only on a workstation. Any action to correct the problem should be performed on that computer. No domain controller is responding to your command.

   
User Action

Contact your network administrator for assistance.

Related: