Adobe Reader Cannot print the PDF generated by Converter

dawa · Post by **dawa** » Wed Feb 01 2006

I have a full license Amyuni PDF Converter 2.50f.

My application is able to create PDF file through Converter, but my app users tell me that when they open the PDF file in Adobe Reader and try to print a hard copy, the print menu item is disabled.

How do I correct this problem?

Joan · Post by **Joan** » Thu Feb 02 2006

Hello,

Please check if the file generated by your users is encrypted, if it is than most probably they do not have the right to print it.

Encrypting a PDF file occurs while generating it if specified by the file generator.

Hope this helps.

dawa · Post by **dawa** » Thu Feb 02 2006

Joan,

Thanks for the reply.

I'm not explicitly encrypting it in my code.

What is the file generator? How do stop it from generating encrypted files?

Joan · Post by **Joan** » Fri Feb 03 2006

Hello,

The file generator is the application or user that is generating the PDF file.

If you are sure that the PDF file is not encrypted i don't see why the Print menu will be disabled.

Your users are opening the files in Acrobat Reader, right?

I suggest that you send a file to support@amyuni.com to check it and see how it will open.

Thanks.

dawa · Post by **dawa** » Fri Feb 03 2006

Joan,

Sorry, I cannot send the document to you guys because of the nondisclosure agreement we've signed for clients' information privacy.

My application is using the PDF Converter which is the PDF printer to generate the PDF file. I did open the file PDF file in Acrobat Reader and checked under Document Properties->Security, it says the following:

-------Document Security---------

The document's security Method is used to restrict what can be done to the document.

Security Method: Password Security
Can be opend by: Acrobat 5.0 or later

-------Document Restriction Summary--------
Printing: not allowed
Document Assembley: not allowed
Content Copying or Extraction: not allowed
Content extraction for Accessibility: not allowed
Commenting: not allowed
Filling of form fields: not allowed
Signing: not allowed
Creation of Template Pages: not allowed
Submitting Forms: not allowed

I wrote the entire app that prints the PDF. So I know for sure that I am not encrpyting it in my code.

I checked the printer settings on the client machine using CDINTFEX ActiveX control using Visual Foxpro code:

Code: Select all

o = createobject("cdintfex.cdintfex")
o.DriverInit("printer name")
o.EnablePrinter("company name","activation key")

I was able to get the following values for that particular printer:

Code: Select all

o.Encryption returns 0
o.FileNameOptions returns 3
o.FileNameOptionsEx returns -1073479677

Is it possible that there is a defalut setting on the printer that needs to be altered? Please help!!!

dawa · Post by **dawa** » Fri Feb 03 2006

Joan,

I created a test PDF file and emailed to the support@amyuni.com address.

Thanks again, it is urgent!!!

dawa · Post by **dawa** » Mon Feb 06 2006

Joan,

I hopey you got my email.

I never got a response and rejection of the email. Hope you got it.

Please let me know.

Joan · Post by **Joan** » Wed Feb 08 2006

Hello,

I checked the code you posted here.

I noticed that you are calling FileNameOptions and then FileNameOptionsEx.

Please note that you don't need to call these two functions, you can comment FileNameOptions and keep the call to FileNameOptionsEx only.

I don't know what does the value -1073479677 stand for but you should call:
o.FileNameOptionsEx = NoPrompt(1) + UseFileName(2) + any other feature you like to add.

Please note that the values added to FileNameOptions sould be all in Decimal value or Hexadecimal.

Hope this helps.

dawa · Post by **dawa** » Thu Feb 09 2006

Problem solved!

Joan,

Thank you so much for you patient help!

I stated in my email to you the cause of my problem but I want people who read this thread to know as well.

Joan made the suggestion the clear the option through the registry. Instead of clearing it, I actually took the value and did bet test against the EncryptDocument128, sure enough it was set. Because I know very clearly that I am not setting that bit, the only explation is that I have a errornious constant that is setting that bit. So I examined the constants.
I had incorrect bit set in the option CCITTCompression which happen to be the bit flag for EncryptDocument128. So the docuemnt generated was encryted naturally.

For those who are curiously, the following is the registry hive:
HKEY_CURRENT_CONFIG\Software\your printer name\Options
You'll see other settings as well.

Dawa