I recenty worked through an issue where a customer was receiving the following error when attempting to install the CRM 2011 Reporting Extensions:
Check ReportingAccountMemberOfSecurityGroupValidator : Failure: A Microsoft Dynamics CRM Server component is using the same account as the instance of SQL Server Reporting Services.
This error can occur for a variety of reasons. One reason can be related to the SQL Reporting Services service being started by a domain account that is a member of the SQLAccessGroup (this account does not need to be in the SQLAccessGroup). The same situation could occur if the SQL Reporting Services service is starting with the Network Service account and the SQL Reporting Services server name is located within the SQLAccessGroup. To get past this issue, you have two options:
- Remove the account from the SQLAccessGroup
- Use the IgnoreChecks registry key to get past this error message in the short term (specified in KB 974584). It would be recommended to remove the account that is in the SQLAccessGroup at a later time.
There may be situations where the CRM server and the SQL Reporting Server are installed on the same physical server running under the same account. Ideally, the services would be running under different accounts. If the CRMAppPool and the SQL Reporting Services service are running under the same account (and that account is added to the SQLAccessGroup), you would receive a warning message rather than an error message.
The reason that the error occurs is listed below:
Microsoft Dynamics CRM Reporting Extensions should not be installed on an instance of Microsoft SQL Server Reporting Services that is running under an account that is a member of the SQL Access Group. This can occur when Microsoft SQL Server Reporting Services is running under the same account as a Microsoft Dynamics CRM Server 2011 component. This configuration can make the system vulnerable to certain attacks. During installation, Setup detects this scenario.