MSExchangeTransport 12029

 

Thank you for clicking the link that brought you to this page. We do not currently have an article to resolve this specific issue. Your attempt to get to this event article helps us prioritize the event articles for which we will be providing detailed explanations and user actions.

Although there is as yet no supplementary content specifically written to help resolve this Exchange 2010 event, here are some recommended next steps to learn more about this alert:

  • Review the Application log and System log on your Exchange 2010 servers for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.

  • Research your issue by using self-support options. From the navigation pane of the Exchange Server Solutions Center page, click Self Support Options to use the following and other self-help options:

  • Research your issue by using other resources. From the navigation pane at the Exchange Server Solutions Center page, click Key Resources to learn about other resources.

  • Resolve your issue by using assisted support options. From the Exchange Server Solutions Center page, click Assisted Support Options to contact a Microsoft support professional. Because your organization may have a specific procedure for directly contacting Microsoft Technical Support, be sure to reviewing your organization's guidelines first. If you do contact support, have the event ID information available. Also, if possible, be prepared to send your application and system logs to the support professional.

Details

Product Name

Exchange

Product Version

14.0

Event ID

12029

Event Source

MSExchangeTransport

Category

TransportService

Symbolic Name

ServerLivingForConsiderableTime

Message Text

The transport server is healthy for time: %1.

Explanation

This event indicates that the TransportService component in the Microsoft Exchange Transport pipeline has responded to health checks. This event indicates the overall health of the transport pipeline.

Microsoft Exchange Server 2010 uses an ESE database to store messages for routing throughout an Exchange organization. On servers that run the Edge Transport role, the database queues those messages that are received from or directed to the Internet. On servers that run the Hub Transport role, the database queues those messages that are transferred throughout the Exchange organization. Exchange 2010 includes the following transport queues:

  • Submission queue

  • Mailbox delivery queue

  • Remote delivery queue

  • Poison message queue

  • Unreachable queue

The Microsoft Exchange Transport service uses several components to move messages throughout an organization. For more information about the transport architecture in Exchange 2010, see Transport Architecture.

Diagnostics logging in Exchange may be configured for the Microsoft Exchange Transport Service process as well as for following components in the transport pipeline:

  • Agents

  • Approval

  • Categorizer

  • Components

  • Configuration

  • DSN

  • Exch50

  • Logging

  • MessageSecurity

  • Ocar

  • Pickup

  • PoisonMessage

  • Process

  • RemoteDelivery

  • ResourceManager

  • Routing

  • ShadowRedundancy

  • SmtpReceive

  • SmtpSend

  • Storage

  • Transport Address Book

  • TransportDumpster

  • TransportService

User Action

No user action is required.

For More Information

If you are not already doing so, consider running the Exchange tools, which have been created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues and improve mail flow. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.