This is an experience that can drive you crazy. You have designed a report to run with the RTC. The preview looks nice and exactly how you expect it. Then you decide to print the report on paper or export it as PDF. And unexpectedly every other page is blank! Headers are printed, but there is no data on it. And the total number of pages is doubled.
The reason for this behavior is almost always caused by the body of the report being to wide for the page. The maximum width of the body should be the physical page width minus the margins.
Or to put it exactly: Body Width <= Page Width – (Left Margin + Right Margin)
To set the physical page size in Visual Studio, choose Report –> Report Properties. On the tab Layout you can set the correct values.
Based on these settings you can calculate the maximum width of the body, also called the Usable Area. In this example the maximum width of the body is 21cm – (1,5cm + 0cm) = 19,5cm. The actual size of the body can be set via the properties of the body:
It is important to keep in mind the concept of Usable Area. The body width should not exceed the usable area. If it exceeds the usable area during rendering, it will break the page onto a new page. For detailed information about pagination with Reporting Services, see the next MSDN article: http://msdn.microsoft.com/en-us/library/bb677374(v=sql.100).aspx
Hi,
Great article!!! Thank you very much! We waste more than 2 hours to find out with that bloody persistent blank pages.
Thank you. This article really help us.
With best regards,
Shuha.
Wow .. thanks for this article. I also wasted two hours and lost a bit of sanity with this problem.
Best wishes,
Chris
Thank you very much…. 🙂 It solved my problem
Thank you very much!!!
I wasted hours to solve this problem.
Thanks and Regards,
Robert
Hi,
Gr8 Artical! It really helped
Thanks.
Regards,
Dnyaneshwar
I was almost in a straight jacket. It solved my problem. In these cases you long for the good old classic reports.
Tnx,
HDU
Thank you very much. This really helped; it solved my issue which I had spent 4.5 hours on.
Regards,
M John
U saved my day!! Thanks!!
The standard report 206 Sales Invoice on the W1 database n(NAV 2013 R2) has the second page blank.
Thanks for the information, but this is not working for me in RTC 2013. Here are my parameters:
Page width = 8.27 in
Left metrgin = 0.67476 in
Right margin = 0.41667 in
so the body width = 8.27 – (.67476 + .41667) = 7.17857 in
I set the body width = 7 in, even them my report goes to second page with blank body. Is there any other parameters I need to check. Thanks.
Body width was correct. Actually system is taking space for conditional hidden lines in body section. I removed unwanted hidden lines and now it is printing it in one page. Thanks.
I am also having this problem, but none of the other solutions that I have seen on various websites seem to be the fix for me. The number one solution seems to be to make sure that your body is narrower than your page width. My body is 9.08333 inches wide and 1.3 inches high. My report is 11 inches wide by 8.5 inches high with a left margin of 0.25 inches and a right margin of 0.25 inches yet I get a blank page after every real page with data when I go to print the report or make it into a pdf. I even tried removing my header and footer to see if something in them was causing the problem, but I still get the extra page. If I try portrait mode so that my page is 8.5 inches wide then I get one page with the table parts that don’t fit on the first page, but then I still get a blank page. I have turned on and off the break between groups and the keep together option on groups and none of this appears to make a difference either.
It doesn’t work for me. I am using the Visual Studio 2013. I just do a test report. I print small data. the report size is 17cm width with no header and footer. it keep have a blank page at last.
Great help. Due to this issue, a simple report made me crazy throughout the day.
Thank you very much.
Thanks so much! This way I solved this issue quicker than when explaining the problem to the NAV implementation partner and have them take a look at it!
Thank you very much for a post. It helped me a lot as well! There are lots of hidden rocks with RDLC unfortunately. It is good that some people share their discoveries and make other guys life easier!
Thanks again.