It’s been couple of months since I have written a blog. One of those years where health has gone south for me and I am gradually limping in back into my stride.
Ironically, as I am making my way back, I started with Dynamics V9.0 on-premise project for one customer as well and it’s been more than couple of years since I worked on an on-premise project. And it’s been a quite a learning so far. My next few blogs would be on my experiences with setting up Dynamics on-premise latest version starting with the easiest one.
So coming to the topic here. You may be thinking – why this post? To be honest, there a quite a few blogs which discuss on this. However each represents a specific solution. However this problem can arise for various reasons and fix suggested by one may not work for another. In this post I collate all the possible causes and their remediation. Feel free to write to me in case I miss something. I would love extra knowledge and add them to my post here.
P.S After fixing the current issue by following the instructions of this blog, you may face issue of missing service ReportServer$SSRS. Check out this blog to know how to resolve the issue.
Server : Windows Server 2016 datacenter
CRM : V9.0
SQL server: SQL Server 2017
This issue is not specific to V9.0 and users have faced this with earlier versions of CRM on-premise installations.
Check 1: Run reporting extensions set-up (SetupSrsDataConnector.exe) from box where reporting services is installed.
This is the easiest fix. Make sure you are running the set-up from the machines where reporting services is installed.
If you are running from reporting services box only but still the issue persist, lets go for Check 2.
Check 2: Service account in Report Server configuration manager must be part of PrivReportingGroup
To verify this, open Report Server configuration manager.
Navigate to “Service Account” on left navigation pane and verify your account. Here I am using a service account “xrmforyouadmin”. We need to verify if “xrmforyouadmin” belongs to PrivReportingGroup in Active Directory.
This step might require your domain admins help. Active directory is not something you will have access to as CRM consultant. However I am providing screenshots below to help you understand better so that you can guide your active directory admin in the right direction.
Open “Active directory users and computers” and then click on Domain controllers. You may find multiple PrivReportingGroups in there. To find the right one for your CRM Organization, you can follow the below link.
Get PrivUserGroup specific to your CRM Organization in Microsoft Dynamics CRM
Open the “PrivReportingGroup” specific to your CRM organization and add the service account to the group.
Now go back and run SetupSrsDataConnector.exe. Check to see if the issue is fixed. Not fixed? Lets go for the next checklist.
Check 3: Make registry entries in SQL Server box.
The first thing to note here is all the below changes should be made in SQL server box. You would need administrative permissions on the machine to perform these operations. Please follow the below steps:
- Open Registry Editor (regedit.exe)
- Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\RS
- Check for the Key MSSQLSERVER. If absent, create a new key as shown in the below screenshot. Key Name – MSSQLSERVER, Key value – SSRS
- We are done with this entry. We need to create one more entry. But for that we would need the SQL server version number installed. But how do I get it? Well, there are many ways. I am showing one of them. Open SQL server management studio and connect to database instance. Then type the below query.
As you can see from above screenshot, there is a version number in the result. Copy the same. In my case it is – 14.0.2027.2
Now navigate to – “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SSRS\Setup”
Look for the entry with the name – “Version”. If not found create a new string value with name – “Version” and value as version of SQL server obtained from earlier step.
All set and done. Now restart SQL server and reporting services and try to install reporting extensions. The installation should successfully complete now
In case the issue is not fixed, the last option is to try install reporting extensions via configuraiton file by adding the instance name into the configuraiton.xml as detailed in below Microsoft Documentation link.
P.S After fixing the current issue by following the instructions of this blog, you may face issue of missing service ReportServer$SSRS. Check out this blog to know how to resolve the issue.
Hope this helped!
Debajit Dutta
Business Solutions MVP
Nice Blog Debajit, Thanks for putting this all together. Wish you a good health and quick recovery.