The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
I am using SSRS 2019, latest version, on Windows 2019 server. When I attempt to create a subscription, I get this error message in the SSRS log: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.ReportingServices.Cloud.DataExtensions' or one of its dependencies.
I have checked the file system and this assembly is not present. How can I fix this? Where can I get this assembly?
Hi @SQLJiim
The error you're encountering in SSRS 2019, "System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.ReportingServices.Cloud.DataExtensions'," indicates that the SSRS instance is attempting to use a cloud-related data extension that is either missing or improperly configured. This assembly is part of the extended functionality for integrating cloud data sources into SSRS reports. The error suggests that the required assembly is not found in the expected location on your file system.
To fix this issue, you will need to obtain the missing assembly, which is typically part of the SQL Server Reporting Services (SSRS) or SQL Server Data Tools installation. You can resolve this by ensuring that all necessary SSRS components are installed correctly, especially any components related to cloud data sources. Check if you need to install additional data extensions or features through the SQL Server installation center. In some cases, reinstalling or updating SSRS with the latest service packs or patches may resolve missing dependencies. If you're using any cloud-based data sources (like Azure), ensure that the corresponding extensions for those sources are properly installed. Additionally, you can manually search for the missing file or download the required extensions from official Microsoft sources.
Did you found an solution with microsoft support?
You are probably better to raise a ticket with Microsoft support for this sort of issue.