As the subject states, we're seeing PDFx generating a blank page. When it works the PDF should have 2 pages.

Typically, for our applications the PDF is saved to C:\Users\**\ate_files\name.pdf without additional user prompts. When it fails there's a prompt with a "Save As" dialog with C:\ATE\Cache as the current directory. This is a PDFX dialog as you can see the PDFX icon on the taskbar while the "Save As" dialog is visible.

Here's a table of EL7/ATE versions.



PDFx Version: 9.2.359.0

Here you can see the "Save As" prompt with the PDFX icon in the taskbar.


Here are the contents of our ATE PQI file.

I'm not clear just what's happening here. Your chart seems to indicate that it's really dependent on the A-Shell version on the server, but you're printing it thru ATE, so all the server has to do is send the file to the PC C:\ATE\Cache directory. Is there a problem with the file transfer not working? If so, that would equally affect APEX preview, which would be an easy way to test it.

You say it generates a blank page. Does that mean the source file is there, but empty?

Can you print the file by using File > Open Local Session and then PRINT from the ATE dot prompt?

Here's what I see ...

After being able to reproduce this consistently, now I can't. I guess this is not a problem.

To be clear, the generated PDF was blank, I didn't look at the source.

Sorry for wasting your time.