Steve MacWilliams
asked on
SSRS using ReportViewer not rendering if it has a sub report on it
I have a Parent report and a child report. Each individually function correctly when 2 parameters are passed to it. Unfortunately when I put the child report (subreport) nested or not nested on the parent it doesn't render. Any ideas?
I have even put a plain form as the subreport... nothing but a header and it still will NOT render the parent.
Please help
I have even put a plain form as the subreport... nothing but a header and it still will NOT render the parent.
Please help
What is it that is not rendering? The title seems to say that the report, both parent & subreport, doesn't render at all when the subreport is present. In your question, however, you seem to possibly be saying that the subreport doesn't render when added to the parent report. The phrase "it doesn't render" at the end of the question can be read in more than one way, depending on what "it" represents. Please clarify.
Also - where is it not rendering? Does it render as expected in BIDS/SSDT and ReportBuilder? Or does it not render when viewed within a report viewer that is embedded into a WinForms or a Web application?
If the issue in on the report viewer, try exporting the report (Save As icon). I have seen instances where the body may not render properly on screen (some UI elements may be entirely missing), but when exported to PDF or Excel, everything is exported properly - indicating an environmental issue.
Finally, do you have data being pulled for the child report (you can verify if the query for the appropriate data set is fired or not using Profiler/Extended Events)?
If the issue in on the report viewer, try exporting the report (Save As icon). I have seen instances where the body may not render properly on screen (some UI elements may be entirely missing), but when exported to PDF or Excel, everything is exported properly - indicating an environmental issue.
Finally, do you have data being pulled for the child report (you can verify if the query for the appropriate data set is fired or not using Profiler/Extended Events)?
ASKER
Thank you. Let me clarify.
Within Visual Studio where I develop the report and sub-report the both render and they work perfect in BIDS/SSDT.
However when this is in production. NIETHER the report NOR the sub-report render. It is accessed/viewed via a url something like .../reports/ReportViewer.a spx?rptNam e=ReportNa me
In Production:
I have troubleshot by removing the sub-report from the parent and then the parent will render.
I then also create a separate 'link' to the sub report and it too will also render.
I am going to reinstall SSMS... I couldn't find profiler
Within Visual Studio where I develop the report and sub-report the both render and they work perfect in BIDS/SSDT.
However when this is in production. NIETHER the report NOR the sub-report render. It is accessed/viewed via a url something like .../reports/ReportViewer.a
In Production:
I have troubleshot by removing the sub-report from the parent and then the parent will render.
I then also create a separate 'link' to the sub report and it too will also render.
I am going to reinstall SSMS... I couldn't find profiler
ASKER
Just as a FYI...
As another part of testing I recreated from scratch and in production it didn't render.
As another part of testing I recreated from scratch and in production it didn't render.
Do you have a development server, or are you only testing in production? Do you have Windows admin access to a report server on which the problem is occurring, so that you can look at the Report Server logfiles? Do you have SELECT access for tables and views in the Report Server temp DB?
Are the subreport parameters simple ones, no available value lists, no defaults (or at least no defaults that are actually used)? Do the values supplied match the parameter data types?
Are the subreport parameters simple ones, no available value lists, no defaults (or at least no defaults that are actually used)? Do the values supplied match the parameter data types?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Megan
Do you have a development server, or are you only testing in production?
Only testing in production
Do you have Windows admin access to a report server on which the problem is occurring, so that you can look at the Report Server logfiles?
No errors in log
Do you have SELECT access for tables and views in the Report Server temp DB?
Please explain, but yes I can query those tables
Are the subreport parameters simple ones, no available value lists, no defaults (or at least no defaults that are actually used)?
Yes the are simple. No default values, but tried both ways
Do the values supplied match the parameter data types?
Yes
Do you have a development server, or are you only testing in production?
Only testing in production
Do you have Windows admin access to a report server on which the problem is occurring, so that you can look at the Report Server logfiles?
No errors in log
Do you have SELECT access for tables and views in the Report Server temp DB?
Please explain, but yes I can query those tables
Are the subreport parameters simple ones, no available value lists, no defaults (or at least no defaults that are actually used)?
Yes the are simple. No default values, but tried both ways
Do the values supplied match the parameter data types?
Yes
ASKER
Nakul
A couple of things - the report renders fine in Visual Studio. Can you deploy it to your development SSRS server and render from there using the Report Manager (typically, http://<ServerName>/Reports)?
I can access the Report Manager. At a previous job I was able to click on the report and it would work. In this instance, I get the following error:
The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationErro r)
Log on failed. Ensure the user name and password are correct. (rsLogonFailed)
For more information about this error navigate to the report server on the local server machine, or enable remote errors
On the sub-report, can you try creating an extremely simple sub-report that only has maybe a textbox with some static text only (no header, footer, tablix or any other component)? That way, we can confirm that there are no issues with respect to sub-report display configuration.
I had already tried this same non-rendering results
A couple of things - the report renders fine in Visual Studio. Can you deploy it to your development SSRS server and render from there using the Report Manager (typically, http://<ServerName>/Reports)?
I can access the Report Manager. At a previous job I was able to click on the report and it would work. In this instance, I get the following error:
The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationErro
Log on failed. Ensure the user name and password are correct. (rsLogonFailed)
For more information about this error navigate to the report server on the local server machine, or enable remote errors
On the sub-report, can you try creating an extremely simple sub-report that only has maybe a textbox with some static text only (no header, footer, tablix or any other component)? That way, we can confirm that there are no issues with respect to sub-report display configuration.
I had already tried this same non-rendering results
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
My solution resolved the problem.