The Recipient Update Service is starting a rebuild of

Details
Product: Exchange
Event ID: 8329
Source: MSExchangeAL
Version: 6.5.7638.0
Component: Microsoft Exchange Recipient Update Service
Message: The Recipient Update Service is starting a rebuild of <distinguished name><distinguished name>
   
Explanation

This Information event indicates that the Recipient Update Service has started a rebuild operation for the domain. The description of this event indicates the distinguished name of the Recipient Update Service that started the rebuild operation.

The Recipient Update Service stamps Exchange-specific attributes on Active Directory objects. The Recipient Update Service also looks for objects that have been created or modified since the last time it was run, and then updates the objects appropriately. The Recipient Update Service is configured to run against a specific domain and is set to run at specific intervals. You can also force the Recipient Update Service to run at any time by using the Update Now and Rebuild commands in Exchange System Manager. You do this using the following procedures:

To update only new and modified objects

  1. In Exchange System Manager, in the console tree, double-click Recipients, and then double-click Recipient Update Services.
  2. In the details pane, right-click the Recipient Update Service responsible for updating the domain that you want to update, and then click Update Now.

To update all objects

  1. In Exchange System Manager, in the console tree, double-click Recipients, and then double-click Recipient Update Services.
  2. In the details pane, right-click the Recipient Update Service responsible for updating the domain that you want to update, and then click Rebuild.

For details about how the Recipient Update Service applies recipient policies, see Microsoft Knowledge Base article 328738, XADM: How the Recipient Update Service Applies Recipient Policies.

   
User Action

No user action is required.

Related:

Calendaring agent failed in message save notification with error on : .

Details
Product: Exchange
Event ID: 8199
Source: EXCDO
Version: 6.5.7638.0
Component: Microsoft Exchange Collaboration Data Objects
Message: Calendaring agent failed in message save notification with error <error code> on <user name>: <file name>.
   
Explanation

This Error event indicates that a user tried to save an appointment, but the operation failed. Other EXCDO source events such as 8213 and 8206 may accompany event 8199.

Viewing the description of EXCDO source events that accompany Event 8199 may provide information about the underlying cause of this error. For example, you may see event 8213 with a description that states “Calendaring agent failed with error code 0x80040215 while saving appointment”. Event 8123 may be logged if the MSExchangeFBPublish registry key, or one of its subkeys, is missing from the Microsoft Windows registry.

For more information about events that can be related to Event 8199, see Microsoft Knowledge Base article 310440, You receive an “unable to perform the operation” error message when you save Calendar items in Exchange 2000 and Exchange 2003.

Error event 8199 might also be caused by a corrupted calendar item.

   
User Action

To resolve this error, try one or more of the following:

  • Verify that the Free/Busy service (MSFBPublish) is functioning correctly.
  • Examine the Application log for an event message that may provide more information about the actual error.
  • Compare the settings on the server on which the Error event occurred with those on an Exchange server that is not experiencing this error.

  • Examine the server to determine whether the MSExchangeFBPublish key exists in the registry. For information about restoring the correct registry key setting, see Microsoft Knowledge Base article 310440, You receive an “unable to perform the operation” error message when you save Calendar items in Exchange 2000 and Exchange 2003.
  • If you determine that this error was caused by a corrupted calendar item, try to identify the corrupted item. After you identify the corrupted item, deleting the item should resolve this error.

If the problem persists and if you cannot locate an event message that provides you more information about troubleshooting this issue, contact Microsoft Product Support Services.

Related:

The service threw an unexpected exception which was caught at ()

Details
Product: Exchange
Event ID: 8331
Source: MSExchangeAL
Version: 6.5.7638.0
Component: Microsoft Exchange Recipient Update Service
Message: The service threw an unexpected exception which was caught at <drive letter>(<directory name>)
   
Explanation

This event is logged when the Recipient Update Service cannot stamp Exchange attributes on Active Directory objects. When this event is being logged, users may not appear in the Global Address List (GAL). Additionally, users may not be able to access their Exchange mailboxes. These GAL display problems and mailbox access problems may occur if an internal class incorrectly processes certain threads that run at the same time.

This event is typically logged on a server when both of the following conditions are true:

  • The computer is running Exchange Server 2003 without Exchange Server 2003 Service Pack 1 (SP1) applied.
  • The computer has more than one logical processor.

For additional information about Event 8331, see Microsoft Knowledge Base article 837444, Users do not appear in the Global Address List, users cannot connect to their Exchange mailboxes, event ID 8331 is logged, and e-mail names cannot be resolved in Exchange Server 2003.

   
User Action

This problem has been fixed in Exchange Server 2003 SP1. To resolve this problem, apply SP1. To download Exchange Server 2003 SP1, visit the Service Pack 1 for Exchange 2003 page of the Microsoft Exchange Server Web site.

Related:

An inconsistency was detected in : . The calendar is being repaired. If other errors occur with this calendar, please view the calendar using Microsoft Outlook Web Access. If a problem persists, please recreate the calendar or the containing mailbox.

Details
Product: Exchange
Event ID: 8230
Source: EXCDO
Version: 6.5.7638.0
Component: Microsoft Exchange Collaboration Data Objects
Message: An inconsistency was detected in <%2>: <file name>. The calendar is being repaired. If other errors occur with this calendar, please view the calendar using Microsoft Outlook Web Access. If a problem persists, please recreate the calendar or the containing mailbox.
   
Explanation

This Warning event is logged when a problem with a Calendar item is detected. This indicates that Exchange detected data corruption and is trying to rebuild the calendaring data for Web client viewing.

The most common cause of calendar item corruption is scanning the Exchange Installable File System (IFS) drive with file system-based antivirus software. By default, the Exchange IFS drive is drive M. Corruption can also occur when you try to back up drive M. The following articles in the Microsoft Knowledge Base may apply:

Other events in the Application log may give you more information about why this event was logged and where the corruption exists. The following events may help you discover the underlying cause of this error:

    EXCDO Event 8199: Calendaring agent failed in message save notification with error 0x80040219 on %2: %3.

    EXCDO Event 8206: Calendaring agent failed with error code 0x8004010f (MAPI_E_NOT_FOUND) while saving appointment.

    EXCDO Event 8206: Calendaring agent failed with error code 0x80040229 while saving appointment.

    EXCDO Event 8206: Calendaring agent failed with error code 0x80070057 while saving appointment.

    EXCDO Event 8207: Calendaring agent failed with error code 0x8004010f while deleting appointment.

    EXCDO Event 8208: Calendaring agent failed with error code 0xfffffae2 while expanding recurring appointments.

    EXCDO Event 8217: The processing of the recurring appointment with the subject %1 in mailbox: %2 failed with error code 0x8000ffff. This appointment will not be visible in the web client or other non-MAPI client.

    EXCDO Event 8219: The calendaring agent could not publish the free/busy information for %1 because it failed reading the registry with Error code 0x80070002. The save/delete calendar operation for %2 will not be completed. Please ensure that MSExchangeFBPublish agent is started.

    EXCDO Event 8241: An existing appointment with the subject %1 in mailbox %2 was modified. The start time, or both the duration and end time of the existing appointment were missing.

    EXCDO Event 8243: The calendaring agent cannot bind to the appointment with the subject %1 in mailbox %2 because the appointment is missing a start time. The calendaring agent will not publish free/busy information for this appointment. To correct this, please delete the appointment and recreate it.

    EXCDO Event 8255: The background calendaring agent failed to logon to the MDB, or create a session object on the MDB:%1. The error code is 0x000003ef. The rendering of large calendars with the web client or Microsoft Internet Explorer for the mailbox %2 with GUID:%3 will be slower.

    EXCDO Event 8263: The recurring appointment expansion in mailbox %1 has taken too long. Some recurring appointment instances may not be visible at this time. To ensure that the calendar view is correct, please refresh the calendar view in Microsoft Outlook Web Access.

   
User Action

To resolve this error, try one or more of the following:

  • After Exchange rebuilds the data, verify whether Exchange was able to correctly display the calendaring data on the Web client.
  • Examine the Application log for relevant EXCDO source event messages. These events may provide additional information about the underlying issue.
  • Make sure that a file system-based antivirus program running on the Exchange Server is not scanning the Exchange IFS drive (M drive). Additionally, make sure that any backup software used is not backing up the Exchange IFS drive. If the corruption cannot be isolated or corrected, restore the data from a backup. For more information, see the Microsoft Knowledge Base articles referenced earlier in this article.

Related:

The evaluation version of Microsoft Exchange Intelligent Message Filter has expired.

Details
Product: Exchange
Event ID: 7516
Source: MSExchangeActiveSyncNotify
Version: 6.5.7638.0
Component: Microsoft Exchange Transport
Message: The evaluation version of Microsoft Exchange Intelligent Message Filter has expired.
   
Explanation

The evaluation version of Microsoft Exchange Intelligent Message Filter has expired. The time period for evaluating Intelligent Message Filter has expired.

   
User Action

For more information about obtaining a retail version of Microsoft Exchange Intelligent Message Filter, see the Exchange Intelligent Message Filter Web site.

Related:

An error occurred while loading Microsoft Exchange Intelligent Message Filter. The error code is .

Details
Product: Exchange
Event ID: 7514
Source: MSExchangeTransport
Version: 6.5.7638.0
Component: Microsoft Exchange Transport
Message: An error occurred while loading Microsoft Exchange Intelligent Message Filter. The error code is <%1>.
   
Explanation

An error occurred when loading Microsoft Exchange Intelligent Message Filter. Intelligent Message Filter writes this event when an error occurs when you install or update Intelligent Message Filter.

   
User Action

Uninstall the new version of Intelligent Message Filter and try to reinstall.

Related:

Microsoft Exchange Intelligent Message Filter was refreshed.Microsoft Exchange Intelligent Message Filter is now enabled. A refresh occurs when the SMTP service is restarted or Microsoft Exchange Intelligent Message Filter is updated.

Details
Product: Exchange
Event ID: 7513
Source: MSExchangeActiveSyncNotify
Version: 6.5.7638.0
Component: Microsoft Exchange Transport
Message: Microsoft Exchange Intelligent Message Filter was refreshed.Microsoft Exchange Intelligent Message Filter is now enabled. A refresh occurs when the SMTP service is restarted or Microsoft Exchange Intelligent Message Filter is updated.
   
Explanation

Intelligent Message Filter writes this event when you install Intelligent Message Filter for the first time or when you update Intelligent Message Filter. This event log is also written when the SMTP service is restarted.

   
User Action

No user action is required.

Related:

This is an SMTP protocol warning log for virtual server ID , connection #.The remote host “”, responded to the SMTP command “” with “”.The full command sent was “”. This may cause the connection to fail.

Details
Product: Exchange
Event ID: 7002
Source: MSExchangeTransport
Version: 6.5.7638.0
Component: Microsoft Exchange Transport
Message: This is an SMTP protocol warning log for virtual server ID <number>, connection #<number>.The remote host “<%3>“, responded to the SMTP command “<name>” with “<error message>“.The full command sent was “<name>“. This may cause the connection to fail.
   
Explanation

This event is logged when the Exchange server sends an SMTP command to a remote server and receives a response that is not valid. The virtual server ID indicates which SMTP virtual server issued the command. The remote host indicates the fully qualified domain name of the remote server that responded to the command. The actual command issued, and the response received, are also mentioned in the event.

Possible causes for this event include faulty network card drivers and network cards that are configured incorrectly.

   
User Action

To resolve this error, try one or more of the following:

  • Make sure that the latest network card drivers and firmware are installed.
  • Run any network diagnostics software that was supplied with the network cards to verify that the network cards are functioning correctly.
  • If the network cards are configured to automatically detect the speed of the connected network, change the configuration to use a specific speed setting.

For additional information that may help you resolve this problem, see Microsoft Knowledge Base article 153119, XFOR: Telnet to Port 25 to Test SMTP Communication.

Related:

Categorizer is NDRing a recipient with address : with reason code ().

Details
Product: Exchange
Event ID: 6015
Source: MSExchangeActiveSyncNotify
Version: 6.5.7638.0
Component: Microsoft Exchange Transport
Message: Categorizer is NDRing a recipient with address <%1>:<%2> with reason code <%3> (<%4>).
   
Explanation

This error event occurs because all public folder replication that uses Simple Mail Transfer Protocol (SMTP) must originate from an authenticated source or from a server that has been granted Send As permissions.

A common symptom of this error is the generation of a specific non-delivery report (NDR) message. Specifically, you may receive the following NDR message when you try to replicate public folders from a domain that has a Microsoft Exchange Server 5.5 computer or a Microsoft Exchange 2000 Server computer to a domain that has a Microsoft Exchange Server 2003 computer:

    General access denied, sender access denied? The sender of the message does not have the privileges necessary to complete delivery.

MSExchangeTransport Event 9013 may also be logged in the Application log. If it is also logged, there is a specific user action required to resolve the error. To view both these events, set diagnostic logging on the Categorizer category of the MSExchangeTransport service to Maximum.

   
User Action
  • If you do not see MSExchangeTransport Event 9013 logged with Event 6015, use the information provided in other MSExchangeTransport events to try to resolve this error. If you cannot resolve this error, contact Microsoft Product Support Services.
  • If MSExchangeTransport event 9013 is also logged in the Application log, you can add the SkipPublicMDBRestriction registry key to resolve this error. After you add this registry key, the Exchange Server 2003 computer can process system messages and public folder messages from unauthenticated sources.

      Caution   This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the “Restore the Registry” Help topic in Regedit.exe or Regedt32.exe.

    To resolve this public folder replication issue:

    1. Open a Registry Editor, such as Regedit.exe or Regedt32.exe.
    2. Navigate to HKey_Local_Machine\System\CurrentControlSet\Services\MSExchangeTransport.
    3. Right-click MSExchangeTransport, point to New, and then click Key.
    4. Type Parameters for the name of the new key, and then click Enter.
    5. Right-click Parameters, point to New, and then click DWORD value.
    6. Type SkipPublicMDBRestriction, and then click Enter.
    7. Double-click SkipPublicMDBRestriction.
    8. In Value data, type 1, and then click OK.
    9. Close Registry Editor.

    Before you edit the registry, and for information about how to edit the registry, see Microsoft Knowledge Base article 256986, “Description of the Microsoft Windows Registry” (http://go.microsoft.com/fwlink/?linkid=3052&kbid=256986).

  • For additional information about troubleshooting public folder replication problems, see the following Microsoft Knowledge Base articles:

    Related:

    Message delivery to the host ” failed while delivering to the remote domain ” for the following reason:

    Details
    Product: Exchange
    Event ID: 4006
    Source: MSExchangeActiveSyncNotify
    Version: 6.5.7638.0
    Component: Microsoft Exchange Transport
    Message: Message delivery to the host ‘<host name>‘ failed while delivering to the remote domain ‘<%2>‘ for the following reason: <text>
       
    Explanation

    This Warning event is logged when Exchange cannot deliver a message to a remote host. The event description should specify the reason for the failure.

    Some common reasons for this Warning event include the following:

    • The connection was dropped by the remote host.
    • The remote SMTP service rejected AUTH negotiation.
    • The server trying to deliver the message cannot access the message delivery information in the message.
    • An SMTP protocol error occurred.
    • The server that is trying to deliver the message cannot connect to the remote server.
    • If a smart host has been specified in the properties of the SMTP virtual server, this event can be logged if the smart host is unreachable for any reason.

    Note   This event can also be logged when the Mail Host Filtering feature of Sybari Antigen Antivirus Software is enabled. See User Action for more information.

       
    User Action

    To resolve this error, try one or more of the following:

    Note   If you are using the Mail Host Filtering feature of Sybari Antigen Antivirus Software, disabling that feature may resolve this issue.

    Related: