Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Error on install of CRM: SQLAccessGroup not found RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I've been trying to install CRM 4.0 in a VM linked to SQL Server 2008 and Windows Server 2008.  Every time I try to run the install, I get an error message:

    Action Microsoft.Crm.Setup.Server.GrantConfigDBDatabaseAccessAction failed. 
    Windows NT user or group 'EHEALTHOZ\SQLAccessGroup' not found. Check the name again.

    I've tried:
    - a complete rebuild,
    - tried using SQL 2005 instead of SQL 2008
    - tried an unattended install to setup the SQLAccessGroup group in advance of the install

    I'm using all the guidance Microsoft has published regarding SQL2008 and Windows 2008 support for CRM 4, but that hasn't helped.

    From the server I'm installing CRM on, I can definitely browse the AD Users & Computers to find EHEALTHOZ\SQLAccessGroup

    Any ideas on what might be at fault??

    Thanks
    Sunday, December 20, 2009 10:02 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Does this user EHEALTHOZ\SQLAccessGroup have an access to SQL Server ?
    You can check also here:

    http://nishantrana.wordpress.com/2009/05/21/action-microsoft-crm-setup-server-grantconfigdbdatabaseaccessaction-failed-windows-nt-user-or-group-not-found-check-the-name-again/
    My Dynamics CRM Blog: http://bovoweb.blogspot.com
    Sunday, December 20, 2009 11:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    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

    • Proposed as answer by AdrianGeorge Sunday, June 6, 2010 3:19 PM
    Wednesday, May 5, 2010 2:38 AM
  • Question
    Sign in to vote
    9
    Sign in to vote

    Hi,

    I know this topic is a bit old but I just want to let you know that I had this error as well and something worked for me.

    SSMS was open on the SQL Server. I closed it, clicked on "Retry" and it worked... The error message was not that obvious but it seemed the install process was not able to create the login in SQL Server because a query window was open and locked one of the system DB.

    I got so many errors installing CRM3 or CRM 4 over the last year and now the first thing I do is closing SSMS when running an install. It fixes a lot of issues.

    • Proposed as answer by PrateekSethi Tuesday, June 14, 2011 9:37 PM
    Sunday, June 6, 2010 3:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I have the same error :

    Action Microsoft.Crm.Setup.Server.GrantConfigDBDatabaseAccessAction failed. 
    Windows NT user or group 'domainename\SQLAccessGroup' not found. Check the name again.

    I apply the hotfix but there is the same error.

    My config is:

    - DC1 (server 2008 R2) with AD.

    - DC2 (server 2008 R2) with sqlserver2008 and CRM 4.0

    Please help me .

    thanks

    Wednesday, June 9, 2010 1:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I have the same error, any new issues ?

    Thanks

    Tuesday, June 22, 2010 8:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, I found where was my problem.

    My 2 DC were derived from the same VHD and therefore had the same SID.

    So I changed the SID of a DC.
    Wednesday, June 30, 2010 7:55 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, I found where was my problem.

    My 2 DC were derived from the same VHD and therefore had the same SID.

    So I changed the SID of a DC.

    Hello,

    I have the same error :

    Action Microsoft.Crm.Setup.Server.GrantConfigDBDatabaseAccessAction failed.  
    Windows NT user or group 'domainename\SQLAccessGroup' not found. Check the name again.

    I apply the hotfix but the problem is not solved. 

    Wednesday, September 8, 2010 4:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello guys,

    if your environment is VM-Workstations, this issue belongs to sid issue when VM workstations are created from the template or copy of another machine. please run newSid utility before installing any application or tools on new created machine. when you know sid issue, do not expriement further, is a mere waste of time. just re-build your environment as below:

    1. Create VM workstation from the template again.

    2. Start the VM Workstations. When prompted, answer as "Copied"

    3. Run the NewSid utility

    4. Restart the workstations

    5. Start again and install all the application what you require

    follow the same steps for all machines you build in the group.

    regards,

    balu

     

     

    Thursday, February 3, 2011 9:12 AM
  • Question
    Sign in to vote
    3
    Sign in to vote
    I could not believe this when I read it first time. Reluctantly, I tried this out and closed SSMS, click Retry. And it worked! No more GrantConfigDBDatabaseAccessAction errors.. thanks Adrian!
    Tuesday, June 14, 2011 9:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hey Adrian ... a year later, I'm installing CRM 2011, and same error, and closing Management Studio worked for me - thanks!
    Kurt Sayer
    Thursday, June 23, 2011 11:32 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi, I confirm this hint for CRM 2011. I got this "'SQLAccessGroup' not found" error, killed ssms.exe process (had to use task manager's "show processes from all users" option to find all instances), clicked Retry and the installation continued!

    Although the solution is a bit absurd, it works, and it's easy.

    Z.

    PS Just to explain the solution to computer geeks I found an every day life analogy: it's like when your microwave oven doesn't work and somebody adviesed you to switch off the light in the bathroom and try again :)

    Friday, June 24, 2011 8:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I also got the same error whiel installing the CRM 2011 setup :-

    Action
    Microsoft.Crm.setup.server.GrantConfigDBDatabaseAccessAction failed.
    Windows NT user or group 'HQ\SQLAccessGroup' {GUID}' not found. Check the name again.

    As a solution I did the follwoing and it worked for me :-

    Manually added these two groups SQlAccessGroup{GUID} and PrivReportingGroup{GUID} in SQL

    Security->Logins->Right Click -> New Login-> created both groups ( SQlAccessGroup{GUID} and PrivReportingGroup{GUID} ) one by one and gave proper permissions.

    -Clicked Retry and the installation continued!



    Tuesday, August 16, 2011 2:56 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Unbelievable !!

    I didn't even had ssms.exe running but loggin off from my remote desktop session in the SQL Server worked! Installation continued!

    Really incredible :p)

    PP

    Microsoft MVP Dynamics CRM | My Twitter: http://twitter.com/pabloperalta | My blog: http://weblogs.asp.net/pabloperalta | Blog en Español: http://wwww.elblogdedynamicscrm.com
    Thursday, September 1, 2011 3:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    BTW, I just blogged about this here:

    http://weblogs.asp.net/pabloperalta/archive/2011/09/01/microsoft-crm-setup-server-grantconfigdbdatabaseaccessaction-failed-windows-nt-user-or-group-mydomain-sqlaccessgroup-not-found-check-the-name-again.aspx

    Regards,

    PP

    Microsoft MVP Dynamics CRM | My Twitter: http://twitter.com/pabloperalta | My blog: http://weblogs.asp.net/pabloperalta | Blog en Español: http://wwww.elblogdedynamicscrm.com
    Thursday, September 1, 2011 3:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    same here for CRM 2011 on 2008 R2, a retry solved it. (still had my RDP connection to MS SQL open)

     

    ---------------------------
Microsoft Dynamics CRM Setup
---------------------------
Action Microsoft.Crm.Setup.Server.GrantConfigDBDatabaseAccessAction failed.

Windows NT user or group 'DEVAD002\SQLAccessGroup {7f164407-7602-4435-9179-f683e9f014cf}' not found. Check the name again.


---------------------------
Retry   Cancel   
---------------------------


    Tuesday, September 20, 2011 11:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This should also help

    http://nishantrana.wordpress.com/2013/05/07/fixed-microsoft-crm-setup-server-grantconfigdbdatabaseaccessaction-failed-windows-nt-user-or-group-sqlaccessgroup-not-found-in-crm-2011/

    Regards,

    Nishant Rana

    http://nishantrana.wordpress.com https://twitter.com/#!/nishantranacrm

    Thursday, May 9, 2013 8:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Just had the same issue with a fresh CRM 2013 install.  Logging out of the SQL box and hitting Retry fixed it.
    Wednesday, September 17, 2014 6:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Just wanted to say that this is a great thread. All the contributed, thanks for your contribution.

    I think we will see this error a great deal, since CRM 2011 is going out of support.  Therefore , there will be quite a few CRM 2011 installs on Virtual environments in order to upgrade them to 2016 before going to the cloud. 

    I'm doing one now, and sure enough this error popped up.  Thanks folks.

    Curtis J Spanburgh

    Monday, May 16, 2016 2:35 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    @AdrianGeorge

    Same with CRM 2016.

    Thanks !

    Gilles Tremblay
    MCSE Server | Desktop | Messaging | Collaboration | Productivity | Mobility | Cloud Platform and Infrastructure

    Dont forget to mark as Answered if you found this post helpful.

    DISCLAIMER: This post is provided "AS IS" with no warranties of any kind, either expressed or implied, and confers no rights. Always test before!


    Friday, February 24, 2017 7:11 PM