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:
|
Tag: Exchange 6.5.7596.0
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.
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:
|
|
User Action | |
To resolve this error, try one or more of the following:
|
Related:
Categorizer is using LDAP server Host: “%1”, Port: %2, Base priority: %3, Bind type: %4, Naming Context: “%5”, Account: “%6”
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
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:
OALGen did not find any recipients in address list ‘%1’. This offline address list will not be generated. %2
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:
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
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:
|
|
User Action | |
To resolve this error, do one or more of the following:
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 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.
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
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:
|
|
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. |