Hello,
I have a couple customers that are experiencing problems using the Common Driver. We started them on version 2.1 and tried version 2.5, but neither seems to work. We've decided that the problem doesn't seem to be caused by the version and since we aren't distributing 2.5 yet, we'd like to stick with getting this resolved with version 2.1.
This user is running XP Home SP2. The user is an administrator. The driver installs fine and there doesn't seem to be any problems with getting them installed, but when they use our program to print to the driver and create a PDF it doesn't work. Everything seems to work just fine and no errors are reported, but no PDF file is ever created. I've tried uninstalling and reinstalling several times using both versions and always get the same result. I've don't complete uninstalls using the instructions found in the forum with reboots in between. I've eliminated the possibility that there is something with our program by creating a simple vbs script that calls a test method in the print dll that simply activates the printer and prints to it. Again, everything appears to work fine, but no output ever gets created.
I have completely run out of ideas as to what is causing this problem and am unable to replicate it on my end. This process works just fine on test machines here and with other customers.
Do you have any ideas whatsoever as to why these customers can't print?
Thank you
Converter Driver not creating PDF files
I am specifying the output filename by setting the .DefaultFileName property with the full path to the output file. An example would be:
oCommonDriver.DefaultFileName = "C:\test.pdf"
and using the appropriate constants:
oCommonDriver.FileNameOptionsEx = NO_PROMPT + USE_FILE_NAME
Keep in mind- this works fine for almost all but 2 or 3 customers.
oCommonDriver.DefaultFileName = "C:\test.pdf"
and using the appropriate constants:
oCommonDriver.FileNameOptionsEx = NO_PROMPT + USE_FILE_NAME
Keep in mind- this works fine for almost all but 2 or 3 customers.
Hello,
The situation you have described typically occurs when the PDF Converter is being restricted from accessing the system’s FILE: port. Although the PDF Converter printer does not use this port it needs to be able to access it.
This scenario typically is caused by some other installed virtual printer or fax driver. One such driver is Thought Communications’s FaxTalk fax driver. The problem occurs because FaxTalk Messenger prevents the Document Converter or any other printer from accessing the FILE: port.
There are two workarounds for this problem:
Upgrade to the latest version 6.0 of FaxTalk Messenger available from http://www.faxtalk.com.
Disable FaxTalk Messenger 4.5 when using the Amyuni Document Converters.
Hope this helps?
The situation you have described typically occurs when the PDF Converter is being restricted from accessing the system’s FILE: port. Although the PDF Converter printer does not use this port it needs to be able to access it.
This scenario typically is caused by some other installed virtual printer or fax driver. One such driver is Thought Communications’s FaxTalk fax driver. The problem occurs because FaxTalk Messenger prevents the Document Converter or any other printer from accessing the FILE: port.
There are two workarounds for this problem:
Upgrade to the latest version 6.0 of FaxTalk Messenger available from http://www.faxtalk.com.
Disable FaxTalk Messenger 4.5 when using the Amyuni Document Converters.
Hope this helps?
Hello,
We're also experiencing this problem with version 2.10i-7. A few customers had FaxTalk installed, but upgrading/uninstalling this didn’t solve the problem.
The PDF document is created in the correct location, with the correct filename but it is empty (0 bytes).
Is there any sort of logging feature we could enable to and figure out what’s going on? What conditions would have to be meet for a PDF file to be created without any content?
Thanks
We're also experiencing this problem with version 2.10i-7. A few customers had FaxTalk installed, but upgrading/uninstalling this didn’t solve the problem.
The PDF document is created in the correct location, with the correct filename but it is empty (0 bytes).
Is there any sort of logging feature we could enable to and figure out what’s going on? What conditions would have to be meet for a PDF file to be created without any content?
Thanks
Empty PDFs!
I am still experiencing this problem and it is becoming extremely frustrating to my customer. Obviously the user does have rights to the output directory since a file does get created but it has 0 bytes and she is logged in on the Adminstrator account.
Do you have any ideas what is happening here at all? I understand that another printer could be hijacking the traffic to that port, but she doesn't have any of the software that you mentioned installed.
Do you have any ideas what is happening here at all? I understand that another printer could be hijacking the traffic to that port, but she doesn't have any of the software that you mentioned installed.
I had the same problem when I first played experimented with this driver. The driver appeared as a Windows printer but it was configured for port "LPT1". I changed that to "Print to File", and it worked like a charm.
It stores the files in the logged in user's document folder. It works best if you specify a path name. The easy way to do that is copy a path from the Windows Explorer address bar, then paste it in followed by your desired file name.
Rudedog
It stores the files in the logged in user's document folder. It works best if you specify a path name. The easy way to do that is copy a path from the Windows Explorer address bar, then paste it in followed by your desired file name.
Rudedog