Setup: We have an application (FLITE) running under Terminal Services (TS) in Windows Server 2003. This application allows a user to save a report in PDF format using the PDF Converter. (PDF Converter has been installed as a printer by an Adminstrator.) TS can be started with two logins: the first one (TS1) automatically starts FLITE, the second (TS2) runs a script file which delays for 25 seconds before starting FLITE.
Problem: Under TS1 when we go to save the report as PDF, a blank PDF file is created by PDF Converter; under TS2 the correct 'populated' PDF file is created.
Question: Is there an issue with automatically starting programs under TS and the 'initialisation' of the PDF Converter driver? Is there a delay in TS before it can recognise 'printers' such as PDF Converter? Can I add another DLL call in the FLITE application that will get over this? (FLITE already uses the DriverInit and DriverEnd routines wrapped around the saving code.)
* We want to get rid of the script that spawns FLITE.
Thanks in advance for any suggestions,
Fiachra
"Initialisation" on Terminal Services
Hello,
There is no need for a delay before being able to use the PDF Printer unless the printer is not installed on the system.
When turning on the Terminal Server, and before running FLITE, will you have the PDF Printer installed and enabled on the server?
Are you using PDFDriverInit in FLITE or only DriverInit?
If with TS1 a blank file is created than maybe when running FLITE directly an empty report is generated and it is converter to pdf.
Please try to trace your application and to direct printing to a physical printer to see why precisely an empty pdf file is created.
By example you can try to log in as TS1 and to direct printing to a physical printing instead of the PDF Printer, will you get empy pages?
Thanks.
There is no need for a delay before being able to use the PDF Printer unless the printer is not installed on the system.
When turning on the Terminal Server, and before running FLITE, will you have the PDF Printer installed and enabled on the server?
Are you using PDFDriverInit in FLITE or only DriverInit?
If with TS1 a blank file is created than maybe when running FLITE directly an empty report is generated and it is converter to pdf.
Please try to trace your application and to direct printing to a physical printer to see why precisely an empty pdf file is created.
By example you can try to log in as TS1 and to direct printing to a physical printing instead of the PDF Printer, will you get empy pages?
Thanks.
Hello Joan,
Thanks for the earlier reply.
* The PDF Printer is installed and enabled on the server before running FLITE.
* FLITE uses DriverInit.
* FLITE cannot not generate an empty report - it will always have header information at the very least.
* On log in with TS1, FLITE can immediately print a report to a physical printer - it cannot be immediately saved to PDF and viewed as the PDF will be empty.
As I mentioned in the previous posting, if there is a delay of 25 seconds before starting FLITE the PDF functionality works correctly; with no delay, the PDF functionality does not work.
If you've any other ideas...?
We want to purchase PDF Converter, but cannot if this issue is not resolved.
Thanks in advance,
Fiachra
Thanks for the earlier reply.
* The PDF Printer is installed and enabled on the server before running FLITE.
* FLITE uses DriverInit.
* FLITE cannot not generate an empty report - it will always have header information at the very least.
* On log in with TS1, FLITE can immediately print a report to a physical printer - it cannot be immediately saved to PDF and viewed as the PDF will be empty.
As I mentioned in the previous posting, if there is a delay of 25 seconds before starting FLITE the PDF functionality works correctly; with no delay, the PDF functionality does not work.
If you've any other ideas...?
We want to purchase PDF Converter, but cannot if this issue is not resolved.
Thanks in advance,
Fiachra
Hello,
Maybe you already contacted Support@amyuni.com and get this issue resolved.
From the above description i am not sure why FLITE would need the 25 seconds delay if the printer is already installed on the system.
If this issue is not resolved yet you may need to run FLITE in debug mode and trace why it is not printing to the PDF Printer if there is no the 25 seconds delay.
Thanks.
Maybe you already contacted Support@amyuni.com and get this issue resolved.
From the above description i am not sure why FLITE would need the 25 seconds delay if the printer is already installed on the system.
If this issue is not resolved yet you may need to run FLITE in debug mode and trace why it is not printing to the PDF Printer if there is no the 25 seconds delay.
Thanks.