The definition of this report is not valid or supported by this version of Reporting Services

[jguaring]

Hi, we're trying the extension for the first time and still figuring out how to us it.

We're having issues when creating a release and get the below 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.

Webservice URL - http://iwn-sqlbi-d01/reportserver/ReportService2010.asmx?wsdl

TFS - 2017
SQL Server version - 2012

[ygeelen-tb]

Seems like a similar issue to #3

[jguaring]

@ygeelen-tb
Above issues is somewhat similar, but in my case I do build the reports in TFS and Publish them

[jguaring]

I did notice that even though my build succeeded I get a warning that the project was not built

warning MSB4078: The project file "Accounting\Accounting.rptproj" is not supported by MSBuild and cannot be built.

[dschuermans]

@jguaring - You'll need to install the appropriate tools on your build server in order to build report projects.

[jguaring]

@dschuermans - we have SSDT for VS2015 installed on the build server is there a specific version that I should be installing?

[ygeelen-tb]

If you deploy to an environment with a different SQL Server version than your reports, then you need an extra build task to build your reports similar to this:
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.com "./MyProject.sln" /Project "./sources/MyProject.Reports/MyProject.Reports.rptproj" /Rebuild "$(BuildConfiguration)|$(BuildPlatform)"

[jguaring]

@ygeelen-tb - not sure what you mean by similar to this:
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.com "./MyProject.sln" /Project "./sources/MyProject.Reports/MyProject.Reports.rptproj" /Rebuild "$(BuildConfiguration)|$(BuildPlatform)"

So what I did on my release definition is added an agent task to build the solution using the MSBUILD task,

but im getting the below errors

1
2017-04-03T13:07:02.1213773Z ##[section]Starting: Build solution $(System.DefaultWorkingDirectory)/SSRS-Accounting-Reports/AccountingReports/Accounting/Accounting.rptproj

2
2017-04-03T13:07:04.9236575Z ##[command]"C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe" "C:\WBI-Agent_work\r1\a\SSRS-Accounting-Reports\AccountingReports\Accounting\Accounting.rptproj" /nologo /nr:false /dl:CentralLogger,"C:\WBI-Agent_work_tasks\MSBuild_c6c4c611-aa2e-4a33-b606-5eaba2196824\1.0.52\ps_modules\MSBuildHelpers\Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll";"RootDetailId=|SolutionDir=C:\WBI-Agent_work\r1\a\SSRS-Accounting-Reports\AccountingReports\Accounting"*ForwardingLogger,"C:\WBI-Agent_work_tasks\MSBuild_c6c4c611-aa2e-4a33-b606-5eaba2196824\1.0.52\ps_modules\MSBuildHelpers\Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll" /p:platform="Default" /p:configuration="Dev" /p:_MSDeployUserAgent="TFS_059f91dc-25c4-4966-9489-3beaabc88cb2_release_9_54_57_1"

3
2017-04-03T13:07:05.0246676Z Build started 4/3/2017 8:07:05 AM.

4
2017-04-03T13:07:05.0796731Z ##[error]C:\WBI-Agent_work\r1\a\SSRS-Accounting-Reports\AccountingReports\Accounting\Accounting.rptproj(2,1): Error MSB4041: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.

5
2017-04-03T13:07:05.0816733Z Project "C:\WBI-Agent_work\r1\a\SSRS-Accounting-Reports\AccountingReports\Accounting\Accounting.rptproj" on node 1 (default targets).

6
2017-04-03T13:07:05.0816733Z C:\WBI-Agent_work\r1\a\SSRS-Accounting-Reports\AccountingReports\Accounting\Accounting.rptproj(2,1): error MSB4041: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.

7
2017-04-03T13:07:05.0816733Z Done Building Project "C:\WBI-Agent_work\r1\a\SSRS-Accounting-Reports\AccountingReports\Accounting\Accounting.rptproj" (default targets) -- FAILED.

8
2017-04-03T13:07:05.0826734Z

9
2017-04-03T13:07:05.0826734Z Build FAILED.

10
2017-04-03T13:07:05.0826734Z

11
2017-04-03T13:07:05.0826734Z "C:\WBI-Agent_work\r1\a\SSRS-Accounting-Reports\AccountingReports\Accounting\Accounting.rptproj" (default target) (1) ->

12
2017-04-03T13:07:05.0826734Z C:\WBI-Agent_work\r1\a\SSRS-Accounting-Reports\AccountingReports\Accounting\Accounting.rptproj(2,1): error MSB4041: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.

13
2017-04-03T13:07:05.0826734Z

14
2017-04-03T13:07:05.0836735Z 0 Warning(s)

15
2017-04-03T13:07:05.0836735Z 1 Error(s)

16
2017-04-03T13:07:05.0836735Z

17
2017-04-03T13:07:05.0836735Z Time Elapsed 00:00:00.04

18
2017-04-03T13:07:05.4147066Z ##[error]Process 'msbuild.exe' exited with code '1'.

19
2017-04-03T13:07:05.4807132Z ##[section]Finishing: Build solution $(System.DefaultWorkingDirectory)/SSRS-Accounting-Reports/AccountingReports/Accounting/Accounting.rptproj

20

[ygeelen-tb]

MsBuild is the problem, it doesn't recognize rptproj projects (even when SSDT is installed).
What I meant is to use a Command Line task (in your build definition preferably) that calls the devenv.com application:

• Specify C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.com in the Tool parameter
• Specify "./MyProject.sln" /Project "./sources/MyProject.Reports/MyProject.Reports.rptproj" /Rebuild "$(BuildConfiguration)|$(BuildPlatform)" in the Arguments parameter

[jguaring]

@ygeelen-tb - build and release worked.

Thanks for your assistance. Great Tool

[ygeelen-tb]

Great! Thank you, we should have time to write more documentation very soon and this will be included.
It would be nice if you would leave a review here: https://marketplace.visualstudio.com/items?itemName=tobania.SqlReportingServices

[jguaring]

@ygeelen-tb
we just noticed that when do the release that the build server is not getting the latest version of the source code, any idea why?

see below- parms passed to the command line task

BuildTool - C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.com

BuildArgument - "C:\Workspaces_WBI\SSRS\Trunk\Call Log Report\CallLogReport.sln" /Project "C:\Workspaces_WBI\SSRS\Trunk\Call Log Report\Call Log Report\CallLogReport.rptproj" /Rebuild "$(BuildConfiguration)|$(BuildPlatform)"

[jguaring]

@ygeelen-tb
another thing that we noticed is that when we include data sources and data set on the release - reports are not associating the datasources and dataset

[ygeelen-tb]

@jguaring
For the first issue: you could try cleaning the sourcesdirectory on build (there's an option for that on one of the build tabs). Are you sure you triggered a new build before executing the release?
This should not be related to the extension though.

For the second issue we implemented a new feature. Please try checking the "Update Data Source" checkbox.

[jguaring]

@ygeelen-tb
this is what I specified as per your previous post

•C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.com in the Tool parameter
•"C:\Workspaces_WBI\SSRS\Trunk\Call Log Report\CallLogReport.sln" /Project "C:\Workspaces_WBI\SSRS\Trunk\Call Log Report\Call Log Report\CallLogReport.rptproj" /Rebuild "$(BuildConfiguration)|$(BuildPlatform)" in the Arguments parameter

its the second bullet that does not get the latest version.

[ygeelen-tb]

@jguaring The command only builds the code, it doesn't featch the latest version from source control.
You need a Get Sources build task before this build task I think.

[jguaring]

@ygeelen-tb
do I need to reinstall the extension to get the new feature "Update Data Sources"?

[ygeelen-tb]

Normally not. Only if an extension changes to a new major version, you need to switch to it using a dropdown at the top right of the build/release task in your definition.
So you should see the field in the task. If not please provide a screenshot if possible.

[jguaring]

@ygeelen-tb
I had to reinstall as the option was not available.

does this option apply to both shared Data sources and Datasets?

I tried using the option but got an error below

2017-05-04T14:31:27.3443317Z Updating the DataSources of the report CallLogReport...

213
2017-05-04T14:31:27.3443317Z

214
2017-05-04T14:31:27.3443317Z

215
2017-05-04T14:31:27.5474594Z ##[error]Microsoft.PowerShell.Commands.WriteErrorException: The operation you are attempting on item '/Data Sources/DS_GISDATAWAREHOUSE' is not allowed for this item type. ---> Microsoft.ReportingServices.Diagnostics.Utilities.WrongItemTypeException: The operation you are attempting on item '/Data Sources/DS_GISDATAWAREHOUSE' is not allowed for this item type.

216
2017-05-04T14:31:27.5787247Z ##[error]PowerShell script completed with 1 errors.

[anton-kirschhock]

@jguaring Just for our information, did you use VSTS or a TFS instance?

[jguaring]

@muziekklas
I used TFS

[NullReferenceError]

Following up with this issue, we have an older SQL report server version (2012) and receive this error. It seems that the reports still get push when this happens. Is it possible to add an option in the Advanced steps to ignore this particular error?

[NullReferenceError]

#33

Let me know if any of you think this PR might fix this issue, or if any changes should be done to it.

[anton-kirschhock]

Well this issue was related to a wrong configuration in VSTS of our product. Could you send us a screenshot (you can hide out passwords and domains ect with some creative paint-skills) of your VSTS configuration?

[NullReferenceError]

This is actually in TFS 2017, moving older SQL reports (created in VS 2008) to a SQL reports server (SQL server 2012, I think.) which configuration screen are you looking for? For the tasks I have the required fields, and service account credentials.

…

On Nov 3, 2017, at 2:07 PM, AntonK ***@***.***> wrote: Well this issue was related to a wrong configuration in VSTS of our product. Could you send us a screenshot (you can hide out passwords and domains ect with some creative paint-skills) of your VSTS configuration? ― You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[anton-kirschhock]

More specific the URI of the service

[NullReferenceError]

During the build phase I use devenv.com to build the solution. Currently using an older version of VS to run the build, I receive the error with any version it seems.

In the release, using the reportservice2010 URL:

[ghost]

Were there any plans to put PR #33 into master? I reviewed it and it looks to be the fix that I need to be able to use this

[NullReferenceError]

@kbrashears I think I've found the actual issue with that error. Verify that you are not trying to send any other files as input to the SQL Reports server.

In my case, I was attempting to upload unsupported files to the report server endpoint. Make sure your "Local Report Path" parameter is checking for the RDL file type

IE:
Instead of this:
$(System.DefaultWorkingDirectory)/SQL Reports Build Test/drop/VS2012ReportTest/VS2012ReportTest/bin/Debug/

Use this:
$(System.DefaultWorkingDirectory)/SQL Reports Build Test/drop/VS2012ReportTest/VS2012ReportTest/bin/Debug/*.rdl

Edit:

I've also updated the PR with a question on if filtering filetypes as input would be a better solution.