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.
Related
For some reason my subscription to a report gets emailed using the subscription service, the font sizes are increased only on text that has an underlying link for example:
However, when I run the report normally (just navigate to it using the browser), all is fine:
What am I doing wrong??
Me too. There is no fix
I just get mine either via pdf, excel or html not mhtml.
But html has it's own issues and is not recomended.
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?
We are having an issue while generating a huge PDF Report. We are using SSRS 2008 and a particular report generates more than 1000 pages. If I export to PDF format, the data is populated upto page no. 465 and rest of the pages till 1000 are totally blank. I have Adobe Reader 9.0 installed on my machine and I thought there should be some issue with the reader itself. I upgraded to Adobe Reader 10 but experiencing same issue. Everytime I generate the report and export to PDF (using the report viewer webcontrol), the pages become blank after 465. There is absolutely no problem with the data (the stored procedure which I am using to load customers) and I have verified in the backend. We had this issue last month and somehow it got fixed automagically. Now again we have the same issue. Any help please?
Apparently there was nothing wrong with SSRS or Adobe reader or anything related to caching. Some of the sections in each page were pushed to next page due to increase in height of an image. When I readjusted the height of the embedded image control, everything went fine.
I’m having an issue with PDF output being rendered in Adobe Reader’s ‘in browser’ feature from an ASP Classic site.
I have a form with a handful of inputs that trundles off and makes a PDF report. The report renders correctly (all input values accounted for) when saved as a file, but gives a blank screen when displaying in Reader v7.0, and goes straight to a no-input-values report in v8.1.2.
Pressing ‘refresh’ in the browser from here will also display a report indicative of none of the HTML form inputs being carried forward.
Are there any basic mechanics of the
HTML form post-back that I may have
left out?
*The one thing that puzzles m*e is that un-checking the ‘Display in-browser’ option in Adobe Reader and not restarting the browser gives the correct report in both versions.
The other possible issue is something to do with the browser’s ‘Trusted sites’ policy. The domain had been added to the trusted list, and:
The HTML input form shows as a trusted site in the status bar
The in-browser PDF screen displays at ‘Unknown Zone’
To clarify:
If the Reader is uninstalled, the downloaded file is correct
If Reader is installed, and set to not display in browser, the output is correct
If set to display in-browser with Adobe Reader, it
v7.0 – Displays a blank screen. ‘Refresh’ goes to a no-input-value PDF report
v8.1.2 – Displays the no-input-value report
Un-checking the ‘Display in-browser’ option in Adobe Reader and not restarting the browser gives the correct report in both versions
There is a working old production environment, which is capable of displaying the PDF file correctly in-browser with Reader v7.0 on the same machines we’re testing with. The issue described occurs with the same code being set up in a new environment with tighter security control.
The environment also uses older technology, which won’t be upgraded. This includes:
The site is ASP Classic
The code is outputting PDF v1.3
Internet Explorer 6. Yes. 6.
Any ideas on why the report isn't always carrying forward the HTML input?
Any help appreciated,
Thanks.
The ASP page that generates the PDF is not getting the values from the form. That is why it is creating a PDF form with empty values. Ensure that the HTML form directly posts to the ASP script generating the PDF. There should not be any response.transfer or response.redirect or 404 redirection that goes to the PDF-generating ASP script.
Ah, dang.
So it turns out IIS had GZIP compression enabled, and the client has an IE6-only rollout. There's much written about IE6's GZIP incompatibility, and if you're looking to conditionally allow it in IIS, there are some solutions.
The white screen is result of it being an ASP page that posts back, and changes its 'content-type' in the HTTP header (to 'application/pdf') - where IIS decides it should compress it, and fails in IE6.
Adobe Reader 8 does a 2nd request, losing the postback values.
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