We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. Image for the cookie policy date
Starting in 2019, the Reporting control is no longer included in Essential Studio. If you're experiencing issues with the Syncfusion Reporting Platform, Report Viewer, Report Designer, or Report Writer, we recommend migrating to Bold Reports, our dedicated reporting platform.

Bold Reports offers a comprehensive suite of tools and features for all your reporting needs, and we will help you make a smooth transition from the discontinued control. Our support team at https://support.boldreports.com/ is here to assist you with any questions or difficulties you may encounter during the migration process.

We thank you for choosing Syncfusion and appreciate your understanding.

Report Viewer Throws an exception when it can't load a resource


I have the most recent version of the SDK and I am getting a failure in the ReportViewer Component.

The failure is: The component 'Syncfusion.Windows.Reports.Viewer.Utils.LoadingIndicator' does not have a resource identified by the URI '/Syncfusion.ReportViewer.Wpf;component/utils/loadingindicator/loadingindicator.xaml'.

The problem is the extension name... in the above message (and in the assembly itself) the extension used is .xaml.  However, the actual resource that exists in the assemby is '/utils/loadingindicator/loadingindicator.baml'.
The extention is baml, not xaml.  Though the file looks like xaml to me.

In any case, because of this error, we cannot make use of the ReportViewer component, is there some way to get around this problem?


1 Reply

VS Vinoth Srinivasan Syncfusion Team April 5, 2016 01:30 PM UTC

Hi Tim,

Thanks for contacting Syncfusion support.

We have created a simple sample with our latest essential studio version, .NET Framework 4.5.1 and its working fine at our end. We suspect that the error may occurred due to the mismatch in the versions of assemblies and its dependent Assemblies. Please ensure assemblies version and dependent assemblies are in same version and referred properly. If you still face this issue then share the following details (Product version,.NET Framework, Machine configuration, Detailed information of error) with us, it would be helpful for us to provide a solution at the earliest.


Live Chat Icon For mobile
Up arrow icon