Topic Last Modified: 2010-01-21

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

To learn more about this alert, in Operations Manager, 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 logged events that meet the criteria of this Operations Manager alert.

Details

Product Name	Exchange
Product Version	14.0 (Exchange 2010)
Event ID	16015
Event Source	MSExchangeTransport
Alert Type	Warning
Rule Path	Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport
Rule Name	The SendProtocolLogPath parameter is set to null; therefore, Exchange will continue to use the old location for protocol log storage.

Explanation

This Warning event indicates that the following conditions are both true:

The SendProtocolLogPath parameter on the Set-TransportServer cmdlet is currently set to $null.
The previous directory that was specified by the SendProtocolLogPath parameter on the Set-TransportServer cmdlet still exists.

By default, the Send connector protocol log files are located at C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpSend. All the Send connectors on a Hub Transport server or an Edge Transport server share the same protocol log files.

The preferred method of disabling protocol logging is to set the ProtocolLoggingLevel parameter to None on the Set-SendConnector cmdlet for each Send connector that is configured on the Hub Transport server or Edge Transport server.

If the following conditions are true, protocol logging for one or more Send connectors will still occur on the Hub Transport server or Edge Transport server, even if the value of the SendProtocolLogPath parameter is set to $null on the Set-TransportServer cmdlet:

The value of the ProtocolLoggingLevel parameter is set to Verbose on the Set-SendConnector cmdlet for one or more Send connectors.
The previous directory that was specified by the SendProtocolLogPath parameter on the Set-TransportServer cmdlet still exists.

User Action

To resolve this warning, set the value of the SendProtocolLogPath parameter on the Set-TransportServer cmdlet to a local file path. If you want to disable protocol logging on one or more Send connectors, set the value of the ProtocolLoggingLevel parameter to None on the Set-TransportServer cmdlet for the specific Send connectors. If you want to enable protocol logging on one or more Send connectors, set the value of the ProtocolLoggingLevel parameter to Verbose on the Set-TransportServer cmdlet for the specific Send connectors.

For more information, see Configure Protocol Logging.

For More Information

If you are not already doing so, consider running the Exchange tools 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, improve mail flow, and better manage disaster recovery scenarios. 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.