SMTP / Routing Group connector state changes cause needless connector state toggling in Exchange 2000 Server

Article ID: 271996 - View products that this article applies to.
This article was previously published under Q271996
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/ )
Description of the Microsoft Windows registry
Expand all | Collapse all

SYMPTOMS

A Simple Mail Transport Protocol/Routing Group (SMTP/RG) connector may go into a "down" state temporarily, and then change within a minute to an "up" state after Advanced Queuing (AQ) retries the connector and determines that the SMTP/RG service on the target server is responding. This issue can occur if an SMTP/RG server on the other side does not close the connection properly. When a connector is in a down state, AQ flags the connector to indicate that it is in an error state. This type of connector state toggling can occur many times in an hour.

This issue impacts performance because it causes needless routing group version changes, which are associated with costly ResetRoutes AQ calculations. This issue also causes needless administrative notifications to be sent to the Exchange 2000 administrator if Exchange 2000 is configured to send notifications (to do so, click to expand Tools in Exchange System Manager, and then click to expand Monitoring and Status).

To have us fix this problem for you, go to the "Fix it for me" section. To fix this problem yourself, go to the "Let me fix it myself" section.
Back to the top | Give Feedback

Fix it for me

To fix this problem automatically, click the Fix it button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.

Fix this problem
Microsoft Fix it 50344



Note this wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note if you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.
Back to the top | Give Feedback

Let me fix it myself

To resolve this issue yorself, edit the registry to delay the forwarding of connector state changes and server changes (DMON info) by an amount of time that you specify in the registry. You can also edit the registry to eliminate redundant elements on that queue, so that the "connector down" element is deleted when the queue also contains "connector up" elements. If you configure these settings, Exchange 2000 only sends the most recent relevant connector state and server information notification when Exchange 2000 empties the queue.

The StateChangeDelay value affects the interval at which connectors are marked down and the notifications that occur as a result of connector and server state change. If you set this value, a server can only be marked up or down once in each time period that is set in the StateChangeDelay value.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To add the StateChangeDelay value:
  1. Start Registry Editor (Regedt32.exe).
  2. Locate and click the following key in the registry:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RESvc\Parameters
  3. On the Edit menu, click Add Value, and then add the following registry value:
    Value name: StateChangeDelay
    Data type: REG_DWORD
    Radix: Decimal
    Value data: Set this value to the number of seconds that you want between updates (if you do not set this value, the default is 300, which is 5 minutes)
  4. Quit Registry Editor.
  5. You need to restart the Simple Mail Transport Protocol service (Smtpsvc) and the Routing Engine service (Resvc) for this change to take effect.
Set the second parameter only in a situation where it is truly non-critical if the connector goes down. To add the SuppressStateChanges value:
  1. Start Registry Editor (Regedt32.exe).
  2. Locate and click the following key in the registry:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RESvc\Parameters
  3. On the Edit menu, click Add Value, and then add the following registry value:
    Value name: SuppressStateChanges
    Data type: REG_DWORD
    Radix: Decimal
    Value data: If you set this value to any value other than zero, you suppress all link state changes on this server (defaults to 0).
  4. Quit Registry Editor.
  5. You need to restart the Simple Mail Transport Protocol service (Smtpsvc) and the Routing Engine service (Resvc) for this change to take effect.
Back to the top | Give Feedback

MORE INFORMATION

In the scenario that is described in the "Symptoms" section of this article, the most recent notification is most likely to be connector up, because the connector down state is retained for only one minute before AQ reverses the connector down state. When a connector up packet arrives at the master, the routing group version number is not incremented because (as is also most likely the case) the connector is already known to be up. Therefore, these registry changes avoid needless and costly ResetRoute AQ calculations.

The default value of the delay time-out (when this registry entry is not enabled) is 300 seconds, or 5 minutes. Modify this registry entry only in the situation that is described in the "Symptoms" section of this article. This is accomplished by setting the registry delay value as necessary (for example, to 600 seconds [10 minutes]), and restarting the Simple Mail Transport Protocol service (Smtpsvc) and the Routing Engine service (Resvc). There are two possible values that you can add to neither of them are set or created by default

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
888231
(http://support.microsoft.com/kb/888231/ )
Exchange 2003 cannot control link state updates that are caused by user version changes
832281
(http://support.microsoft.com/kb/832281/ )
Link state issues and routing issues in Exchange 2000 Server and in Exchange Server 2003
Back to the top | Give Feedback

Properties

Article ID: 271996 - Last Review: September 10, 2011 - Revision: 3.0
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbmsifixme kbfixme kbfix kbprb KB271996
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top