%1 (%2) %3The database engine lost one table called %4. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.

Details
Product: Exchange
Event ID: 504
Source: ESE
Version: 8.0
Symbolic Name: REPAIR_BAD_TABLE
Message: %1 (%2) %3The database engine lost one table called %4. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.
   
Explanation

This Warning event occurs only when an error is encountered during offline repair.

   
User Action

To resolve this warning, perform an application-level integrity check of the database to ensure application-level data integrity.

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:

A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3). Cause: The message size was large or the local quota exceeded. For example, remote Exchange user might have delivery restrictions set with maximum incoming message size. Solution: Check access permissions as well as the message size.

Details
Product: Exchange
Event ID: 3014
Source: MSExchangeTransport
Version: 6.5.7596.0
Message: A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3). Cause: The message size was large or the local quota exceeded. For example, remote Exchange user might have delivery restrictions set with maximum incoming message size. Solution: Check access permissions as well as the message size.
   
Explanation

This Error event indicates that a non-delivery report (NDR) was generated due to the size of the message sent to a valid recipient on the remote Exchange Server. This event may be caused by a local quota such as a delivery restriction on the size of incoming messages for the remote user either at the remote user’s Exchange Server or Internet Service Provider.

   
User Action

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

  • Resend the message without attachments.

  • Set the remote server side limit or the remote client side limit to permit a larger message size.

For more information about the causes of Exchange Server non-delivery reports, see Microsoft Knowledge Base article 284204, Delivery status notifications in Exchange Server and in Small Business Server.

Related:

No route has been created for public folder hierarchy %1 in routing tables with timestamp %2. Recipients will not be routed to this public folder. Check the routing logs for further information.

Details
Product: Exchange
Event ID: 5010
Source: MSExchangeTransport
Version: 8.0
Symbolic Name: RoutingNoPfTreeRoute
Message: No route has been created for public folder hierarchy %1 in routing tables with timestamp %2. Recipients will not be routed to this public folder. Check the routing logs for further information.
   
Explanation

This Warning event indicates that the Microsoft Exchange Server 2007 transport routing engine could not calculate the route to the specified public folder hierarchy. For more information, see Managing Public Folders.

This warning may be caused by:

  • No route to the store that hosts the public folder hierarchy exists.

  • The server has not yet received configuration updates because of Active Directory replication latencies.

  • The public folder hierarchy is misconfigured.

The Folder Hierarchies container is missing under the administrative group in Exchange 2007. (The HomeMDB value is missing for public folders.)

   
User Action

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

  • Use the Get-PublicFolderDatabase cmdlet in the Exchange Management Shell to verify if one database that hosts the public folder hierarchy exists.

  • Verify the configuration of the public folder hierarchy.

  • Take no action. The messages will be routed to the Unreachable queue and delivery will be retried when routing configuration changes.

  • If you have the correct permissions, force Active Directory replication to occur immediately. An Active Directory notification causes the routing tables to be updated, and any affected messages in the Unreachable queue are resubmitted and routed to the destination server.

  • Add inheritable permissions to the appropriate mailbox store object, and make sure that the Exchange Servers group has the correct permissions. For more information, see Troubleshooting Mail Flow from Exchange 2007 to Exchange 2003 When E-Mail Messages are Stuck in the Queue.

  • Use ADSI Edit to create the Folder hierarchies container under the administative group in Exchange Server 2007. For more information, see Troubleshooting Mail Flow from Exchange 2007 to Exchange 2003 When E-Mail Messages are Stuck in the Queue.

  • Make sure that the msExchOwningPFTree attribute is associated with a public folder tree and that the location of the CN=Public folders container is under the Folder hierarchies container. For more information, see Troubleshooting Mail Flow from Exchange 2007 to Exchange 2003 When E-Mail Messages are Stuck in the Queue.

  • Review other related Error and Warning events in the Application log. These related events may help you find the root cause of this error.

  • If the recommended steps do not resolve this error, contact Microsoft Customer Support Services. For more information about how to contact support, 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:

The VoIP platform encountered an exception %1 during the call with ID “%2”. This exception occurred at the Microsoft Exchange Speech Engine VoIP platform during an event-based asynchronous operation submitted by the Unified Messaging server. The Unified Messaging server will attempt to recover from this exception. If this warning occurs frequently, contact Microsoft Product Support.

Details
Product: Exchange
Event ID: 1079
Source: MSExchange Unified Messaging
Version: 8.0
Symbolic Name: PlatformException
Message: The VoIP platform encountered an exception %1 during the call with ID “%2”. This exception occurred at the Microsoft Exchange Speech Engine VoIP platform during an event-based asynchronous operation submitted by the Unified Messaging server. The Unified Messaging server will attempt to recover from this exception. If this warning occurs frequently, contact Microsoft Product Support.
   
Explanation

This Warning event indicates that an exception occurred at the Microsoft® Exchange Speech Engine Voice over IP (VoIP) platform during an event-based asynchronous operation submitted by a computer that has the Unified Messaging server role installed. Event-based asynchronous operations allow the Unified Messaging (UM) server to continue to accept new calls and wait for responses for previous calls at the same time. The UM server handles these parallel VoIP operations by using separate threads. These parallel operations allow the UM server to perform many tasks at the same time, yet remain responsive.

   
User Action

If this warning frequently occurs, contact Microsoft Product Support. For information, see 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:

Exchange ActiveSync is ending its back-off from Exchange Mailbox server [%1]. Exchange ActiveSync will retry Exchange ActiveSync requests to the Exchange Mailbox server.

Details
Product: Exchange
Event ID: 1017
Source: MSExchange ActiveSync
Version: 8.0
Symbolic Name: MailboxBackOffPeriodEnded
Message: Exchange ActiveSync is ending its back-off from Exchange Mailbox server [%1]. Exchange ActiveSync will retry Exchange ActiveSync requests to the Exchange Mailbox server.
   
Explanation

This Information event indicates that Exchange ActiveSync has ended a back-off session from the computer that is running the Mailbox server role. It is now trying to send requests to the Mailbox server again.

   
User Action

No user action is required.

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:

Calendaring agent failed with error code thread id while expanding recurring appointments.

Details
Product: Exchange
Event ID: 8208
Source: EXCDO
Version: 6.5.0000.0
Message: Calendaring agent failed with error code thread id while expanding recurring appointments.
   
Explanation
The Event 8207 indicates that the Calendaring Agent on the Exchange Server

encountered an unexpected problem while processing a recurring appointment in the Calendar folder of the mailbox. This failure can occur for a variety of reasons and the error code in the Description section of the event will indicate the underlying cause of

the failure to delete. For example, error 0xfffffa1d maps to JET_errColumnNotFound. Please use the ERROR.EXE program from the Exchange 2000 CD to get details on the error.This error is seen if there is a corruption of the Calendar items in a mailbox or if the Calendar Folder on the mailbox is not accessible due to permissions issues or if there is a corruption in the database that the mailbox is homed on. Also, if the Exchange Installable File System (IFS) Drive (also called M Drive) is being scanned by a file level Virus Scanner (or has been scanned so in the past), then this error might be seen.

   
User Action

Ensure you have applied the latest Exchange 2000 Service pack. Service packs

might include fixes for the EXCDO component (or other related components) and

may fix the problem.

Re-register the following DLL files using the REGSVR32.EXE program:
oledb32.dll
, Oledb32r.dll, Msdaipp.dll, Msdaurl.dll and

Msado15.dll.

Check to see if any kind of File Level Antivirus Scanner is scanning the M

Drive. If so, configure the Antivirus software to exclude the M Drive (and also

the Exchange Database and log directories) from a file level scan. You may have

to reboot the server after making this change. Contact the Antivirus vendor for

details.

If the errors persist after the above changes, then you may have to run some

maintenance utilities on the Exchange 2000 databases. Please contact Microsoft

Product Support Services before performing this action.

Related:

The server has reached its currently configured outstanding requests limit of [] request(s). At this point, all new requests will be returned immediately with HTTP 503 (Service unavailable) error messages until the pending requests are processed. For more information about how to increase this limit, see Microsoft Knowledge Base article 901382 “Mobile Device Users Cannot Synchronize their Devices and Receive HTTP 503 (Service unavailable) Messages” (http://go.microsoft.com/fwlink/?linkid=3052kbid=901382).

Details
Product: Exchange
Event ID: 3032
Source: Server ActiveSync
Version: 6.5.7638.0
Component: Microsoft Exchange ActiveSync
Message: The server has reached its currently configured outstanding requests limit of [<number>] request(s). At this point, all new requests will be returned immediately with HTTP 503 (Service unavailable) error messages until the pending requests are processed. For more information about how to increase this limit, see Microsoft Knowledge Base article 901382 “Mobile Device Users Cannot Synchronize their Devices and Receive HTTP 503 (Service unavailable) Messages” (http://go.microsoft.com/fwlink/?linkid=3052kbid=901382).
   
Explanation

The server reached the currently configured limit for concurrent Exchange ActiveSync connections. All new requests will be returned immediately with HTTP 503 (Service unavailable) error messages until the pending requests are processed. The limit that is currently configured is specified in the text of the event. The default limit for concurrent Exchange ActiveSync connections is 10,000. You must take immediate administrator action to ensure ActiveSync availability.

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

  • Deploy an additional front-end server to minimize the load. This option is only applicable in front-end and back-end server deployments that use network load balancing solutions such as Windows Network Load Balancing.
  • Increase the concurrent request limit.
  • Important  This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore the registry if a problem occurs. For information about how to restore the registry, view the “Restore the Registry” Help topic in Regedit.exe or Regedt32.exe.

    To increase the concurrent request limit:

  1. On the computer running Exchange Server, start Regedit.exe.
  2. Open the following registry key:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MasSync\Parameters

    The registry value name for the concurrent request limit is MaxClients.

  3. Do one of the following:

    • If the registry parameter already exists, to increase the maximum heartbeat interval value, right-click MaxClients, and then click Modify. In Edit DWORD Value, in Value data, type a value larger than the current setting.
    • If the registry key parameter does not exist, to add the registry key parameter and specify a larger value than the default of 10000 connections, right-click Parameters, point to New, and then click DWORD Value. For the new value name, type MaxClients. Double-click MaxClients. In Value data, type a value larger than 10000. Click OK.
  4. Close Registry Editor.
  5. Restart Internet Information Services (IIS).

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 more information about how to resolve this error, see Microsoft Knowledge Base article 901382, “Mobile device users cannot synchronize their devices and receive HTTP 503 (Service unavailable) messages” (http://go.microsoft.com/fwlink/?linkid=3052&kbid=901382).

Related:

process name (process id) %3The database engine lost one bad data record. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.

Details
Product: Exchange
Event ID: 503
Source: ESE
Version: 6.5.0000.0
Message: process name (process id) %3The database engine lost one bad data record. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.
   
Explanation
At least one data record may be corrupt.

This event occurs only when problems are encountered during an offline repair.

   
User Action
Perform an application-level integrity check of the database to ensure application-level data integrity.

Related:

{process name} ({process id}) The database engine lost one bad data record. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.

Details
Product: Exchange
Event ID: 503
Source: ESE98
Version: 6.0
Component: Extensible Store Engine
Symbolic Name: REPAIR_BAD_RECORD_ID
Message: {process name} ({process id}) The database engine lost one bad data record. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.
   
User Action
Perform an application-level integrity check of the database to ensure application-level data integrity.

Related:

%1 (%2) %3The database engine lost one bad data record. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.

Details
Product: Exchange
Event ID: 503
Source: ESE
Version: 8.0
Symbolic Name: REPAIR_BAD_RECORD_ID
Message: %1 (%2) %3The database engine lost one bad data record. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.
   
Explanation

This Warning event indicates that at least one data record may be corrupted. This event occurs only when problems are encountered during an offline repair.

   
User Action

To resolve this warning, perform an application-level integrity check of the database to ensure application-level data integrity.

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: