[In addition to blogging, I am also now using Twitter for quick updates and to share links. Follow me at: twitter.com/pabloperalta] Microsoft.Crm.Setup.Server.GrantConfigDBDatabaseAccessAction failed. Windows NT user or group 'MYDOMAIN\SQLAccessGroup' not found. Check the name again. - Pablo Peralta's Blog
Thursday, September 01, 2011 1:17 PM pablop

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

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]

Filed under: ,

Comments

# Microsoft.Crm.Setup.Server.GrantConfigDBDatabaseAccessAction failed. Windows NT user or group 'MYDOMAIN\SQLAccessGroup' not found. Check the name again. - Pablo Peralta's Blog

Pingback from  Microsoft.Crm.Setup.Server.GrantConfigDBDatabaseAccessAction failed. Windows NT user or group 'MYDOMAIN\SQLAccessGroup' not found. Check the name again. - Pablo Peralta's Blog

# Agenda MVP (5 de septiembre – 11 de septiembre)

Monday, September 05, 2011 1:58 PM by MVP Factor

Agenda MVP (5 de septiembre – 11 de septiembre) Martes 6 de septiembre El ABC del despliegue de W7 SP1

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

Friday, September 16, 2011 5:44 PM by Pooja

Thanks a tonn.. that really helped me..

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

Tuesday, September 20, 2011 12:38 PM by Mark Sammon

Result!

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

Wednesday, November 16, 2011 10:08 AM by Alex Goss

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!

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

Thursday, January 26, 2012 10:46 AM by ajcsco

totally helped me. cheers

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

Sunday, March 04, 2012 7:42 AM by MG

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

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

Wednesday, April 11, 2012 4:32 AM by Thomas Henckel

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

Leave a Comment

(required) 
(required) 
(optional)
(required)