I just upgraded from 2.1 to 2.5 PDF Converter. Now, each time we resart the app server machine (via a reboot), the first call to print fails with a -1. If I reinstall the drivers, all is fine, but its dang frustrating. I run the install, put in the Licensee and Key and the install works fine. Something is getting reset at reboot. Any clues? I am generating PDF reports from a PowerBuilder component running within EAServer.
Thanks,
Rick
Each time my server reboots, I have to reinstall 2.5
Yes. I have followed instructions found on another topic in which I uninstalled 2.5, rebooted, then went to control panel, printers, File menu, server properties, drivers, and removed both the 2.1 and 2.5 drivers. Then reinstalled 2.5, proper activation and licensee..installs fine, but subsequent reboot yields an error on the first print. I wonder if this is an EAServer thing, who knows. Anyone???
rick
rick
sorry, didn't specifically answer your question. Yes, i have updated the key in my application code. I did not change any other code in my application component, only the value of the key. Is there anything new in how 2.5 makes its initial call? Again, if i reinstall the drivers after the reboot, i can run just fine, this is only happening just after a machine reboot.
Hello,
Are you calling PDFDriverInit in your application?
If yes, please either replace the call of PDFDriverInit by a call to DriverInit or call DriverInit right after your call of PDFDriverInit.
Please note that these functions (PDFDriverInit and DriverInit) should be called once when launching the application and not each time you print.
Let us know if this helps.
Are you calling PDFDriverInit in your application?
If yes, please either replace the call of PDFDriverInit by a call to DriverInit or call DriverInit right after your call of PDFDriverInit.
Please note that these functions (PDFDriverInit and DriverInit) should be called once when launching the application and not each time you print.
Let us know if this helps.
I'm calling DriverInit. This code is executing within a method of a stateless component on EAServer, therefore, I need to call this method each trip through. Still experiencing this problem... If I run the install after I reboot the server and before the first request into this method, all is fine...if the call is made first, it fails with a -1 on the Print() method... I then can run the install again and it is fine.
Out of ideas.....
rick
Out of ideas.....
rick
Hello,
DriverInit will fail if the printer is not installed on your system.
Ie: If you call: DriverInit("My PDF Printer"), and there is no printer on the system called "My PDF Printer", DriverInit will fail.
What is weired is the fact that the printer is getting removed when closing your application. Please check the following:
- When rebooting your server, will you see the PDF Printer there?
- In your code, are you calling "PDFDriverInit" at any time?
- When closing your application, will the PDF Printer still there or is it removed?
Thanks.
DriverInit will fail if the printer is not installed on your system.
Ie: If you call: DriverInit("My PDF Printer"), and there is no printer on the system called "My PDF Printer", DriverInit will fail.
What is weired is the fact that the printer is getting removed when closing your application. Please check the following:
- When rebooting your server, will you see the PDF Printer there?
- In your code, are you calling "PDFDriverInit" at any time?
- When closing your application, will the PDF Printer still there or is it removed?
Thanks.