Error while opening a custom report(.rdl) in SSMS 2017, created in VS 2019

  • I'm experiencing difficulties opening a custom report created in Visual Studio 2019 using Microsoft Reporting Services within SQL Server Management Studio (SSMS).

    The error message I'm encountering is as follows:

    An error occurred during local report processing. (Microsoft.ReportViewer.WinForms)
    The definition of the report 'Main Report' is invalid. (Microsoft.ReportViewer.Common)
    The report definition is not valid. Details: The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition' which cannot be upgraded. (Microsoft.ReportViewer.Common)

    My environment consists of SQL Server 2017 and Visual Studio 2019. All components (report server, SQL Server, and Visual Studio) are on the same PC. Despite trying the above solutions, the issue persists. Has anyone encountered a similar problem? If so, could you please share your insights or suggest a possible solution? I appreciate any help or guidance on resolving this issue.

    Note: I am able to open the report when the .rdl file is copied and added to the same server in SSMS 2017 on a different PC.

    I've attempted several solutions stated in the following links

    https://stackoverflow.com/questions/36272514/the-report-definition-has-an-invalid-target-namespace-rsinvalidreportdefinition

    https://forums.ivanti.com/s/article/Receiving-Invalid-target-namespace-error-when-uploading-a-Report-to-BIDS?language=en_US#:~:text=within%20the%20report.-,Resolution,then%20imported%20into%202008%20R2

    Removing the <ReportSections> <ReportParametersLayout> and <ReportSection> tags from the report.

    Setting the TargetServerVersion(SQL Server 2016 or later).

    Trying to replace the Report Viewer 10.0.0.0 version with the appropriate 15.0.0.0 version, but the references are not present in my project.

    Using the report DLL from the bin folder.

  • To be completely honest with you, I've never tried to open an RDL in SSMS and didn't even know you could... I don't see the point? Is there a reason you need to open it in SSMS? My approach is to create and preview the report in Visual Studio and then deploy it to SSRS for consuming. I can't think of a use case where I'd want to view the report in SSMS. BUT it could just be that I have not had that scenario come along...

    But, to address the question, have you installed SSDT in your copy of SSMS 2017? My advice is not to modify the rdl once it is generated by visual studio, especially if it works on a different computer. If it doesn't work on computer A and does on computer B, then something is installed differently between the two computers. Look at the installed software (including patches) and get them both to the same state.

    The above is all just my opinion on what you should do. 
    As with all advice you find on a random internet forum - you shouldn't blindly follow it.  Always test on a test server to see if there is negative side effects before making changes to live!
    I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.

  • For Visual Studio 2019, you will also need to download the extensions for Microsoft Reporting Services Projects and Microsoft RDLC Report Designer.

    =======================================================================

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply