Hello,
We have the professional developers version of PDF Converter 2.50d. This is working well on Windows XP, Vista, Windows 2003. We have a client who has installed Windows 2008 server who is complaining that the PDF converter is not creating files when run on that platform.
- The PDF printer was created on the server via INSTALL.EXE, logged in as administrator
- The INSTALL.LOG file indicates that the printer was created successfully
- When we programmatically print to the PDF printer from within our application (also logged in as administrator) we don’t get any errors, all that happens is that the PDF file is not created anywhere, so our application fails when trying to do a subsequent merge.
- I have tried doing a INSTALL –u, reboot and reinstall, but the problem still exists
- The Windows 2008 server is as initially installed, no other 3rd party software (or printers) are installed
- the “Microsoft XPS Document Writer†printer was installed by default
NOTE: The identical application programs create the PDF file fine on all the other platforms as mentioned above.
Has anyone verified that PDF converter works on Windows 2008. And if so, do you have any clues as to why it is failing here.
Ross.
PDF Converter on Windows 2008
Version 2.50d is very old. We tried version 3 with 2008 and it works properly.
Did you try version 2.51 or 3?
Did you try version 2.51 or 3?
Custom Brand the Amyuni PDF Printer Driver http://www.amyuni.com/en/developer/branding/index.html
Amyuni PDF Converter tested for true PDF performance. View results - http://www.amyuni.com/benchmark
Amyuni PDF Converter tested for true PDF performance. View results - http://www.amyuni.com/benchmark
-
- Posts: 12
- Joined: Wed Aug 10 2005
Joan,
I managed to get 2.50d working under W2K8 (and also tried V3.02 with the same results).
The issue was that when the PDF printer is installed it doesn't create a printer record within the following keys:
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows NT\Currentversion\PrinterPorts
and
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows NT\Currentversion\Devices
i.e. Our application is web based and we get errors opening the PDF printer from within our application unless the aboves keys for the printer exist. I manually created the keys and it all worked OK from there.
I managed to get 2.50d working under W2K8 (and also tried V3.02 with the same results).
The issue was that when the PDF printer is installed it doesn't create a printer record within the following keys:
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows NT\Currentversion\PrinterPorts
and
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows NT\Currentversion\Devices
i.e. Our application is web based and we get errors opening the PDF printer from within our application unless the aboves keys for the printer exist. I manually created the keys and it all worked OK from there.