Share via

RDLC Reports no longer working.

  • Article

Question

Friday, January 24, 2020 11:08 PM

Waaaay back in VS 2010 I made a WINFORMS app that includes some reports.

My old VS2010 has gone on to it's reward, and now I have VS2015 and VS 2019.

Of course the client now wants a SIMPLE change to the report, only a text box changed, and...

1. 2019 and 2015 no longer have a report editor.  I downloaded one for 2019, but didn't find one for 2015.

2. change made, piece of cake, but when I attempt to run the report, I get this...

Microsoft.Reporting.WinForms.LocalProcessingException occurred
  HResult=-2146233088
  Message=An error occurred during local report processing.
  Source=Microsoft.ReportViewer.WinForms
  StackTrace:
       at Microsoft.Reporting.WinForms.LocalReport.EnsureExecutionSession()
       at Microsoft.Reporting.WinForms.LocalReport.SetParameters(IEnumerable`1 parameters)
       at Microsoft.Reporting.WinForms.Report.SetParameters(ReportParameter parameter)
       at Onesource.Reports.SalesInvoice.salesInvoiceForm.salesInvoiceForm_Load(Object sender, EventArgs e) in C:\Users\Bryan Valencia\Documents\Visual Studio 2015\Projects\OneViewBackOffice\OneView\Reports\SalesInvoice\salesInvoiceForm.cs:line 33
  InnerException: 
       ExceptionLevelHelpLink=http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=pvInvalidDefinition&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=1.0
       HResult=-2146233088
       Message=The definition of the report '' is invalid.
       SkipTopLevelMessage=false
       Source=Microsoft.ReportViewer.Common
       StackTrace:
            at Microsoft.Reporting.ReportCompiler.CompileReport(ICatalogItemContext context, Byte[] reportDefinition, Boolean generateExpressionHostWithRefusedPermissions, ControlSnapshot& snapshot)
            at Microsoft.Reporting.LocalService.GetCompiledReport(PreviewItemContext itemContext, Boolean rebuild, ControlSnapshot& snapshot)
            at Microsoft.Reporting.LocalService.CompileReport()
            at Microsoft.Reporting.LocalService.Microsoft.Reporting.ILocalProcessingHost.CompileReport()
            at Microsoft.Reporting.WinForms.LocalReport.EnsureExecutionSession()
       InnerException: 
            ExceptionLevelHelpLink=http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsProcessingError&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=1.0
            HResult=-2146233088
            Message=The definition of this report is not valid or supported by this version of Reporting Services. The report definition may have been created with a later version of Reporting Services, or contain content that is not well-formed or not valid based on Reporting Services schemas. Details: The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition' which cannot be upgraded.
            SkipTopLevelMessage=false
            Source=Microsoft.ReportViewer.Common
            StackTrace:
                 at Microsoft.ReportingServices.ReportPublishing.ReportPublishing.CreateInvalidReportDefinitionException(Exception e)
                 at Microsoft.ReportingServices.ReportPublishing.ReportPublishing.Phase1(Stream definitionStream, String& description, String& language, DataSourceInfoCollection& dataSources, DataSetInfoCollection& sharedDataSetReferences, Boolean& hasExternalImages, Boolean& hasHyperlinks)
                 at Microsoft.ReportingServices.ReportPublishing.ReportPublishing.InternalCreateIntermediateFormat(Stream definitionStream, String& description, String& language, ParameterInfoCollection& parameters, DataSourceInfoCollection& dataSources, DataSetInfoCollection& sharedDataSetReferences, UserLocationFlags& userReferenceLocation, ArrayList& dataSetsName, Boolean& hasExternalImages, Boolean& hasHyperlinks, Byte[]& dataSetsHash)
                 at Microsoft.ReportingServices.ReportPublishing.ReportPublishing.CreateIntermediateFormat(Byte[] definition, String& description, String& language, ParameterInfoCollection& parameters, DataSourceInfoCollection& dataSources, DataSetInfoCollection& sharedDataSetReferences, UserLocationFlags& userReferenceLocation, ArrayList& dataSetsName, Boolean& hasExternalImages, Boolean& hasHyperlinks, Byte[]& dataSetsHash)
                 at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.CompileOdpReport(PublishingContext reportPublishingContext, IDataProtection dataProtection, PublishingErrorContext errorContext, String& reportDescription, String& reportLanguage, ParameterInfoCollection& parameters, DataSourceInfoCollection& dataSources, DataSetInfoCollection& sharedDataSetReferences, UserLocationFlags& userReferenceLocation, ArrayList& dataSetsName, Boolean& hasExternalImages, Boolean& hasHyperlinks, Byte[]& dataSetsHash)
                 at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.CreateIntermediateFormat(PublishingContext reportPublishingContext, IDataProtection dataProtection)
                 at Microsoft.Reporting.ReportCompiler.CompileReport(ICatalogItemContext context, Byte[] reportDefinition, Boolean generateExpressionHostWithRefusedPermissions, ControlSnapshot& snapshot)
            InnerException:

This error occurs on this line:

                ReportParameter InvNoParam = new ReportParameter("InvNo", this.InvoiceNumber);
                this.reportViewer1.LocalReport.SetParameters(InvNoParam);

OK, details: Winforms app.  The report is a local report, set to process locally.

Was originally designed in VS2010, and worked fine there.

I have been all over the site AND stack, without any resolution.

I'd rather live with false hope than with false despair.

All replies (5)

Saturday, January 25, 2020 7:17 AM

you used the "Microsoft RDLC Report Designer" extension from Marketplace?
Can run locally on your development machine build with VS 2019, using the "Microsoft.ReportingServices.ReportViewerControl.Winforms" Nuget package?

The InnerException seems to indicate that your are trying to load the report with older reporting components than the one it was created with:
"Details: The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition' which cannot be upgraded."

see
The report definition has an invalid target namespace rsInvalidReportDefinition

Monday, January 27, 2020 2:54 PM

The functionality for that moved to SSDT for versions up to VS 2019. This is a standalone VS shell that can integrate with existing VS instances. Starting with VS 2019 the tools were separated out and are now just extensions. For reports go to your extensions in VS and search for Microsoft Reporting Services Projects. Install this extension and all the report functionality you need will be added to VS. You can then test your report in the designer like you have in the past.

The exception you're getting is because you have an error in your RDLC. By using the designer you'll be able to avoid this issue.

Michael Taylor http://www.michaeltaylorp3.net

Monday, January 27, 2020 4:35 PM

There is no error in my RDLC.

This code has been running in production for 10 years.

Here's my concern.

Whataver is "not upgradeable" - if I go through all the reports and redo them, will it be now incompatible with what the users have THAT IS CURRENTLY WORKING?

I am concerned that upgrading will cause havoc with my client, as they are on SQL Server 2008.

A preferable solution would be to find out what the compatibility issue is and put the same version of whatever on my development box.

But as of right now, I don't know if its SSRS, or something on the desktops, or what. 

I'd rather live with false hope than with false despair.

Monday, January 27, 2020 5:16 PM

For the most part reporting services hasn't changed since SQL 2005. Even the underlying web service is still the same. The aforementioned extension works with all versions of SSRS from SQL Server 2008+. 

To ensure your report works with older versions of SQL then go to the reporting service project and then properties. Set Target Server to SQL Server 2008. The generated file should now be compatible with that version. At least that is how it used to work. It's been a while since I've had these types of issues but it works fine for our SQL 2012 servers using reports that were originally run against SQL 2008 R2 and upgraded when we switched to the new SQL version.

Michael Taylor http://www.michaeltaylorp3.net

Wednesday, February 5, 2020 11:02 AM

Hi Bryan Valencia,

You could have a try to install this component:Microsoft SQL Server 2017 Feature Pack for your visual studio 2017. 

To use rdlc in VS 2015, you could refer this answer, the extesion could be installed through VS2015 installer.

Hope it could help you.

Best Regards,

Dylan

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]