Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Trying to install Reporting Extension for CRM 2016 but SSRS instance is blank.
VM containing (SQL & CRM on same machine)
Can you please help me how to fix the error below (SSRS instance name is empty). Can we install reporting extension on SQL server 2017 (should be OK as I was able to install CRM server)
you did it! nice work. I finally could choose my organisation.
System.Exception: Error.ActionFailed Microsoft.Crm.Tools.Admin.UpgradeDatabaseAction ---> Microsoft.Crm.CrmException: Error in Action: Bin\Microsoft.Crm.DataUpgrade.dll:TrackCustomDatabaseObjects on attempt 3. System.Reflection.TargetInvocationException: Ein Aufrufziel hat einen Ausnahmefehler verursacht. ---> System.IO.FileNotFoundException: Die Datei oder Assembly "Microsoft.SqlServer.Smo, Version=126.96.36.199, Culture=neutral, PublicKeyToken=89845dcd8080cc91" oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.
I had to install Cleartypes SQL Server2012 and SharedManagementObject 2012 because the import gave an exception.
After this was fixed the next Problem occured:
Microsoft.Crm.PackageDeployment.PackageDeployerException: Package BaseCustomControlsCore failed to install on attempt 1.System.AggregateException: Mindestens ein Fehler ist aufgetreten. ---> Microsoft.Crm.MultiTenantPackageDeployment.PackageDeployerImportException: PackageDeployerWrapper: Import Failed status encountered. Details: Failed to load solution Base Custom Controls Core, version: 9.0.0000.0375. See the log file. bei Microsoft.Crm.MultiTenantPackageDeployment.PdExecutor.Process(PackageDeploymentInputArgs input, JobOutput`1 output, CancellationToken ct) bei System.Threading.Tasks.Task.Execute()
Microsoft really blew this one!
The solution with the new dummy service, .... did wirk for me. Reporting services are now isntalled. Gret thanx for the solution!!!!
2. The setup program also needs a windows service names exactly 'ReportServer$SSRS'. To achieve this, just create a dummy blank new service with a specified name and register it using C:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe
How do i do this? I used:sc create ReportServer$SSRS binPath= C:\_Temp\ReportServer$SSRS.exe DisplayName= "ReportServer$SSRS" start= auto
It worked for the Installation check but then i get the error - Cannot start Service ReportServer$SSRS on Computer %1 is not a valid Win32 application.
Do you create this with Visual Studio or how you do it?
Please can you help me out, Thanks!
It worked now for me with that solution.
I created the Service with this command:
sc create "ReportServer$SSRS" binpath= "C:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe"
Do you create this with Visual Studio or how you do it?
- Yes, just like this:
Was wondering if I could get some guidance here.
I already have SRS Data Connector installed and I'm getting the red x' stating that it can't find the SSRS Instance when I run a report.
I followed your steps and made sure that my SSRS service account was part of the PrivReportingGroup
I have a dummy service of ReportServer$SSRS running as I see that in my local services.
I have updated the 2 branches in my registry, my version of SSRS is 14.0.600.906.
I run the executable and select "Repair" and I get the red x's.
Should I uninstall and try a fresh install or is there something else that I'm doing incorrectly.
The accepted solution worked!
Many thanks for posting and persisting with this!!!
When I have encountered this it is usually because I have installed the 32-bit version instread of the 64-bit version of SQL
After spending a few hours I've figured out what exactly should I do to install this glorious SSRS CRM Data Connector (Microsoft Dynamics CRM Reporting Extensions) on SQL Server 2017.These Extensions were for Microsoft Dynamics CRM 2011 but I'm sure you can use this method for CRM 2016 and 365 too. 1. Make sure that in the Report Server Configuration Manager there is specified a service account which is a member of PrivReportingGroup and has a _write permissions_ to this group. This account must not be a member of SQLAccessGroup. At least during installation.2. The setup program also needs a windows service names exactly 'ReportServer$SSRS'. To achieve this, just create a dummy blank new service with a specified name and register it using C:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe
3. After that, we need to open Regedit.exe to make changes that will allow the setup program to discover and validate our SSRS instance.
* In [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\RS] branch add new REG_SZ attribute with name 'MSSQLSERVER' and value 'SSRS'* In [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SSRS\Setup] branch add new REG_SZ attribute with name 'Version' and value '14.0.600.906' (in my case, you should use your version of SQL server)4. Now run the setup program (SetupSrsDataConnector.exe). Some next step must show our SSRS instance and we choose it. After all the steps done we will get the last step with important System Checks which all must be green, thanks to our preparation actions.
Voilà! Setup complete successfully.
5. Manually restart SSRS using stop and start buttons in Report Server Configuration Manager.6. Finally, check in the /Reports web application. Open any data source and check that a new data source type options have appeared.
Business Applications communities