locked
Action Microsoft Crm Setup Server Crant Config dbdatabase accsess action failed Windows NT user group qu\SQLAccessGroup not foun RRS feed

  • Question

  •  

    Hi

    i got this error under install of crm 4

    Action Microsoft Crm Setup Server Crant Config dbdatabase accsess action failed Windows NT user group qu\SQLAccessGroup not found check name again.

    some one who knows what it can be

    the sytem is

    new install of

    win 2003 server sp2

    msql 2005 sp2

     

    och crm

     

     

    Thursday, January 15, 2009 3:41 PM

Answers

  • Such problem occur when we do CRM installation on Windows Server 2008 R2 which is under the domain hosted in Windows 2000 server.

    This kind of error occur when a program calls the LookupAccountName function to retrieve a security identifier (SID) for an account.

    So, CRM installation is stopped when the AD groups created by CRM (SQLAccessGroup, ReportingGroup, UserGroup, etc.) cannot be added into SQL security logins.

    Installing the hotfix including in this article will solve the problem.

    http://support.microsoft.com/kb/976494

    Wednesday, May 5, 2010 2:41 AM

All replies

  •  

    Have you created SQLAccessGroup in Active directory domain?
    Thursday, January 15, 2009 8:27 PM
  • Does the user that is doing the CRM install have full rights on the SQL server?

     

    Friday, January 16, 2009 1:38 PM
  • Such problem occur when we do CRM installation on Windows Server 2008 R2 which is under the domain hosted in Windows 2000 server.

    This kind of error occur when a program calls the LookupAccountName function to retrieve a security identifier (SID) for an account.

    So, CRM installation is stopped when the AD groups created by CRM (SQLAccessGroup, ReportingGroup, UserGroup, etc.) cannot be added into SQL security logins.

    Installing the hotfix including in this article will solve the problem.

    http://support.microsoft.com/kb/976494

    Wednesday, May 5, 2010 2:41 AM
  • Hello,

    I searched the web extensively for a fix for this, but all I was able to find were instances where people had an open connection to SQL whether through SSMS or a remote connection. This was not the case during my installation so this resolution was invalid. For me the resolution to this issues was to install the required windows roles prior to the SQL install. Install IIS, Indexing Services and the Application Server roles prior to the CRM installation. I believe it's specifically the Application Server role that was most important. When installed SQL before installing these roles I continuously received this error during the CRM install. When I installed these roles prior to the CRM install I did not.

    Thanks,

    Bob 

    Friday, September 20, 2013 7:51 PM