It doesn't have to do with the signature fields on the form, but rather the usage rights that you added. When the document is opened in Reader/Acrobat, it attempts to validate the digital signature that's included when a document is enabled. Since you've altered the document in a way that invalidates the usage rights signature, it fails to validate and you get that error. The correct way to do this would be to enable the document after you've altered it, but you'd need LiveCycle Reader Extensions for that if you need to do it on the server.
You need to complete the editing of the PDF file prior to adding the Reader Usage Rights. My suggestion is to download the file and open it in Acrobat Pro. Then, use the Save a Copy command (on the File menu) to remove the Reader Usage Rights. Edit that file (the saved copy, not the copy you downloaded) and when it's in the format you need save the file from Acrobat Pro using the File > Save As > Reader Extended PDF > Enable Additional Features menu item (that's the menu item in Acrobat X. You said you were using Reader X so I took a guess that you are using Acrobat Pro X as well).
Thank you for the replies.
More specifically, here's what I'm doing. There's a desk where people come to pick up a gift card. When someone picks one up, a clerk runs this .net program, selects the persons name form a dropdown list, I modify a pdf file (using iTextSharp), by adding the person's name, the serial number of the giftcard, etc, download this file to the client desktop, where the person signs using an ePad. Then the clerk saves that pdf file.
The clerk will not be able to go into the menus and remove and/or save Reader Usage Rights. Is there a way through code that I can add Reader Usage Rights after I modify the file. It sounds from your replies that that's what I need to do.
Also, I don't really care about the official "signature", security, certificates, etc. I just want someone to be able to scribble onto the document using a signature pad.
I do have Acrobat Pro X and LiveCycle. (I assume that means I have LCR Extensions.)
1 person found this helpful
Since you cannot use Acrobat on a server, the only way to add usage rights to a PDF on the server is to use the LiveCycle Reader Extensions product. This has a Java API.
When you say you have LiveCycle notice that LiveCycle is a whole family of products. The one you have is probably LiveCycle Designer, unusually a desktop product. Almost all of the others are enterprise class server products.
Dear Test Screen Name,
Yes, I have LiveCycle Designer. I"ll look into whether I can get the Extensions onto the server and use the Java API.
Just to be clear, Usage Rights are necessary in order to have a Signature Box in the pdf? If so, is there any way around that?
It's complicated... and may well be different in Reader 11.
If there are less than 100 such desks, it could be cheaper and simpler to just install Acrobat on each desk.
There are 3 desks.
So, if Acrobat were installed, does that mean the clerk would have to (once the file gets downloaded and opened) do a Save As... to enable Reader Usage Rights, prior to the person signing on the signature pad?
I assume that at each desk there is a signature pad directly connected?
In this case Adobe Reader wouldn't be involved at all.
Reader usage rights just aren't relevant, you have the full power of Acrobat available to you.
You are right! Currently the 3 desktops only have Reader but I see that if you have Acrobat and associate pdf's to Acrobat, then this works perfectly.