If using Windows 8, you should instead make sure that the .Net 4.5 WCF services features are installed, and HTTP Activation feature is installed, as shown highlighted here:
In MDS Configuration Manager, when you click the button [Enable integration with Data Quality Services] , it may fail with an error when the server is a Windows Domain Controller (DC). The error is:
"Error while trying to enable integration with Data Quality Services. SQL Server returned the following error: Windows NT user or group 'ComputerName\MDS_ServiceAccounts' not found. Check the name again.
The cause of the problem is that MDS has created a global domain group called MDS_ServiceAccounts, and is trying to put the group into the DQS security role. Instead it should use the domainname\MDS_ServiceAccounts. SQL
only allows windows user names (not group names), and MDS is confusing it about group vs. user. This is not fixed in the SQL Server, so use an easy workaround.
1. Manually add DOMAIN\MDS_ServiceAccounts as a Windows User login into your SQL Server security.
Query to run in Management Studio. Replace the placeholder DOMAIN with your own domain name.
IF NOT EXISTS (SELECT * FROM SYS.SYSUSERS WHERE NAME = 'MDS_ServiceAccounts')
CREATE USER [MDS_ServiceAccounts] FOR LOGIN [DOMAIN\MDS_ServiceAccounts]
2. Map the login to access DQS_MAIN role dqs_administrator which in effect is the same thing that the button does.
Query to run in Management Studio:
EXEC sp_addrolemember @rolename=N'dqs_administrator',@membername=N'MDS_ServiceAccounts'
// It will call - ALTER ROLE [dqs_administrator] ADD MEMBER [MDS_ServiceAccounts] within the DQS_MAIN database.
Now the MDS_ServiceAccounts are part of the dqs_administrator role, and MDS can interface with DQS on the same SQL Server instance.
When you try to upgrade the MDS database schema using MDS Configuration Manager after restoring the MDS database on a computer from a backup, you might receive the following error:
"Cannot be enabled because there is already an enabled Service Broker with the same ID."
This happens if the computer on which you restored the MDS database already has another copy of the database restored. When you restore the most recent copy of the MDS database from another computer to the current computer, SQL Server disabled Service Broker,
which is an expected behavior. Subsequently, when you try to upgrade database schema the newly restored database, the MDS Schema upgrade process could not use the same Service Broker GUID as it was used by other copy of database restored from the same computer
earlier, and resulted in an error.
To resolve this issue, you must generate a new GUID for the newly restored database by executing following command:
ALTER DATABASE MDS_DB SET NEW_BROKER
Next, upgrade your MDS database schema.