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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

CRM 2015 setup fails, stating AD error

(0) ShareShare
ReportReport
Posted on by 10

Hi,

I try to install CRM 2015 on a 2012 R2 Server with MSSQL Server 2012 on the same host.

Prerequisites are fine, the setup-user is member of domain admins and local admins. Setup creates the MSCRM_CONFIG database and fails afterwards with the following exception (translated):


15:44:40|  Error| Install exception.System.Exception: Error on action Microsoft.Crm.Setup.Server.InstallConfigDatabaseAction. ---> Microsoft.Crm.CrmSecurityException: Could not find AD entry for : <setup-user> with SearchFilter: samAccountName ---> System.DirectoryServices.ActiveDirectory.ActiveDirectoryObjectNotFoundException: global catalog not found in the overall structure (forest?) 'CRM15.DOMAIN.COM' 
   at System.DirectoryServices.ActiveDirectory.GlobalCatalog.FindOneInternal(DirectoryContext context, String forestName, String siteName, LocatorOptions flag)
   at Microsoft.Crm.SecurityUtils.GetActiveDirectoryEntry(String searchItem, String searchFilter, String searchItemLogInfo, Boolean throwIfNotFound, String domainName)


*This post is locked for comments

I have the same question (0)
  • Verified answer
    MdgM Profile Picture
    10 on at

    Solved this one myself, maybe my solution can help others with similar problems.

    Lesson learned: if it looks like an AD error it is an AD error.

    dcdiag put me on the right track - the DC was missing a DNS entry I've never seen before.

    Missing information: we use a perfectly working BIND DNS server on FreeBSD that is only updated by the DHCP server and does not permit updates by anybody else. The DC has been set up only for CRM.

    I had registred several addresses manually (following a online tutorial). That was sufficient to allow user login and led me to the assumption that the DC configuration is working.

    The solution lies in giving the DC the right to write to the DNS as follows:

    - modify in the named.conf the allow-update clause of the relevant zone by adding the IP address of the DC

    - restart DNS daemon

    - restart the DC

    The DC registers a handful of additional DNS records and the CRM setup completes without complaints.

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…

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