PdfFileEditor concatenate multi-page pdf's generates empty pages

As a workaround for the font-size bug I reported, I'm trying to generate one large pdf by concatenating all the individual pdf invoices. The idea is that at the end of the invoice run the end-user only needs to open that large pdf, select the printer and tray, and press print.

I'm using the PdfFileEditor class' Concatenate method (tried both Stream and string as input) to create the overall pdf. As long as the individual pdf's have only one page the result is okay. As soon as a pdf contains more than one page the resulting pdf contains a blank page for each page in the original.

Is there a fix for this?

It seems that the problem is not related to the number of pages. I get the error using pdf's generated using Sql Server Reporting Services 2008. The pdf's generated using SRSS 2005 seem to be handled correctly. Attached two examples of the pdf's that result in blank pages when concatenating.

Hi Jim,

I have tested this issue using 3.4.4.4 hotfix and I couldn't notice the problem. I have successfully generated the output file. Please download the latest hotfix 3.4.4.4 and try to concatenate the files at your end.

If you still find any problem please do let us know.

Regards,

The 3.4.4.4 version solved the issue.
Thanks.

Hi,


I’m currently facing the similar problem as jimfranquemont had. When i combine 2 pdf’s generated using SSRS 2008, i get a blank pdf file. Though the file property shows the file size to be around the sum of the 2 input pdf files.
Our version of pdf.kit is ver2.6.0.0.

Is this issue resolved for an isolated version of pdf.kit or does it occur in all versions of pdf.kit released before 3.4.4.4 hotfix.

Thank you,
Vijay

Hi Vijay,

The latest version of Aspose.Pdf.Kit for .NET is 3.5.0.0. Please download it from this [link](http://www.aspose.com/community/files/51/file-format-components/aspose.pdf.kit-for-.net-and-java/default.aspx).
If problem persists then please share the source PDF files with us so we could test the issue at our end.

We’re sorry for the inconvenience.
Regards,

Thanks a lot.. V3.5.0.0 solved our problem.

Vijay