Workaround: Unable to complete setup of MDM – Could not obtain information about Windows NT group/us

Installed SQL Server 2008 R2 MDM on Windows Server 2008 R2 x64.  The SQL Server service account is a local user account in the admins group.  The database configuration fails with

Microsoft.MasterDataServices.Configuration.ConfigurationException: Could not obtain information about Windows NT group/user , error code 0x5. —> System.Data.SqlClient.SqlException: Could not obtain information about Windows NT group/user , error code 0x5.

   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)

   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)

   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

   at Microsoft.MasterDataServices.Configuration.DatabaseUtilities.ProcessSqlString(String commandSql, SqlConnection connection)

   at Microsoft.MasterDataServices.Configuration.DatabaseUtilities.InstallMasterDataServicesDatabase(SqlConnection connection, String databaseName, String collation, String adminAccount)

   at Microsoft.MasterDataServices.Configuration.Commands.NewMasterDataServicesDatabase.InternalProcessRecord()

   at Microsoft.MasterDataServices.Configuration.Commands.ConfigurationCmdlet.ProcessRecord()

   at System.Management.Automation.CommandProcessor.ProcessRecord()

   — End of inner exception stack trace —

   at Microsoft.MasterDataServices.Configuration.InstanceManager.Execute(Command command)

   at Microsoft.MasterDataServices.Configuration.InstanceManager.CreateMasterDataServicesDatabase(DatabaseServerInformation serverInformation, DatabaseInformation databaseInformation)

   at Microsoft.MasterDataServices.Configuration.UI.MdsDatabase.CreateNewDatabase()

I managed to workaround this problem by using a SQL Server logon account during setup rather than a domainuser account. 
Looks like a bug to me which should hopefully be fixed in a later build.

HTH
Ben

Can you check the following:1) Go to Start > Administrative Tools > Computer Management2) Expand “Services and Applications”3) Double-click on Services4) Select the SQL Server instance where you are trying to install the MDS database.  Right-click and select Properties.5) Select the “Log on” tab.This should be set to log on with “Network Service” or with a domain account.If a local account is specified you would have the problem you’re experiencing./

That is correct, the service account is a local account.  My workaround  was to use a SQL Server logon rather than change the service account.

Hi Ben.There’s a lot of info regarding this issue in this thread http://social.msdn.microsoft.com/Forums/en-US/mdmsetup/thread/22eecda4-aaa2-4fcd-9c15-02502520bc0eBasically the SQL server  service account needs permissions to look up info about the domain account you’re providing. This has been a problem for  a few people since most are setting MDS up on stand alone dev environments. The error message is quite good though the setup  is not too well documented, early days I guess…The SQL Server account works because the SQL Server service account doesn’t have to talk to the domain to verify it. So either run SQL server under the network service account or use a domain system account. I aslo had issues with the network service account due the way our network is setup.Or the SQL account works fine. Most company environments will have SQL server running under domain system accounts so it probably won’t be too much of a problem for these environments.Shaun