Domain Naming FSMO role not found
Topic Last Modified: 2005-11-17
The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine the fSMORoleOwner attribute of the domain naming operations master in the Configuration Naming Context. For example, in a domain called contoso.com, fSMORoleOwner for the domain naming master is an attribute of CN=Partitions, CN=Configuration, DC=contoso, DC=com. The Exchange Server Analyzer then tries to open a Lightweight Directory Access Protocol (LDAP) connection with the domain controller. If the Exchange Server Analyzer finds that the domain controller specified in the fSMORoleOwner attribute does not respond, an error is displayed.
The domain naming master domain controller controls the addition or removal of domains in the forest. There can be only one domain naming master in the whole forest.
You must have a domain naming master defined for your Active Directory forest. Exchange Setup and Exchange Service Pack Setup will fail if a domain naming master domain controller is not online during set up. If the domain controller listed as the domain naming master is offline, it must be brought back online.
Verify that the designated Active Directory server is physically present.
If this directory server has been decommissioned, assign the role of domain naming master to another domain controller.
For more information about how to assign the role of domain naming master to another domain controller, see the following Microsoft Knowledge Base articles:
For Microsoft Windows Server™ 2003, see 324801, "How To View and Transfer FSMO Roles in Windows Server 2003" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=324801).
For Microsoft Windows® 2000 Server, see 255690, "HOW TO: View and Transfer FSMO Roles in the Graphical User Interface" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=255690).