locked
Action Microsoft.Crm.Setup.Server.GrantConfigDBDatabaseAccessAction failed. RRS feed

  • Question

  • hi

    i am trying to install crm2011 on a windows 2008 R2 sever using a windows 2003 AD domain controller and i keep getting this error message. i have tried everything on this post and still no result. please help. i have been on this for 2days now

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

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


    System integrator

    Thursday, August 30, 2012 8:20 AM

Answers

  • Try dropping the SQL server from the domain and re-adding it again.

    Jason Peterson

    • Marked as answer by youngceaser Friday, August 31, 2012 2:19 PM
    Thursday, August 30, 2012 11:21 PM

All replies

  • Hi,

    the SQLAccessGroup is missing on the SQL server. Manually add the group to the logins folder on the SQL side.


    Visit my blog for CRM material, improving performance, kerberos, IFD, development tips, etc. :) http://quantusdynamics.blogspot.com

    Thursday, August 30, 2012 9:37 AM
    Answerer
  • i tried this but it gives me this error

    TITLE: Microsoft SQL Server Management Studio
    ------------------------------

    Create failed for Login 'CCSNL\SQLAccessGroup {66c79543-7fd0-4e92-82ab-a93c7709e19a}'.  (Microsoft.SqlServer.Smo)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1+((KJ_RTM).100402-1539+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+Login&LinkId=20476

    ------------------------------
    ADDITIONAL INFORMATION:

    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

    ------------------------------

    Windows NT user or group 'CCSNL\SQLAccessGroup {66c79543-7fd0-4e92-82ab-a93c7709e19a}' not found. Check the name again. (Microsoft SQL Server, Error: 15401)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600&EvtSrc=MSSQLServer&EvtID=15401&LinkId=20476

    ------------------------------
    BUTTONS:

    OK
    ------------------------------


    System integrator

    Thursday, August 30, 2012 10:00 AM
  • The groups are different:

    CCSNL\SQLAccessGroup {66c79543-7fd0-4e92-82ab-a93c7709e19a}

    mydomian\SQLAccessGroup {7f164407-7602-4435-9179-f683e9f014cf}'

    you receiving a not found error on the first one. If the GUID on the second group is correct you should try adding that one.


    Visit my blog for CRM material, improving performance, kerberos, IFD, development tips, etc. :) http://quantusdynamics.blogspot.com

    Thursday, August 30, 2012 10:07 AM
    Answerer
  • the first one is the actuall group and GUID the second was just an illustration. I have tried with this one and no luck. i have also tried uninstalling dynamics crm and reinstalling and still the same issue keeps coming up.


    System integrator

    Thursday, August 30, 2012 10:23 AM
  • The user that is running the CRM setup needs to have permissions to write to the OU in AD you have selected and sys admin on the SQL server, otherwise will not be able to create and add the groups.

    Visit my blog for CRM material, improving performance, kerberos, IFD, development tips, etc. :) http://quantusdynamics.blogspot.com

    Thursday, August 30, 2012 10:48 AM
    Answerer
  • yes the user is  in both the DomainAdmin security role and use Administrator roles of the AD also he is an Administrator on the server running SQL.also a sys admin on SQL server.

    System integrator

    Thursday, August 30, 2012 11:20 AM
  • Try dropping the SQL server from the domain and re-adding it again.

    Jason Peterson

    • Marked as answer by youngceaser Friday, August 31, 2012 2:19 PM
    Thursday, August 30, 2012 11:21 PM
  • Thanks jason dropping the SQL server from the domain worked.

    System integrator

    • Marked as answer by youngceaser Friday, August 31, 2012 2:19 PM
    • Unmarked as answer by youngceaser Friday, August 31, 2012 2:19 PM
    Friday, August 31, 2012 2:19 PM