Both Leonard and also I talk about SSRS and also Power BI reporting every one of the time. We also publish weekly tips and also tricks around reporting on the Enhansoft blog website and distribute a monthly newsletter complete of tips. By the way, if you are not signed up for the newsletter, you have to be! One of the things that drives us nuts, though, is when we get the complying with error message after uploading a new SSRS report (RDL) to a SSRS server aka the SCCM Reporting Services Point: The interpretation of this report is not valid or sustained by this version of Reporting Services. The report interpretation may have been created through a later version of Reporting Services, or contain content that is not well-formed or not valid based upon Reporting Services schemas. Details: The report definition has an invalid tarobtain nameroom ‘http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition’ which cannot be upgraded. (rsInvalidReportDefinition)

*

Now, after seeing this error message sufficient times, we recognize how to settle the difficulty. Heck, Leonard even composed around somepoint similar in his blog short article, Clean and Build – How It Saves Me Money. The trouble is, as soon as we went to tell someone else just how to fix it, up until now, we didn’t have actually a blog write-up that described the process, so via today’s short article I deserve to cross that “to-do” item off my list.

You are watching: The definition of the report is invalid

Definition of this Report is Not Valid

When execute you obtain this error? The answer is really simple. You uppack a RDL with a version that isn’t supported by your SSRS server. For example, a SSRS 2016 RDL version is uploaded to a SSRS 2012 server. You deserve to see the variation incompatibility information in the error message text itself.

How Does this Happen?

Tbelow are two methods. The initially one entails someone else (typically external of your organization) developing a RDL, posting it to their blog site and also then you downfill it. It’s as soon as you upfill the report to SSRS that you view the error message. If you are not familiar via exactly how to upfill a RDL, make sure to check out my blog article, How-To Upfill a SSRS Report and Change its Data Source.

The second way entails making use of either Visual Studio (VS) or Report Builder (RB). When you manually uppack the RDL (report) to SSRS, you check out the, “Definition of this Report is Not Valid,” error message. Why is it vital that I said, “manually,” uppack the RDL? If you publish the report directly from VS or RB, the variation of SSRS is normally detected immediately and also any kind of adjustments are made in the background. In this situation, you must never before watch the error.

Definition of this Report is Not Valid – Solution

There are no tricks to fixing this difficulty. All you must do is set the RDL to the appropriate version that’s supported by your SSRS server. Tbelow is one caveat, but, to this solve. The original RDL variation is ALWAYS stored in the task directory as the HIGHEST RDL variation sustained by VS or RB. Whereas the proper (aka downgraded) variation is found within the “BIN” project catalog.

Note: When I say the “BIN” task brochure, it deserve to be BIN or BINDebug or BINRelease. Wright here it is uncovered counts on many type of things, yet it must be apparent to you in which folder the newly produced RDL is stored.

RDL 2016

*

Here’s an instance of a RDL opened in XML Notepad. Notice that the schema is listed as 2016. This is a RDL from our task magazine.

RDL 2008

*

The same RDL is opened in XML Notepad, yet alert that the schema is noted as 2008. This is the SAME report as the one in the previous example. It was downgraded to 2008 and also it’s discovered within the “BIN” project catalog.

How to Downgrade the RDL’s Version

*

In the Systems Explorer window, right-click the project (in this instance it is referred to as Microsoft Office) and choose Properties.

*

In the TargetServerVersion drop dvery own, select the proper variation. In my instance it’s SQL Server 2008 (see the purple arrow). Once the appropriate variation is selected, click the OK button. In this instance, the “BIN” project brochure is called binDebug (green arrow).

See more: Why Is It Important To Work To Delete Cyberbullying ? Why It'S Important To Prevent Cyberbullying

Wait, Why Isn’t the Solution to Never before Manually Uppack a RDL from VS or RB?

Well, tbelow is a lengthy answer and also a brief answer. Here’s the brief answer. When you are functioning on a project, you usually have actually a number of reports in various says. If you are careful, you need to publish one report at a time from VS or RB. The key word in that last sentence is “careful.” Why? I seem to upfill all the reports, regardmuch less of their state, or none of them. This mostly occurs out of halittle bit bereason I want to prevent overwriting reports I didn’t mean to overcompose. In this situation, I constantly upload my reports manually. As the saying goes, YMMV.

Definition of this Report is Not Valid – Summary

As a report writer it is important to understand how to “downgrade” your report in order to assistance all versions of SSRS that you intend it to support. This is a super-straightforward solution that permits folks with different SSRS versions to usage your reports. If you are a customer of reports that you “find” on the internet, then you may have to recognize just how to downgrade RDLs to enhance your SSRS server. Don’t let this error message, “Definition of this Report is Not Valid,” stand also in your way!

Let us know just how helpful this blog article is to you. As always, if you have inquiries, please feel free to touch base via