Hello everyone and welcome to my blog. In today’s blog I will discuss in the detail the problems you may encounter while executing a report from Dynamics CRM and how to resolve the same.
Through my blog I share interesting tips and discuss on latest releases of Microsoft.NET technologies, Dynamics 365 and Power Platform, SharePoint and Client scripting libraries. Please subscribe to my blog to stay updated.
The blog may also help to resolve the below errors.
- Unable to fetch the list of data extensions from server
- Immediate caller has insufficient privilege to run the report as user.
Without further ado, let’s get started. I will list down the steps you should validate if you are not able to run the Dynamics CRM Reports from within the application.
Step 1 – Validate your SQL Server reporting services is up and running.
This is the first step of validation. Navigate to Services and make sure your SQL Server reporting services is running. If you CRM is multi-server deployment, make sure the reporting services is running under a domain service account and not NETWORK SERVICE.
It is very important to run the reporting services under a domain account. This is because the account running the reporting services should be added to certain AD groups which we will discuss in a later section of the blog.
You administration might have a problem to add NETWORK SERVICE account to the required AD groups
Step 2 – Provide permission to the Reporting services account on your CRM Database and CONFIG database.
Make sure your reporting services account have the following permissions on <Orgname>_MSCRM and MSCRM_Config database. You can provide permission to these databases from SQL Server management studio.
Provide the role memberships are per the below illustration
You need to create a login for the reporting services account and then provide the required permissions for the login using SQL server management studio.
Step 3 – Configure the service account and database credentials in Reporting Services Configuration Wizard
Open Reporting services configuration manager and make sure the reporting services account is set up in both the Service Account and Database section.
Step 4 – Add the Reporting services account to the required AD groups.
This is probably the step missed in majority of the deployments and the cause of errors during reporting. The reporting services account should be added to the PrivReportingGroup and PrivUserGroup in active directory.
Bot how do I find the PrivReportingGroup and PrivUserGroup for my organization. You can follow this blog to get the details.
Once you have identified the groups, you need to work with your AD team to add the reporting services account user to the group.
Step 5 – Reset IIS in CRM front-end servers
The final step is to reset the IIS in the application servers (CRM Front-end servers). If you have multiple front-end servers, make sure to reset the IIS in each of the servers.
Remember, this is a very important step. Recycling the application pool or starting and stopping the application pool may not yield the desired result.
Once all the steps are complete, your reports should run fine.
Hope this helped. For similar interesting topics on Microsoft.NET and Power platform, you can subscribe to my blog.
Debajit Dutta
Business Solutions MVP