We have found that in some instances, the PDF Converter print driver creates a PDF with no pages (this is most likely caused by the source print job).
When this happens, the info dictionary is not finished properly in the PDF file. For example, here is the entire object entry for the info object in one such PDFs, followed by the Pages dictionary object:
1 0 obj
<<
/Title (! B e n e f i t s 2 0 0 4 . x l s)
/Producer (Amyuni Document Converter)
/Version (Version 2.10h - Licensed to Trumpet, Inc.)
/CreationDate (2/2/2004 11:22:17)
3 0 obj
<<
/Type /Pages
/Count 0
/Kids []
/Resources <<
/ProcSet [/PDF /Text /ImageB /ImageC /ImageI]
/ColorSpace << /CS1 [/Pattern /DeviceGray] /CS2 [/Pattern /DeviceRGB] >>
>>
>>
Note that the 1 0 obj entry does not have an ending '>>' before the 3 0 obj begins.
Any help on this one?
- Kevin
Print driver creates corrupt "empty" PDFs
Hello,
Please check that you are not printing in a multithreaded environment, and that you are not in a situation where a multiple jobs are printed to the PDF Printer in the same time.
If this is the case than please use the locking mechanisme of CDintf while printing.
If this is not the case please send us a sample code with your test case specification to support@amyuni.com so we can try to reproduce this issue and check what is happening precisely.
Hope this helps.
Please check that you are not printing in a multithreaded environment, and that you are not in a situation where a multiple jobs are printed to the PDF Printer in the same time.
If this is the case than please use the locking mechanisme of CDintf while printing.
If this is not the case please send us a sample code with your test case specification to support@amyuni.com so we can try to reproduce this issue and check what is happening precisely.
Hope this helps.