Connected routing group %1 was not found for connector %2 in routing tables with timestamp %3.

Details
Product: Exchange
Event ID: 5029
Source: MSExchangeTransport
Version: 8.0
Symbolic Name: RoutingNoConnectedRg
Message: Connected routing group %1 was not found for connector %2 in routing tables with timestamp %3.
   
Explanation

This Error event indicates that the Microsoft Exchange Server 2007 transport routing engine can’t find the specified routing group using the specified connector.

Routing group connectors are used in Exchange 2007 for Hub Transport servers to communicate with Exchange 2000 Server or Exchange Server 2003 bridgehead servers.

For more information, see Message Routing in a Coexistence Environment.

   
User Action
  • Verify that the specified routing group exists.

  • Verify that the specified routing group contains an Exchange 2000 or Exchange 2003 bridgehead server that is reachable on the network.

  • Make sure that you have correctly configured the source transport server on the connector that is specified in the event description. For information about how to configure connectors, see Managing Connectors.

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

Error %1 occurred while logging an event related to public folder age limits. Database “%2”.

Details
Product: Exchange
Event ID: 3063
Source: MSExchangeIS
Version: 8.0
Symbolic Name: msgidElscExpiryError
Message: Error %1 occurred while logging an event related to public folder age limits.
Database “%2”.
   
Explanation

This Error event indicates that the Exchange server is experiencing errors while logging events related to public folder age limits.

   
User Action

No user action is required. However, if this event is logged repeatedly, 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:

Error %1 occurred while logging an event related to replication state table updates for Public Folder Store “%2”.

Details
Product: Exchange
Event ID: 3012
Source: MSExchangeIS
Version: 8.0
Symbolic Name: msgidElscDsUpdatesError
Message: Error %1 occurred while logging an event related to replication state table updates for Public Folder Store “%2”.
   
Explanation

This Error event indicates that an event log message failed. Replication errors may occur when the database is out of synchronization, records are locked, or data is missing or unavailable. Most errors can be ignored, and retries will be attempted during the synchronization process. If a message fails to synchronize, the updates are made during the next synchronization.

   
User Action

No user action is required. However, if this event is logged repeatedly, 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:

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:

Error %1 occurred while creating site folder %2.

Details
Product: Exchange
Event ID: 3048
Source: MSExchangeIS
Version: 8.0
Symbolic Name: msgidSiteFolderCreateError
Message: Error %1 occurred while creating site folder %2.
   
Explanation

This Error event indicates that an error occurred when a site folder was created. Site folders can include free/busy and offline address book folders.

   
User Action

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

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:

Database error %3 occurred in function %1 while accessing the database “%2”.

Details
Product: Exchange
Event ID: 1159
Source: MSExchangeIS
Version: 8.0
Symbolic Name: msgidJetCritical
Message: Database error %3 occurred in function %1 while accessing the database “%2”.
   
Explanation

This Error event indicates that the threshold of uncommitted transaction log files in the Exchange database has been reached or about to be reached. This error may cause all databases under the storage group specified in the event description to dismount automatically. In Microsoft® Exchange Server 2007, transaction log file size has been reduced to 1 MB compared to 5 MB in Exchange 2000 Server or Exchange Server 2003. For more information about the changes in database functionality for Exchange Server 2007, see New Exchange Database Functionality on the Exchange Server TechCenter.

Another symptom you may experience is that MSExchangeIS Warning event 9788 is logged in the Application log. For more information about the event, visit the Events and Errors Message Center.

   
User Action

To resolve this error, see Microsoft Knowledge Base Article, 925817 The information store is dismounted, and an event ID 1159 message is logged in Exchange Server 2007 on Microsoft Help and Support center.

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 find the global domain information for the name Microsoft Exchange site. [valuevaluevaluevalue] (12)

Details
Product: Exchange
Event ID: 168
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: Unable to find the global domain information for the name Microsoft Exchange site. [valuevaluevaluevalue] (12)
   
Explanation
The message transfer agent (MTA) in Exchange 2000 now uses a DLL to access the routing engine recalculated routing.
   
User Action
Check network connectivity. Verify that the domain controller is running. If the error persists, stop and restart the MTA service. If the error persists, restart Microsoft Exchange Server.

Related: