Microsoft KB Archive/282446

= DSProxy configuration for static ports on Exchange cluster =

Article ID: 282446

Article Last Modified on 2/27/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition, when used with:
 * Microsoft Windows 2000 Standard Edition

-



This article was previously published under Q282446



Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
After statically mapping ports for the system attendant, directory NSPI proxy, and information store interfaces on a Microsoft Exchange 2000 Server cluster server behind a firewall, you also need to configure registry entries and install a hotfix for Dsproxy. If you do not do this, you receive the following error message when failing over on the Exchange nodes:

Event Type: Error

Event Source: MSExchangeCluster

Event Category: (4)

Event ID: 2076

Date: 11/20/2000

Time: 12:47:22 PM

User: N/A

Computer: BE1

Description: Mmapi SA: Cluster Service failed resource control function



CAUSE
The DSProxy component in Exchange 2000 that provides directory access to the domain controller or global catalog for non-Microsoft Outlook 2000 clients is not cluster-aware. It makes no check point to the registry in case of failover.



RESOLUTION
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

If ports are statically mapped on a cluster server, you must manually adjust the following registry keys on both nodes, and install the hotfix referenced in this article.

Note that when the following keys do not exist, DSProxy uses the compiled-time defaults or pass-in parameters.

Warning If you are performing directory replication by using the Site Replication Service (SRS) between Exchange 2000 or Microsoft Exchange Server 2003 computers and Microsoft Exchange Server 5.5 computers, you should not configure static ports on an Exchange cluster. This is because static port mapping requires disabling the Request for Response (RFR) service. Disabling the Request for Response (RFR) service adversely affects SRS directory replication. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

867502 Event ID 1091 is logged, and intersite directory replication does not occur between an Exchange Server 5.5 computer and the Site Replication Service on an Exchange 2000 or Exchange 2003 computer

Adjust the following registry key as indicated in the following table:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters

++ ++ ++ ++ ++ ++ ++ ++ ++ ++ Adjust the following registry key as indicated in the following table:
 * Key                       | Data type              | Value                                                                                                |
 * NSPI Target Server        | REG_SZ or REG_MULTI_SZ | DC server name used for MAPI client proxy service.                                                   |
 * RFR Target Server         | REG_SZ or REG_MULTI_SZ | DC server name used for MAPI client referral service.                                                |
 * No RFR Service            | REG_DWORD              | Set to 1 to turn off referral service.                                                               |
 * TCP/IP NSPI Port          | REG_DWORD              | TCP port number if other than system default.                                                        |
 * IPX/SPX NSPI Port         | REG_DWORD              | IPX port number if other than system default.                                                        |
 * AppleTalk NSPI Port       | REG_DWORD              | AT port number if other than system default.                                                         |
 * NSPI Max Worker Threads   | REG_DWORD              | Maximum worker threads use to contact the NSPI interface. Default is 10.                             |
 * NSPI Polling Times (msecs) | REG_DWORD             | Time the listener threads sleep when idle. Default value is 1 msec provided by the system attendant. |

HKEY_LOCAL_MACHINE\System\CurrentControlSet\MSExchangeSA\Diagnostics

++ ++ ++ ++
 * Key          | Data type | Value                                  |
 * NSPI Proxy   | REG_DWORD | Logging Level: 0,1,3,5 (default is 0). |
 * RFR Interface | REG_DWORD | Logging level: 0,1,3,5 (default is 0). |

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange 2000 Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix should have the following file attributes or later:

Component: Dsproxy



STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.



MORE INFORMATION
For additional information about mapping ports for the system attendant, directory NSPI proxy, and information interfaces on an Exchange 2000 server, click the following article number to view the article in the Microsoft Knowledge Base:

270836 Exchange 2000 and Exchange 2003 static port mappings

Additional query words: exch2kp2w XCCC

Keywords: kbbug kberrmsg kbexchange2000presp1fix kbfix kbqfe KB282446

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.