Tag: Exchange 6.5.7596.0

An appointment with the subject “%1” was saved to mailbox %2. The start time is missing, so the calendaring agent cannot publish the free/busy information for this appointment. To correct this, please delete the appointment and recreate it.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 8239
Source: EXCDO
Version: 6.5.7596.0
Message: An appointment with the subject “%1” was saved to mailbox %2. The start time is missing, so the calendaring agent cannot publish the free/busy information for this appointment. To correct this, please delete the appointment and recreate it.
   
Explanation

This Error event indicates that the appointment that was saved was not saved with all the required information. An appointment can be saved without the required information if your file-level antivirus application is incorrectly configured to scan specific directories on the computer that is running Microsoft® Exchange Server. File-level scanners scan a file when the file is used or at a scheduled interval, and these scanners may lock or quarantine an Exchange Server file when Exchange Server 2003 tries to use the same file.

   
User Action

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

  • Make sure that you have correctly configured your file-level antivirus application to exclude specific Exchange Server directories. For a description of the folders that you should not include when scanning an Exchange server, see Knowledge Base article 823166, Overview of Exchange Server 2003 and antivirus software.

  • Make sure that you are running the most current version of your antivirus application software. For complete information about Exchange Server and antivirus software, see Knowledge Base article 823166, Overview of Exchange Server 2003 and antivirus software.

  • Contact the user and have them delete the appointment specified in the event description and then re-create it.

Related:

An inconsistency was detected in %2: %3. 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.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 8230
Source: EXCDO
Version: 6.5.7596.0
Message: An inconsistency was detected in %2: %3. 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 Microsoft® Exchange Server has detected data corruption and is trying to rebuild the calendar data for Web client viewing.

Calendar item corruption is usually caused when file system-based antivirus software scans the Exchange Installable File System (IFS) drive. 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

  • EXCDO Event 8206

  • EXCDO Event 8206

  • EXCDO Event 8206

  • EXCDO Event 8207

  • EXCDO Event 8208

  • EXCDO Event 8217

  • EXCDO Event 8219

  • EXCDO Event 8241

  • EXCDO Event 8243

  • EXCDO Event 8255

  • EXCDO Event 8263
   
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 calendar data on the Web client.

  • In Event Viewer, examine the Application log for relevant EXCDO source event messages. The descriptions of these related events may provide additional information about the underlying issue. For more information about the cause and resolution of these related events, click the “http://www.microsoft.com/contentredirect.asp” URL at the end of the description of each related event. Alternatively, you can search for more information about these related events at the Events and Errors Message Center Web site.

  • 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 that is 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:

Categorizer is using LDAP server Host: “%1”, Port: %2, Base priority: %3, Bind type: %4, Naming Context: “%5”, Account: “%6”

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 6020
Source: MSExchangeActiveSyncNotify
Version: 6.5.7596.0
Message: Categorizer is using LDAP server Host: “%1”, Port: %2, Base priority: %3, Bind type: %4, Naming Context: “%5”, Account: “%6”
   
Explanation

This Information event is logged when Microsoft® Exchange Server tries to contact the domain controller in another site. The domain controller that Exchange Server is trying to contact is specified in the event description. This event is only logged when you have increased Diagnostic logging for the MSExchangeTransport service.

   
User Action

No user action is required. This Information event can be ignored if you are not experiencing other message delivery problems in the Exchange Server environment. We recommend that you examine the Application log for related MSExchangeTransport events that occur before or after this event. If you examine related MSExchangeTransport Warning events and Error events, you may find the underlying cause of this event.

For more information about how to troubleshoot Exchange Server transport issues, see Microsoft Knowledge Base article 257265, General troubleshooting for transport issues in Exchange 2000 Server and in Exchange Server 2003.

Related:

Categorizer received error %1 from WLDAP32!%2 for server %3

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 6010
Source: MSExchangeTransport
Version: 6.5.7596.0
Message: Categorizer received error %1 from WLDAP32!%2 for server %3
   
Explanation

This Warning event is logged when Microsoft® Exchange Server identifies a delay during the message categorizer process. The message categorizer is a component of the advanced queuing engine that sends Lightweight Directory Access Protocol (LDAP) queries to the global catalog server to perform directory lookups.

The occurrence of MSExchangeTransport event 6010 does not indicate that e-mail messages have been lost or rejected.
   
User Action

No user action is required. This Warning event can be ignored if you are not experiencing other message delivery problems in the Exchange Server environment. We recommend that you examine the Application log for related MSExchangeTransport events that occur before or after this event. If you examine related MSExchangeTransport Warning events and Error events, you may find the underlying cause of this event.

For more information about how to troubleshoot Exchange Server transport issues, see Microsoft Knowledge Base article 257265, General troubleshooting for transport issues in Exchange 2000 Server and in Exchange Server 2003.

Related:

Exchange could not synchronize the information for mailbox ‘%1’ (mailbox store: ‘%2/%3’) with the information in the directory (error code: %4).

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 9583
Source: MSExchangeIS Mailbox Store
Version: 6.5.7596.0
Message: Exchange could not synchronize the information for mailbox ‘%1’ (mailbox store: ‘%2/%3’) with the information in the directory (error code: %4).
   
Explanation

This Error event indicates that Microsoft® Exchange Server was unable to deliver one or more e-mail messages to the mailbox specified in the event description. Other events that are logged near the time of this event may provide more information about the root cause of this error. There are two possible causes for this error:

  • There are two objects in Active Directory® with the same e-mail address.

  • There is a problem with the access control list (ACL) attribute for a user object.

   
User Action

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

  • If you have also logged MSExchangeIS event 9514, find the accounts that have duplicate proxy addresses, and modify one of the proxy addresses so that they are unique. For more information about event 9514, search the Events and Errors Message Center Web site.

  • If you have also logged MSExchangeIS event 9548, you may have to repair the account. For more information about event 9548, search the Events and Errors Message Center Web site.

  • If you have not logged MSExchangeIS event 9514 or 9548, search the event log for other events that come before or follow this event message to determine whether they explain the underlying reason for message delivery problems.

Related:

OALGen did not find any recipients in address list ‘%1’. This offline address list will not be generated. %2

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 9337
Source: MSExchangeSA
Version: 6.5.7596.0
Message: OALGen did not find any recipients in address list ‘%1’. This offline address list will not be generated. %2
   
Explanation

This Warning event may be logged during the Offline Address Book (OAB) file generation process. The OAB file is generated based on the recipients list from Active Directory®. If the recipients list is empty, this Warning event is logged.
   
User Action

To resolve this event, do one or more of the following:

  • Examine the permissions assignment on the Active Directory objects specific for the address list specified in the event description.

  • Verify the authentication between Microsoft® Exchange Server and the domain controllers in your organization.

  • Verify that Kerberos authentication, NTLM authentication, and Basic authentication are correctly functioning.

For information about troubleshooting offline address book issues, see the TechNet Support WebCast, How to troubleshoot Offline Address Book issues in Microsoft Exchange Server.

You can use the Offline Address Book Integrity (OABInteg) tool to troubleshoot offline address list problems. For information about how to use the OABInteg tool, see Microsoft Knowledge Base article 907792, Description of the Offline Address Book Integrity (OABInteg) tool.

For best practices for administering offline address lists, see the Offline Address Book Best Practices Guide.

Related:

Microsoft Exchange Server Mailbox Manager failed to send the following message:Subject: %1Recipient: %2Error: %3

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 9313
Source: MSExchangeSA
Version: 6.5.7596.0
Message: Microsoft Exchange Server Mailbox Manager failed to send the following message:Subject: %1Recipient: %2Error: %3
   
Explanation

This Error event occurs if Microsoft ® Exchange Server cannot send Exchange Mailbox Manager reports to the recipient listed in the description of this event. Possible causes of this error are the following:

  • The mailbox is disconnected.

  • There are message size restrictions on the mailbox or mailboxes.
   
User Action

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

  • Make sure that there is a mailbox connected to the recipient object specified in the event description.

  • Make sure that message size restrictions are not preventing Exchange from delivering Mailbox Manager reports to the recipient specified in the event description.

  • Restart the Exchange System Attendant service.

For more information about resolving this error, see Microsoft Knowledge Base article 322062, XADM: Mailbox Manager Does Not Send Reports and Does Not Log Any Error Messages.

Related:

