web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Error while installing...
Microsoft Dynamics CRM (Archived)

Error while installing MSCRM 4.0: Unable to obtain DNS hostname of Active Directory domain controller with ntdsa object name

(0) ShareShare
ReportReport
Posted on by Community Member

Good afternoon all,

Twice in the past two weeks I have run into a showstopping error when installing 4.0. One was a fresh install, the other was an upgrade from 3.0. Basically the setup program goes through the validation steps OK, and but when it starts the install and gets to the step where it's creating the database I get the following error:

 Got error: System.Exception: Action Microsoft.Crm.Setup.Server.InstallConfigDatabaseAction failed. ---> System.DirectoryServices.ActiveDirectory.ActiveDirectoryOperationException: Unable to obtain DNS hostname of Active Directory domain controller with ntdsa object name "CN=XXXXX Settings,CN=XXXXXXX,CN=Servers,CN=XXXXX,CN=Sites,CN=Configuration,DC=XXXX,DC=XXX".
   at System.DirectoryServices.ActiveDirectory.Utils.GetReplicaList(DirectoryContext context, String partitionName, String siteName, Boolean isDefaultNC, Boolean isADAM, Boolean isGC)
   at System.DirectoryServices.ActiveDirectory.DomainController.FindAllInternal(DirectoryContext context, String domainName, Boolean isDnsDomainName, String siteName)
   at System.DirectoryServices.ActiveDirectory.Domain.get_DomainControllers()

The installation gives a retry option but it tries to recreate the MSCRM_CONFIG database and then halts the installation with a failure.

 In the first install scenario, an admin inadvertantly deleted the domain controller named in the error instead of demoting it. In the second case, the DC was actually only powered on when needed to conduct testing. In both cases, the DC's involved were in no way connected to CRM.

What is the installer doing when looking for these domain controllers? What happens in the future when a DC is taken offline? Will this cause problems with the application or future upgrades? Is there any way around this error?

 Thanks,

Rob

*This post is locked for comments

I have the same question (0)
  • Binu Kumar S Profile Picture
    Binu Kumar S 1,720 on at

    For an Active Directory authenticated CRM environment, its unfair playing with Domain Controllers. Its a systemmatic step we use when we install CRM server. So don'teven think about renamin/deleting Domain controlers from CRM server.

    It will arise unexpected issues.

    In your case, make sure you have the domain controller working perfectly !

  • Community Member Profile Picture
    Community Member on at
    When you try to remove a domain controller from your Active Directory domain by using Dcpromo.exe and fail, or when you began to promote a member server to be a Domain Controller and failed (the reasons for your failure are not important for the scope of this article), you will be left with remains of the DCs object in the Active Directory. As part of a successful demotion process, the Dcpromo wizard removes the configuration data for the domain controller from Active Directory, but as noted above, a failed Dcpromo attempt might leave these objects in place.The effects of leaving such remains inside the Active Directory may vary, but one thing is sure: Whenever you'll try to re-install the server with the same computername and try to promote it to become a Domain Controller, you will fail because the Dcpromo process will still find the old object and therefore will refuse to re-create the objects for the new-old server.In the event that the NTDS Settings object is not removed correctly you can use the Ntdsutil.exe utility to manually remove the NTDS Settings object.If you give the new domain controller the same name as the failed computer, then you need perform only the first procedure to clean up metadata, which removes the NTDS Settings object of the failed domain controller. If you will give the new domain controller a different name, then you need to perform all three procedures: clean up metadata, remove the failed server object from the site, and remove the computer object from the domain controllers container.You will need the following tool: Ntdsutil.exe, Active Directory Sites and Services, Active Directory Users and Computers.Also, make sure that you use an account that is a member of the Enterprise Admins universal group.Caution: Using the Ntdsutil utility incorrectly may result in partial or complete loss of Active Directory functionality.To clean up metadata
    1. At the command line, type Ntdsutil and press ENTER.
    C:\WINDOWS>ntdsutilntdsutil:
    1. At the Ntdsutil: prompt, type metadata cleanup and press Enter.
    ntdsutil: metadata cleanupmetadata cleanup:
    1. At the metadata cleanup: prompt, type connections and press Enter.
    metadata cleanup: connectionsserver connections:
    1. At the server connections: prompt, type connect to server <servername>, where <servername> is the domain controller (any functional domain controller in the same domain) from which you plan to clean up the metadata of the failed domain controller. Press Enter.
    server connections: connect to server server100Binding to server100 ...Connected to server100 using credentials of locally logged on user.server connections:Note: Windows Server 2003 Service Pack 1 eliminates the need for the above step.
    1. Type quit and press Enter to return you to the metadata cleanup: prompt.
    server connections: qmetadata cleanup:
    1. Type select operation target and press Enter.
    metadata cleanup: Select operation targetselect operation target:
    1. Type list domains and press Enter. This lists all domains in the forest with a number associated with each.
    select operation target: list domainsFound 1 domain(s)0 - DC=bulli,DC=netselect operation target:
    1. Type select domain <number>, where <number> is the number corresponding to the domain in which the failed server was located. Press Enter.
    select operation target: Select domain 0No current siteDomain - DC=bulli,DC=netNo current serverNo current Naming Contextselect operation target:
    1. Type list sites and press Enter.
    select operation target: List sitesFound 1 site(s)0 - CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bulli,DC=netselect operation target:
    1. Type select site <number>, where <number> refers to the number of the site in which the domain controller was a member. Press Enter.
    select operation target: Select site 0Site - CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bulli,DC=netDomain - DC=bulli,DC=netNo current serverNo current Naming Contextselect operation target:
    1. Type list servers in site and press Enter. This will list all servers in that site with a corresponding number.
    select operation target: List servers in siteFound 2 server(s)0 - CN=SERVER200,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bulli,DC=net1 - CN=SERVER100,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bulli,DC=netselect operation target:
    1. Type select server <number> and press Enter, where <number> refers to the domain controller to be removed.
    select operation target: Select server 0Site - CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bulli,DC=netDomain - DC=bulli,DC=netServer - CN=SERVER200,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bulli,DC=net DSA object - CN=NTDS Settings,CN=SERVER200,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bulli,DC=net DNS host name - server200.bulli.net Computer object - CN=SERVER200,OU=Domain Controllers,DC=bulli,DC=netNo current Naming Contextselect operation target:
    1. Type quit and press Enter. The Metadata cleanup menu is displayed.
    select operation target: qmetadata cleanup:
    1. Type remove selected server and press Enter.
    You will receive a warning message. Read it, and if you agree, press Yes.metadata cleanup: Remove selected server"CN=SERVER200,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bulli,DC=net" removed from server "server100"metadata cleanup:At this point, Active Directory confirms that the domain controller was removed successfully. If you receive an error that the object could not be found, Active Directory might have already removed from the domain controller.
    1. Type quit, and press Enter until you return to the command prompt.
    To remove the failed server object from the sites
    1. In Active Directory Sites and Services, expand the appropriate site.
    2. Delete the server object associated with the failed domain controller.
    To remove the failed server object from the domain controllers container
    1. In Active Directory Users and Computers, expand the domain controllers container.
    2. Delete the computer object associated with the failed domain controller.
    1. Windows Server 2003 AD might display a new type of question window, asking you if you want to delete the server object without performing a DCPROMO operation (which, of course, you cannot perform, otherwise you wouldn't be reading this article, would you...) Select "This DC is permanently offline..." and click on the Delete button.
    1. AD will display another confirmation window. If you're sure that you want to delete the failed object, click Yes.
    To remove the failed server object from DNS
    1. In the DNS snap-in, expand the zone that is related to the domain from where the server has been removed.
    2. Remove the CNAME record in the _msdcs.root domain of forest zone in DNS. You should also delete the HOSTNAME and other DNS records.
    1. If you have reverse lookup zones, also remove the server from these zones.
    Other considerationsAlso, consider the following:
    • If the removed domain controller was a global catalog server, evaluate whether application servers that pointed to the offline global catalog server must be pointed to a live global catalog server.
    • If the removed DC was a global catalog server, evaluate whether an additional global catalog must be promoted to the address site, the domain, or the forest global catalog load.
    • If the removed DC was a Flexible Single Master Operation (FSMO) role holder, relocate those roles to a live DC.
    • If the removed DC was a DNS server, update the DNS client configuration on all member workstations, member servers, and other DCs that might have used this DNS server for name resolution. If it is required, modify the DHCP scope to reflect the removal of the DNS server.
    • If the removed DC was a DNS server, update the Forwarder settings and the Delegation settings on any other DNS servers that might have pointed to the removed DC for name resolution.
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans