Deploy of a report with SSDT 2016 generates error

10
votes

I use VS2015 with SQL Server Data Tools; I have some Reporting Services (RDL) reports.

I want to deploy them to a Reporting Server with SQL Server 2014 installed.

In my report project I set the TargetServerVersion to "SQL Server 2008R2, 2012 or 2014", but the deploment process fails with an error similar to:

Report Definition invalid, because namespace .../2016/... invalid.
1
sql-serverdeploymentvisual-studio-2015sql-server-data-toolssql-server-2016
You might need to edit the code directly to change that to the previous namespace. I've had to do that before. <Report xmlns="schemas.microsoft.com/sqlserver/reporting/2008/01/…" xmlns:rd="schemas.microsoft.com/SQLServer/reporting/reportdesigner"> – Peter Schott
Simply opening a report with the newer SSDT changes the xmlns immediately and a new parameters section to the xml. Neither of which are likely to work on the production SSRS 2012 my current project is using. As per the question I also have the target version set to 2008r2-2014 which you'd think would do the job. Good thing I still have a VM with VS2013 and the older SSDT installed. – Tim Abell
Same problem: social.msdn.microsoft.com/Forums/sqlserver/en-US/… – Tim Abell
How did you deploy them? From this stackoverflow.com/q/39188874/10245 it seems that uploading the .rdl directly to ssrs won't work, but using the publish function or grabbing them from the bin folder will. – Tim Abell
@TimAbell The link you have provided should resolve the issue. We struggled with it for a while until we figured it out. We are currently using VS2015 to develop and deploying to SQL 2008 R2 using the SharePoint integration. We have a current project to upgrade to SQL 2014 and while I am not involved with the testing, my understanding is that there have not been any issues deploying. Let me know if you can`t make this work because we may need to look more closely on our side! – SMM

1 Answers

0
votes

It is solved. You "MUST" recompile your report project and immediately afterwards you can deploy your reports without any problem.