Export (0) Print
Expand All
Expand Minimize

Pipeline tracing is enabled

 

Topic Last Modified: 2007-11-16

The Microsoft Exchange Server 2007 Management Pack for Operations Manager monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.

To learn more about this alert, if you are using Microsoft Operations Manager 2005, do one or more of the following:

  • From the Operator Console, select this alert, and then click the Properties tab. Review the description of the alert that includes the variables specific to your environment.

  • From the Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description. Review the events that have been logged that meet the criteria of this Operations Manager alert.

To learn more about this alert, if you are using System Center Operations Manager 2007, do one or more of the following:

  • From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.

  • From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the events that have been logged that meet the criteria of this Operations Manager alert.

 

Product Name

Exchange

Product Version

8.0 (Exchange Server 2007)

Event ID

5500

Event Source

MSExchangeTransport

Alert Type

Warning

MOM Rule Path

Microsoft Exchange Server/Exchange 2007/Common Components/Hub Transport and Edge Transport/Transport

MOM Rule Name

Pipeline tracing is enabled. This may degrade system performance.

This Warning event indicates that transport pipelining is enabled on a server that has Microsoft Exchange Server 2007 installed. Pipeline tracing is a diagnostic feature in Exchange 2007 that enables you to capture diagnostic information about e-mail messages as they encounter transport and routing agents that are registered on Simple Mail Transfer Protocol (SMTP) events in the transport pipeline.

Pipeline tracing produces significant diagnostic logging and can affect the performance of the Exchange server. If left enabled for a long time, pipeline tracing can potentially use a significant amount of disk space. Therefore, pipeline tracing should only be enabled for short periods of time to diagnose or investigate immediate and specific transport agent or routing agent problems.

The diagnostic logging that is produced by pipeline tracing includes all the contents of the message as it passed through the transport agents and routing agents. Therefore, it's recommended that the pipeline tracing output directory be secured so that only authorized people can access the directory.

No user action is required for this warning if pipeline tracing has been enabled to troubleshoot or investigate an immediate and specific transport agent or routing agent problem. However, remember that pipeline tracing should be left enabled only long enough to gather enough information to help you investigate a current problem. Consider doing one of the following:

  • If you no longer need pipeline tracing enabled, disable it by running the following command on the Exchange server on which this warning was generated:

    Set-TransportServer <Identity> -PipelineTracingEnabled $False

    In this command, replace <Identity> with the name of the Hub Transport server on which you want to disable pipeline tracing. For example:

    Set-TransportServer Hub01 -PipelineTracingEnabled $False

  • If pipeline tracing has consumed a significant amount of disk space, you can safely move all the log files that are located in the pipeline tracing log directory to another location. You can determine the location of the pipeline tracing log directory by running the following command:

    Get-TransportServer <Identity> | Format-List PipelineTracingPath

    In this command, replace <Identity> with the name of the Hub Transport server on which you want to view the location of the pipeline tracing log directory location. For example:

    Get-TransportServer Hub01 | Format-List PipelineTracingPath

  • If pipeline tracing should be enabled, monitor available disk space closely to make sure pipeline tracing doesn't consume available disk space. Also, verify that only authorized people can access the pipeline tracing log directory.

For more information about pipeline tracing, see the following Microsoft Exchange Server 2007 Help topics:

To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.

To review Exchange 2007 event message articles that may not be represented by Exchange 2007 alerts, see the Events and Errors Message 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.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft