Reputation: 41861
I am wondering if someone can let me know which of the following steps I am doing wrong.
Things I have tried:
The SubReport control rdl:
<Subreport Name="Subreport1">
<ReportName>Sub1</ReportName>
<Parameters>
<Parameter Name="Likelihood">
<Value>10</Value>
</Parameter>
</Parameters>
<Top>2cm</Top>
<Left>2cm</Left>
<Height>7cm</Height>
<Width>7cm</Width>
<ZIndex>1</ZIndex>
<Style>
<Border>
<Style>None</Style>
</Border>
</Style>
</Subreport>
I have encountered many others with similar problems but I have not yet found a solution and would appreciate a point in the right direction.
Upvotes: 1
Views: 8355
Reputation: 1
I just ran into this same problem. Nothing I tried would fix the problem from within Visual Studio. I used the reporting services web portal to fix the shared data source. (Locate the report, click on the ... and select "MANAGE". Select "Data sources" from the side menu.) Once I confirmed the report was good, I downloaded the RDL for my local development.
Upvotes: 0
Reputation: 5711
I came across a forum on ActiveReports6 where an identical error was being encountered. In that case, the user (DeepSeaDave), "put a breakpoint in the subreport's DataSourceChanged() event. When [he called] the main report's Run() method, the DataSourceChanged event [fired] twice. The second time it [fired was] when the datasource [became] Nothing..."
I encountered the same problem (also involving a sub-report, and also involving Shared Data Sources), after I had copied/renamed an existing report (as well as the sub-report) as the template for a new one.
Solution:
By deleting the Data Source (report specific link to the Shared Datasource in the Project) in my parent report, and re-creating it (saving and closing down in between), the problem went away!
Upvotes: 3
Reputation: 41861
I realised I'm using a shared dataset on my subreport and others have encountered that issue. I deleted everything in my subreport, but it wasn't until I deleted that dataset that it would render without an error (i.e. a blank page as expected since I deleted everything). With this in mind I played with some settings and come up with the "solution" below.
One "solution" that "worked" for me was:
I wish I knew what caused this to start working again and I fully expect it will break again, but I do know that this is what I did and now it works so maybe its a cached reports issue?
This is NOT a solution, but I would be very interested to hear if it helps anyone else as maybe it will help us isolate the issue.
Upvotes: 0