The Microsoft Exchange Information Store encountered an unexpected exception %1 at address %2 while processing a request for user %3.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 9659
Source: MSExchangeIS Mailbox Store
Version: 6.5.7596.0
Message: The Microsoft Exchange Information Store encountered an unexpected exception %1 at address %2 while processing a request for user %3.
   
Explanation

This Error event is logged for a variety of reasons. The most common cause of MSExchangeIS event 9659 is a corrupted message in a Microsoft® Exchange Server mailbox. If this error is cause by a corrupted message, the event description specifies the name of the user who has a corrupted message in their mailbox.
   
User Action

To resolve this event, do one or more of the following:

  • Examine the Application log and System log for related Warning events or Error events that come before or after MSExchangeIS event 9659. The descriptions provided in these related events can provide more information about the root cause of this error.

    When troubleshooting MSExchangeIS Error events such as MSExchangeIS event 9659, we recommend that you increase diagnostic logging on the MSExchangeIS and MSExchangeTransport components. For information about how to increase logging levels when troubleshooting MSExchangeIS errors, see Microsoft Knowledge Base article 821912, How to Collect Diagnostic Data to Help Troubleshoot Information Store Issues.

  • Search the Microsoft Knowledge Base for more information about the exception code specified in the description of this event.

  • If you are running Microsoft Exchange Server 2003 Service Pack 1, see Microsoft Knowledge Base article 872963, Microsoft Exchange Information Store service crashes periodically after you install Exchange Server 2003 SP1.

Related:

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.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 8263
Source: EXCDO
Version: 6.5.7596.0
Message: 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.
   
Explanation

This Warning event indicates that an e-mail client that accesses calendar data using Microsoft® Office Outlook® Web Access was unable to successfully display all calendar items for a specific calendar view. This error may occur if a user has many calendar items that meet the criteria of the specific calendar view.

   
User Action

No administrator action is required. The user specified in the event message can use the refresh command in their Internet browser to view the remaining calendar items that meet the criteria of a calendar view. After the user has refreshed the Web page that showed the incomplete list of calendar items, Outlook Web Access will try to display the remaining items that meet the criteria of a calendar view.

Related:

OALGen will skip user entry ‘%1’ in address list ‘%2’ because the SMTP address ‘%3’ is invalid. %4

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 9325
Source: MSExchangeSA
Version: 6.5.7596.0
Message: OALGen will skip user entry ‘%1’ in address list ‘%2’ because the SMTP address ‘%3’ is invalid. %4
   
Explanation

This Error event indicates that the user account specified in the event description has not been included in an offline address list because of an incorrectly configured SMTP address. For example, an incorrectly configured SMTP address is an address that contains a dash “-“, an underscore “_”, or no characters after the @ symbol. Incorrectly configured SMTP addresses can occur in the following circumstances:

  • A script modified either a user’s primary SMTP proxy address attribute or e-mail address attribute. These attributes must match for a user to be added to an offline address list.

  • An administrator modified the e-mail address of a user on a computer that did not have the Exadmin.dll extensions loaded.

   
User Action

To resolve this error, make sure that the user account specified in the message has a correctly configured SMTP e-mail address. For information about SMTP address mismatches and how to resolve MSExchangeSA event 9325, see “Simple Mail Transfer Protocol Address Mismatches” in Improvements for Offline Address Books.

For more information about this event, see the Microsoft Knowledge Base article 555405, Event ID 9325 is logged by MSExchangeSA while generating Offline Address List.

You can use the proxytest test of the Offline Address Book Integrity tool (OABInteg) to identify the e-mail address that does not match the primary SMTP address for a user. For information about how to use OABInteg, see Microsoft Knowledge Base article 907792, Description of the Offline Address Book Integrity (OABInteg) tool.

For information about troubleshooting offline address book issues, see the Technet Support WebCast, How to troubleshoot Offline Address Book issues in Microsoft Exchange Server.

You can use the Offline Address Book Integrity (OABInteg) tool to troubleshoot offline address list problems. For information about how to use the OABInteg tool, see Microsoft Knowledge Base article 907792, Description of the Offline Address Book Integrity (OABInteg) tool.

For best practices for administering offline address lists, see the Offline Address Book Best Practices Guide.

Related: