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

Thursday, September 1, 2011

dynamics crm dynamics crm 2011

Hi,

Installing a completely new Dynamics CRM 2011 on top of Windows Server 2008 R2 and a separate SQL Server 2008 R2 I faced the following issue:

Microsoft.Crm.Setup.Server.GrantConfigDBDatabaseAccessAction failed

Windows NT user or group 'MYDOMAIN\SQLAccessGroup' not found. Check the name again.

[Cause]

Everything was right (the account I was using had enough privileges, the group exists in the AD, etc.).

After some research I found some links that talked about the problem but didn’t match at all with my scenario (i.e. one talks about a german deployment issue). Then, I came up with this thread, where I found some (unbelievable) clue: it seemed the install process was not able to create the login in SQL Server because a SQL Server Management Studio query window was open and locked one of the system DB.

Odd, but true :p). But, just by closing SSMS was not enough.

[Solution]

In my case, I had a Remote Desktop Session opened with my SQL Server.

So, my solution was: just logoff SQL Server remote desktop session :p)

This way everything was closed.

Then, got back to my Dynamics CRM setup and clicked on “Retry”. Installation continued smoothly :)

Hope it helps to save somebody else’s time.

PP [twitter: @pabloperalta]

16 Comments

Thanks a tonn.. that really helped me..

Pooja - Friday, September 16, 2011 9:44:04 PM

Had exactly the same issue and this resolved it thanks - would never have occured to me that having a remote desktop session open would prevent the CRM install. Thanks, saved me time!

Alex Goss - Wednesday, November 16, 2011 3:08:45 PM

totally helped me. cheers

ajcsco - Thursday, January 26, 2012 3:46:20 PM

Thanks for putting this up. I love it when the first article I go to has the solution!

MG - Sunday, March 4, 2012 12:42:25 PM

Thanks a lot, i just had to close SQL Server Management Studio :-)

Thomas Henckel - Wednesday, April 11, 2012 8:32:31 AM

Thanks! Your solution worked like a charm :)

Neal - Sunday, October 14, 2012 11:46:38 PM

This helped, reading the error mesage, one just cannot image the solution. Thanks a lot

Rakesh - Wednesday, October 31, 2012 12:09:06 PM

Thank you for all your comments! Glad to know it was some help.

pablop - Wednesday, October 31, 2012 12:52:01 PM

Hi, I think, that what really helps, is to wait for a while - e.g. 5 minutes, and then retry.
The problem is probably caused by some caching delayes between sql server and AD, so it really doesn't matter, whether you close any db connection or not. Just wait a minute :)

JS - Friday, January 18, 2013 11:17:42 AM

Incredible but true! Thank you!

Matteo - Friday, January 18, 2013 3:38:04 PM

Helped me. Thank you.

Edward Birch - Monday, June 3, 2013 1:00:11 AM

THANKS SOOOOOOO MUCH! At 2AM from South Africa, this page solved MANY headaches!!! Thanks!

Frustrated Developers - Thursday, June 6, 2013 12:21:12 AM

Spot on, thank you very much.

Edward Rhodes - Friday, September 20, 2013 1:21:05 PM

This just saved my butt, thanks a mil :)

Stefan - Thursday, October 17, 2013 12:39:56 PM

Thank you very. It helped me

Sri - Friday, November 15, 2013 12:32:20 AM

Ran into this with the CRM 2013 installation today. Found that my CRM server was defaulting to a domain controller in a different site, so the group had not sync'd back to the local DC. Found that my SQL server had correct IP settings, but my CRM server for some reason had a primary WINS server defined as the DC in the other site. I rolled back my CRM server VM, removed the WINS server from the IP settings, then rebooted and the installation worked. I'm inclined to believe that as one poster suggested, for most people it is just a matter of waiting for AD to sync.

Thanks for your posts.

Jeff - Tuesday, December 3, 2013 9:24:23 PM

Comments have been disabled for this content.