PublishTask::Validate Does not deploy?

Topics: Developer Forum, User Forum
May 14, 2009 at 11:34 AM
Edited May 14, 2009 at 11:36 AM

Hi -

I need some help to get RSBuild working. Has any one used RSBuild?

Requirement -
The project has over 30 reports that need to be deployed each time a build goes in. It is very cumbersome deploying the reports by uploading them one at a time using ReportManager. RSBuild seems very promising but setting it up seems quite a job!

Progress so far - 
I have set up the RSBuild App Config... Sample below...
<?xml version="1.0" encoding="utf-8" ?>



<Global Name="ReportServer">localhost</Global>

<Global Name="ReportServerPath">reports/Pages/Folder.aspx</Global>

<Global Name="CollapsedHeight">0.5in</Global>



<ReportServer Name="myReportServer" Protocol="http" Host="${ReportServer}" Path="${ReportServerPath}" Timeout="30" />



<DataSource Name="TestDb" Publish="true" Overwrite="true" TargetFolder="TestFolder" ReportServer="myReportServer">

<ConnectionString>Data Source=VSS07; Initial Catalog=Rump</ConnectionString>








<!-- TestReport -->

<ReportGroup Name="Test" DataSourceName="TestDb" TargetFolder="TestFolder"

ReportServer="myReportServer" CacheTime="10080">

<Report Name="TestReport">






So i run the RSBuild.exe suppling the above config from the command prompt.

Problem -
I end up with following ...

[Settings]: Loading RSBuild settings from 'C:\Documents and Settings\!3rdxxxx\
RSBuild 1.1.1
(C)2005 Microsoft Corporation
Microsoft Corporation
Database Installation
Reports Installation
Validating reporting service: http://localhost/Reports/

Help -
Validate - ? I have validated the link is correct!
Still it says Validate, neither the report nor the Datasource are created.  ny inputs on how to progress?


May 15, 2009 at 3:32 AM

You have hit a bug in the reporting of report server url validation issues. I'll try to release a bug fix today.

May 21, 2009 at 2:49 PM
Edited May 21, 2009 at 2:50 PM

The report server url validation issue should be reported now by the latest release. And the actual problem in your config file has already been tackled on