Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Did you verify the DataSourceReference element in your RDL? It needs the path to the reporting server. </p> <blockquote> <p>The DataSourceReference element can contain a full folder path (for example, /SampleReports/AdventureWorks) or a relative path (for example, AdventureWorks). Relative paths start in the same folder as the report. The shared data source must be on the same server as the report.</p> </blockquote> <p>Verify the DataSourceID too. Take a look at the <a href="https://stackoverflow.com/questions/1797180/using-a-shared-data-source-for-dynamically-generated-and-deployed-reports">answer on this question</a>. It looks like it might be the same problem you are having.</p> <p>If you are using an RDLC you could also set the datasource of your report manually using <a href="http://msdn.microsoft.com/en-us/library/ms254370.aspx" rel="nofollow noreferrer">ReportDataSource</a>. "GetMyData" in the example below would implement IEnumerable or IDataSource.</p> <pre><code>ReportDataSource reportDataSource = new ReportDataSource("MyDataName", GetMyData(startAt, endAt)); ReportViewer1.LocalReport.DataSources.Add(reportDataSource); ReportViewer1.LocalReport.ReportPath = Server.MapPath("~/Reporting/MyReport.rdlc"); ReportParameterCollection col = new ReportParameterCollection(); ReportParameter startAtParam = new ReportParameter("StartAt", startAt.ToString("MMM, dd yyyy")); col.Add(startAtParam); ReportParameter endAtParam = new ReportParameter("EndAt", endAt.ToString("MMM, dd yyyy")); col.Add(endAtParam); ReportViewer1.LocalReport.SetParameters(col); </code></pre> <p>If you are converting an RDL to an RDLC you can <a href="http://msdn.microsoft.com/en-us/library/ms252109%28v=vs.90%29.aspx" rel="nofollow noreferrer">follow the steps here</a>. Note that you need to re-create data source and query information. Also, the XML schema definition is different between 2005 and 2008.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload