Updated: MaTwitter Facebook LinkedIn Previous Next Tags: OnPremise, Reporting Services, SQL ServerĬategories: Dynamics 365 / CDS / PowerApps Only solution was using SQL Server 2016 end installing Reporting Services using the classic server installer. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM DWORD IgnoreChecks = 1 It will let you create an org but I wasn’t able to import or upgrade existing ones due to errors during the process. You can set a flag in registry to ignore the errors if you are ok to proceed without reporting services. Without correct setup of SrsDataConnector environment checks will fail when you try to provision a new organization or import an existing one. After successful installation SrsDataConnector wizard was unable to locate my SSRS instance. I had even tried to use XML config to pass the instance parameters to the SetupSrsDataConnector.exe directly. It configures SSRS instance differently but I could find why Reporting Extensions wizard fails to locate it. Since SQL Server 2017 we have a standalone installer of Reporting Services. Everything went smooth until I tried to reinstall Dynamics 365 Reporting Extensions via SetupSrsDataConnector.exe. Important note: It is not listed as a supported version And here is probably why. I came across a strange issue when trying to upgrade CRM deployment to Microsoft SQL Server 2017. Dynamics 365 Reporting Extensions and SQL Server 2017 incompatibility
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |