I have an SSRS report with two subreports that had been working fine. Recently I added some additional table sections to the report and I started seeing an issue when the report was displayed in the interactive viewer. The data is fine but the formatting on the last two table sections does not appear in the viewer.
The formatting actually stops working half way through the next to last report. However, when I print the report (or export to a PDF), all of the formatting is there and the report prints fine.
I have tried splitting the report into more subreports, running with different data and it still does not display correctly in the interactive viewer. The report and subreports do have a lot of formatting and table sections and I am wondering if the RDL files are too big to store in memory or if they even do get stored in memory.
The RDL file sizes are 61 kB for the main report and 2612 kB and 2608 kB respectively for the subreports. Is there a size limitation on the RDL files? Any ideas?
I have found a work around for my problem. If I render my report directly to a PDF, then the report will not display in the interactive viewer, but only as a PDF which displays correctly. This is done by adding "&rs:Format=PDF" to my URL when I call it from my C# program that allows the user to input the parameters. Then the user can print the report and never see the missing formatting in the interactive viewer. This works for my, however, I would still like to know if there is another answer that allows it to view correctly in the interactive viewer or if I have surpassed some memory limitations.
If you split the report into its component parts does it display ok? If as you say you have recently added some new sections/Sub reports to it if you remove them does it look ok again.
You have probably got some strange overlapping happening, in the report designer when the report complies check the warning tag to see if it gives you any clues
Related
I have an SSRS (2012) .rdl main report that calls a subreport. This subreport is displaying a column which is a very long string.
If I call the subreport directly, this column displays the entirety of the text.
If I call the main report (which subsequently calls, among others, the afforementioned subreport), the preview in the SSRS page also shows the entire text as it's supposed to, but when I export it to .pdf or excel, all the text after the first line is missing (the first line of text is shown, and the rest of the space where the text should is just blank).
This issue does not occur when calling the subreport directly, but it does when I call the main report.
Furthermore, I have 2 environments with these reports installed, Production and Development, and the issue does not occur in Development, but it does in Production, and only if I call the main report!
I have already checked all the .rdl, .rsd and .dll files installed on both environments, and all of them are exact matches. The text itself, is the same for this column on both databases (I think). I have confirmed that "Page Width >= Body Width + Left Margin + Right Margin", also I tried on the Report Properties changing the margins from cm to Inches and back to cm to get the margins rounded up by 4 or 5 decimal digits, none of it worked.
I have looked extensively for problems similar to mine, but none of them were properly answered. I have no idea what is causing this, but considering that the subreport works just fine, that the same main report works fine in Development, and that even on the preview of the Production environment all of the text is shown, I suspect it may have something to do with the exporting process. The browser used is always the same in all scenarios, IE11. The PDF is Acrobat Reader DC.
Any help is deeply appreciated.
I have created a report using Birt 3.7.2 The report behaves exactly how I want when using the web viewer and even when exporting to PDF from the web viewer. However When running the report direct to PDF all pages always show as page 1, causing conditional formatting to break.
Why would the page numbers work correctly to the viewer but not direct to PDF. Is there a workaround. The report is called from our application and attached to an email. As such we do need to be able to run it directly to PDF.
The page numbers are on the report body rather than in the Master Page.
I did see this was a bug in 2.6.1 but it was resolved in 2.6.2.
I have an application developed with Vb.Net 2003 and using Crystal Reports 11 used to preview many statistical reports.
I always preview any report successfully, but when exporting some of the reports (not all) into PDF using the built-in export functionality in the report viewer control, the application freezes forever.
So, I need to know if there is any report object (textobject, Picture, Chart, line, box, etc..) that might not be able to be exported into PDF, and I think this type of object is only found in some of my reports and that's why I face this problem only with some of the reports and not all of them.
The most common reason this happens is that not all the variables you use in the report are filled. So make sure of that. Otherwise you should get an error on the object you use. Do you get an error on exporting?
I have a RDLC report and I am displaying it on the Report Viewer Control in my front end application. I get the report perfectly and theres no problem in it.
But the problem arises when I try to export the report to a PDF (using available option - basically the inbuilt option).
I get the report in 3 pages whereas my client wants it to be in a single page. I am not able to figure out the reason for it as in my report viewer I see only one page but in a PDF there are 3 pages. I have only four columns with no data, still they are breaking up into multiple pages. 2 columns on 1st page 2 on second page. Not real sure what happened to the 3rd page. Somebody recommended changing the paper size of the default printer but I didn't think is was worth trying.
Can something be done abt it so that I can control the size of the report???
This can be a real PITA but there are several things you can do to get you there in BIDS.
To see what it will look like as a pdf use the "Print Layout" button on the preview mode toolbar.
Goto the report properties and set the orientation and paper size as you need them.
Remember the margins in the report properties to make your report display area smaller. I generally set these smaller than the defaults.
Go back to you report items and make sure they are smaller than (pagesize - margins)
This should help.
you can try setting InteractiveHeight=0 , I know that at least works for the MHTML output, not sure about PDF, but it might lead you in the right direction
I'm working on my first significant Sql Reporting Services project and am having problems with paging. Most of the reports are already working.
What is happening is that I"m getting different numbers and locations of page breaks between Web Reportviewer, PDF and Word documents. The word is the closest, but none of the three are really correct.
I've looked for the for the obvious like extra paging and making sure the report does not go outside of the left or right margins. My problem is that I'm not sure how to go about troubleshooting reports that pages that do not break in the correct location.
Does anyone have a suggestion where to start?
I'm using VS2008, SQL2008 DE on Vista Dev box.
This isn't really a problem - the different renderers are rendering the report appropriately for their output. The web viewer is optimised for screen-based reading and generally allows more content per page than the PDF viewer does as the PDF viewer is constrained by the paper size that it formats to. Thus you get more pages when rendering for PDF than web; however, the content of the report is exactly the same.
The best illustration of this is the Excel renderer - the Excel renderer renders the entire report onto a single worksheet in most cases (for reports with grouping and page breaks set on the group footer it will render each group on its own worksheet). You wouldn't want the Excel renderer to artificially create worksheets to try to paginate your report. It does the appropriate thing which is to include all the data in one big worksheet even though that may be logically thought of as one big "page".
The web renderer page length is determined by the InteractiveHeight attribute of the report (in the InteractiveSize property in the Properties pane for the report) but the interactive height is an approximation rather than a fixed page break setting and your page breaks may still not conform to the PDF version even though the InteractiveHeight is set to the same length as your target page length.