XADM: Exchange Admin Unable to Map SIDs to Account Names After 5.5 Upgrade

ID: Q216313

The information in this article applies to:

SYMPTOMS

The Microsoft Exchange Server Administrator program can be installed and run from computers running Windows NT Workstation. If the workstation computer is in a domain with a one-way trust, such that the domain where the Exchange Server computers reside trusts the domain where the computers running Windows NT workstation reside, but the reverse is not true, the Exchange Server Administration program may not be able to administer the Exchange Key Management Server (KMS) features from these computers running Windows NT Workstation.

When you attempt to view the KMS properties dialog box with the Exchange Server Administrator program, you will be prompted for the KMS password. After you type the password, a message box with the following error message may be displayed:

No mapping between account names and security IDs was done.
This only occurs if any of the Exchange KMS administrator accounts are in the Exchange Server domain.


CAUSE

In Exchange Server 5.0, the Exchange Server Administrator program requests the account names of the KMS administrators. In Exchange Server 5.5, the Exchange Server Administrator program was requesting the security IDs (SIDs) of the KMS administrators. This required that the Exchange Server Administrator program map the SIDs back into names. Because the domain that the computers running Windows NT Workstation are in does not trust the domain the Exchange Server computers are in, the Exchange Server Administrator program will not ask the Exchange Server domain to map the SIDs to strings.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.5 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

Component: KMS

File name Version
Admin.exe 5.5.2549.0



NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


WORKAROUND

To work around this problem, you could set up a two-way trust between the two domains. A second workaround would be to move the computers running Windows NT Workstation into the same domain as the Exchange Server computers.


STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5.


Keywords          : 
Version           : winnt:5.5
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: August 3, 1999