{"id":58,"date":"2016-01-22T14:58:54","date_gmt":"2016-01-22T19:58:54","guid":{"rendered":"https:\/\/www.sqlskills.com\/blogs\/tim\/?p=58"},"modified":"2016-01-22T15:06:01","modified_gmt":"2016-01-22T20:06:01","slug":"issue-publishing-to-ssrs-2012-with-ssdt-2015","status":"publish","type":"post","link":"https:\/\/www.sqlskills.com\/blogs\/tim\/issue-publishing-to-ssrs-2012-with-ssdt-2015\/","title":{"rendered":"Issue publishing to SSRS 2012 with SSDT 2015"},"content":{"rendered":"<p>I recently was helping a client who was trying to use SQL Server Data Tools 2015 to update and generate reports that would be deployed to SQL Server Reporting Services 2012. When trying to deploy the report, the client would get the following error:<\/p>\n<p>\u201c[rsInvalidReportDefinition] 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.\u201d<\/p>\n<p>I knew that SSDT 2015 should be backwards compatible and able to work with multiple versions of SQL Server products, so I had to do a little research to figure out what exactly needed to be changed in order to publish a report to SSRS 2012.<\/p>\n<p>In my lab, I created a new project named GetDatabases. This project was a basic report that would get query a system table. The first thing I tried to change in the project was the TargetServerVersion located under the project properties.<\/p>\n<p><a href=\"https:\/\/www.sqlskills.com\/blogs\/tim\/wp-content\/uploads\/2016\/01\/clip_image0011.png\"><img decoding=\"async\" loading=\"lazy\" style=\"display: inline; border: 0px;\" title=\"clip_image001\" src=\"https:\/\/www.sqlskills.com\/blogs\/tim\/wp-content\/uploads\/2016\/01\/clip_image001_thumb1.png\" alt=\"clip_image001\" width=\"403\" height=\"278\" border=\"0\" \/><\/a><\/p>\n<p><a href=\"https:\/\/www.sqlskills.com\/blogs\/tim\/wp-content\/uploads\/2016\/01\/clip_image0031.jpg\"><img decoding=\"async\" loading=\"lazy\" style=\"display: inline; border: 0px;\" title=\"clip_image003\" src=\"https:\/\/www.sqlskills.com\/blogs\/tim\/wp-content\/uploads\/2016\/01\/clip_image003_thumb1.jpg\" alt=\"clip_image003\" width=\"403\" height=\"230\" border=\"0\" \/><\/a><\/p>\n<p>I updated the TargetServerVersion to \u201cSQL Server 2008 R2, 2012, or 2014\u201d, the default in was \u201cSQL Server 2016\u201d. I also updated the TargetServerURL to my development server running SSRS 2012. I made these changes to both the release and debug configuration options.<\/p>\n<p>After making these changes, I was still unable to deploy the report. After a bit more research, I found a location to change the default deployment server version of the Business Intelligence Designer. This is located under \u2018Tools and then Options\u2019. The default was set to version 13.0, once I changed the version to 11.0 to match the server I was deploying to, I was able to successfully deploy my report to SSRS 2012.<\/p>\n<p><a href=\"https:\/\/www.sqlskills.com\/blogs\/tim\/wp-content\/uploads\/2016\/01\/clip_image0041.png\"><img decoding=\"async\" loading=\"lazy\" style=\"display: inline; border: 0px;\" title=\"clip_image004\" src=\"https:\/\/www.sqlskills.com\/blogs\/tim\/wp-content\/uploads\/2016\/01\/clip_image004_thumb1.png\" alt=\"clip_image004\" width=\"407\" height=\"239\" border=\"0\" \/><\/a><\/p>\n<p>It seems odd to me that I would have to change the overall behavior of SSDT instead of just the properties of my project, however I confirmed with my client that they couldn\u2019t deploy until they modified the default deployment server version.<\/p>\n<p>I hope this helps if you are having similar issues.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I recently was helping a client who was trying to use SQL Server Data Tools 2015 to update and generate reports that would be deployed to SQL Server Reporting Services 2012. When trying to deploy the report, the client would get the following error: \u201c[rsInvalidReportDefinition] The definition of this report is not valid or supported [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[13],"tags":[16,10,15,14,17],"_links":{"self":[{"href":"https:\/\/www.sqlskills.com\/blogs\/tim\/wp-json\/wp\/v2\/posts\/58"}],"collection":[{"href":"https:\/\/www.sqlskills.com\/blogs\/tim\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sqlskills.com\/blogs\/tim\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/tim\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/tim\/wp-json\/wp\/v2\/comments?post=58"}],"version-history":[{"count":0,"href":"https:\/\/www.sqlskills.com\/blogs\/tim\/wp-json\/wp\/v2\/posts\/58\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.sqlskills.com\/blogs\/tim\/wp-json\/wp\/v2\/media?parent=58"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/tim\/wp-json\/wp\/v2\/categories?post=58"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/tim\/wp-json\/wp\/v2\/tags?post=58"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}