Signing a document, generates a "Timestamp signature property generation error: Verification error."

I am getting this error message when I sign my documents. Especially when I try and create a second or third signature on a document.
I have just upgraded to Reader11.0.09 and then when I got the error, I went back to Reader 11.0.08 and then back to Reader 11.0.07 but all are giving the error. The document gets signed but a pop up box shows the "Timestamp signature property generation error: verification error"
I have the settings pointing to our timestamp server under Preferences > Document Timestamping > Server Settings.
Under signature verification preferences > Verification > Verification time, I have the "Secure time (timestamp) embedded in the signature" selected.
It seems to work but is generating the error. If I open a new document and sign it sometimes it works without the error. Occasionally it produces the error on first signing. Mostly on second and third signatures on the page..
Any ideas?

you can mail me directly to [email protected], and I'll try to help.
no guarenty :-)
Tal
[email protected]

Similar Messages

Transforming signed XML document with namespace invalidates signature

I am running into a problem signing an XML document. Well, signing the document isn't the problem, as I can sign it and then verify the signature with the public key successfully. The problem comes when I transform the document to a string. It all appears to be OK, but when I transform it back, the hash no longer verifies. After more testing, it appears that the issue is related to namespaces. When I remove namespaces from the document, the signing and transformations work just fine. Does anyone have any insight on this?
Here is how I am transforming the document to an XML string that I and back.
    try
      signSAML( doc, assertionElement );
      xmlSource = new DOMSource( doc );
      baos = new ByteArrayOutputStream();
      outputTarget = new StreamResult( baos );
      xmlString = new String( new ByteArrayInputStream( baos.toByteArray() ) );
      transformerFactory = TransformerFactory.newInstance();
      transformer = transformerFactory.newTransformer();
      transformer.transform( xmlSource, outputTarget );
      boolean verified = verify( doc );
      if ( verified )
        System.out.println( "Verified" );
      else
        System.out.println( "UNVerified" );
    catch ( Exception e )
      // TODO Auto-generated catch block
      e.printStackTrace();
    }

jtahlborn wrote:
i'm not talking about the transform, i'm talking about this line:
xmlString = new String( new ByteArrayInputStream( baos.toByteArray() ) );which is a great way to break xml data.Yes. That's not the only kind of data it's good at breaking, either.
To the OP: just have your transform output to a StringWriter in the first place. Don't muck about converting between chars and bytes unless you know the correct encoding and use it. Which you don't know it and you didn't use it.

Sign pdf document - no allowe new signature id

hi together,
i do have a workflow planned where several people should sign task cards on a pdf document (using acrobat reader version 9)
i would like to have the signatures for the people who will be allowed to sign the document to be created my own. the creation of new signatures should not be allowed.
when someone selects the signature id, there is the opportunity given to create new signatures.
is there any way that the creation of new signatures can be baned?
in advance thank you very much for your answer - Frank

thanks Simon ATS,
the only question is now how and where to disable the "create self sign id" function.
may be someone can give some additional help.
thanks in advance - Frank

Recieving error when signing a document

When signing a document, users are receiving >>Timestamp signature property generation error: Unsupported transport protocol
Time Stamp Server is configued as Server URL: IP Address of Time Server
Any ideas on how to resolve this error?

Hi,
The problem is probably the URL for the timestamp server is an SSL address (i.e. https://) and the certificate that the OS needs to validate the SSL connection is not available. One thing to try is to copy the address for the timestamp server and paste it into a browser. This may give you the option of installing the SSL certificate.
Steve

Version of file protected by timestamp signature (3161) alone shows "Unrecognized PDF Content"

Documents which have been signed with a RFC 3161 timestamp signature alone show "Report Code: 4000" described as "Unrecognized PDF Content" in the PDF Signature Report. I access this report by selecting the signature in the panel and "Click to view this version", then an option to "View Report" is in the top right corner.
Documents with digital signatures and attached timestamps from the same TSA verify properly and show no errors in the PDF Signature Report.
All of the timestamps verify properly, though the TSA root certificate must be downloaded and trusted manually.
Any ideas as to what's going on here?
An example called InvoiceTS.pdf can be found here. You may also use the link to StarField below to timestamp any PDF you like; the problem occurs universally.
Version Info: Problem shows in Acrobat X and XI and Reader X and XI, occurs in files with timstamps attached by both Acrobat X and XI.
TSAs affected: DigiStamp, StarField
Explicit Error:
Unrecognized PDF content: The document contains PDF content or custom content not supported by the current version of Adobe Reader.The document appears to have been produced by a later version of Acrobat.

I have been on the phone with Adobe support more times than I care to remeber about this issue. It would be nice if the problem would be addressed so a capability Adobe claims to exist with Adobe X actually functions properly.

Signing a Document using Custom PKCS#11 and Hardware Token

I am using a custom PKCS#11 dynamic library and a hardware token to sign a document in Adobe Acrobat 10. I encountered this error when I used the Standard Text as the Appearance of the Signature.
Creation of this signature could not be completed. Unknown error Support Information: CDSHandler-657
If I use a custom appearance, the signing is successful.
Do I need to set anything else before signing the document? Everything works fine on Adobe Acrobat 11. I am using a Mac OS X 10.9 machine. The same error is encountered in Windows 7.
Is this a known issue in Adobe Acrobat 10?

My bad, actually I was not using Adobe SDK. I just loaded my custom PKCS module and tried to sign the document. Have you encountered this error?

Programmatically Accessing Self Sign in Plug in for Digital Signature

Hello There,
We are looking forward to use “Adode Acrobat 9 Pro – Self Sign in Plug in” for one of the application to digitally sign PDF document i.e. appending signature to existing PDF document. We have gone through Adobe site (http://learn.adobe.com/wiki/download/attachments/52658564/samplesignatures.pdf?version=1 ; http://www.adobe.com/ap/epaper/tips/acrsignatures/ ) and explored “Tips and Techniques” along with screenshots.
We would like your help on following queries:
·         Can we programmatically from C#.NET access Adobe Object and create certificate for digital signature? If Yes, can you please provide pointers, references and sample code snippets? [We understand that we do not need to purchase SDK as Professional would be sufficient for digital PDF signature]
·         Does Adobe Pro installer provide DLL which can be leveraged in Code base i.e. C#.NET?
·         How does certificate management work for digital signing? Can third party like verisign, local computer / certificate from organization server work for digital PDF signature?
·         Please provide Technical Reference manual to use Adobe from C#.NET
·         Can you please throw some light and pointers on Licensing and Cost?
We are running on a deadline hence your quick help and response will be highly appreciated.
Thanks & Regards

best check on the sdk forum:
http://forums.adobe.com/community/acrobat/acrobat_sdk
sdk docs can be found here:
http://www.adobe.com/devnet/acrobat/?view=documentation

How to digitally sign PDF document in VB?

Hi,
I was wondering if there was a way to open a PDF file and digitally sign the document (with the electronic signature info showing on the bottom of the last page) programatically?
Thanks
K

> (1) When I download the SDK, it only has a setup file which I launch - I don't see any documentation in there and no menu item is created.
Where did you download the SDK?
> (2) When I go to the livedocs.abobe.com link and look how to use Javascript to digitally sign documents, the link is blank and is waiting for someone to post a comment.
May be a problem of your browser.
> Does someone know of a VB code that allows you to digitally sign the PDF documents via Javascript?
Look at the JavaScript sample AddSignature in the SDK.

Generate report using Word Report Generation VIs error

When I Generate report using Word Report Generation VIs ,the error is generated.
This is my Vi
can somebody tell the error reason?
The attaché is Vi (one is 2011,other is 8.6)
Attachments:
report-8.6.vi ‏16 KB
report2.vi ‏33 KB
template.doc ‏40 KB

Hi Ben64
Thank you! The problem is solved.
BUT when I use the Word Easy Graph vi ,the result is
I want the Graph (curve),like as:
How Can I do get the picture.
I have other problem. I want to get default name for the new word file.
liang

How do I sign a document in Adobe Reader w/electronic signature?

I'm trying to sign a tax form, its unclear from the Reader doc how to create a signature for use on the document.

Hi Matt,
Starting with the form you want to sign opened in Reader, select the Fill & Sign tool on the right side of the toolbar. This will open the right hand Fill & Sign panel. Next, open (expand) the Fill & Sign Tools pane.
There are three possible scenarios from this point...
The Place Signature tool is disabled (grayed out). This would be because the security setting on the file do not allow for changes.
The Place Signature tool is enabled, but when you select it and get the Place Signature dialog, the only option available is Use a certificate. This is because the document contains an existing signature field and the assumption is the document author requires a secure digital signature as opposed to electronic signature.
The Place Signature tool is enabled,and all of the radio buttons are enable on the Place Signature dialog.
Depending on which of the three scenarios you encounter drive what you can do next. Obviously with scenario 1 there is nothing else to do. With scenario 2 you have to have access to a valid digital ID to create a digital signature. With scenario 3 you have the option of creating either a digital signature using your digital ID, or you can create an electronic signature by placing a mark on the document. That mark can be your typed name, a signature you create with a mouse, or a scanned image of your wet-ink signature.
If you need to create a digital signature, then you need to have access to a digital ID. There are two options for procuring a digital ID; either you can buy one from a trusted Certificate Authority (CA) who will vet your identity, or, you can have Reader generated an untrusted digital ID for free. What you select to do depends on what the second party (you're the first party, the document recipient is the second party, and if a CA is involved they are the third party) requires, or more precisely, what agreement you and other party come to.
I hope this helps get your started.
Steve

Digital Signature -- Unlock signed off document

Hello,
We are implementing digital signature to BBP documentation. The signatures can be successfully triggered and documents can be signed off and status changed. When trying to unlock the signed off documents, in the document attribute window, the unlock button is however not available. Therefore we can never get a signed document re-opened. I wonder how we could configure to get the button visible?
We'd appreciate any suggestions you may have to share with us. Many thanx!
Regards, Li

HI Jason,
Thanks for the message. Yes the "document is locked" checkbox has been selected.
What is the role you mentioned? I created a role with authorization objects C_SIGN and C_SIGN_BGR, but it seemed not to help.
There is supposed to be a "document unlock" botton available in the document attribute, see a sample in the presentation (shown in slide 11, step 3).
https://websmp110.sap-ag.de/~sapidb/011000358700002397472006E
Now when I open the attribute of a signed document, the "document unlock" button is not available, I am wondering where in the configuration/role we should do more.
Hopefully this helps you to understand my problem a bit more
Kind regards,
Li

Digital signature- signing adobe documents

Hello
We are planning to buy Adobe true credentials for signing the adobe documents using digital certificates.
the program that we have is using the .pfx private keys to sign the documents. Can someone pls let us know if true credential software is going to generate private keys?

intbuz,
First off you'll get better results posting in the appropriate forum, this is the Digital Editions forums which is discussion about Adobe Digital Editions and eBooks in general. So the people on the forum generally aren't ready to answer Acrobat Security questions which would be better asked in the Acrobat Windows forums.
Also "True Credentials" is not an Adobe product but a GeoTrust product.
Look at either http://www.geotrust.com/products/client_certificates/true_credentials_express.asp
or
http://www.geotrust.com/products/client_certificates/true_credentials.asp
Assuming that's what you are talking about, a quick overview of the whitepaper leads me to believe that they are using the Operating system protected storage for the both the public and private keys, so while it won't automatically generate .pfx files, you might be able export the private keys after the fact into the container format you desire. However you should really check with GeoTrust about that, since I don't have direct experience with the product.
Jim Lester
Adobe Systems

Sign documents without entering a signature password?

On the PC version of Acrobat you can sign documents very easily without entering in a password every time you want to sign a document. On the mac version it appears that you have to enter a pwd every single time you sign a document... this is very frustrating when signing 20-30 docs at a time. Is there a way to disable the pwd requirement in Acrobat X for Mac?

Hi sojourner166,
For the sake of discussion lets limit how a digital ID is access to either directly from a file or through the operating system (OS). Both the file & the OS methods allow the user to access the private key (that's the part that is password protected) without having to enter the password each time.
On Windows the OS loads the digital ID into the Windows Certificate Store an on the Mac OS it uses Keychain Access. On Windows when you import a digital ID, if you don't select High Assurance (which is off by default) the OS assumes that if you could log in using your password that's good enough and will allow access to the private key without prompting you for the password. On the Mac, Keychain Access has UI which lets you control whether you need to confirm the password or not.
When you are signing with a digital ID in either of the OS based systems Acrobat say to the OS "give me access to the private key so I can do a signature operation". The OS then checks the setting and either grants access without further ado, or, it says to Acrobat "before I'll give you access to the private key you've got to tell me the password". Acrobat in turn puts up a dialog asking the user for the password. You type it in, hit the Sign button and Acrobat says to the OS, "okay here you go, now can I get access to the private key so I can finish this signing operation?". The OS checks the password that Acrobat sent along and if it's correct grants access to the private key, and if it's not correct returns an error code, which causes the signing operation to abort.
If the digital ID is residing in a file then the OS sits on the sideline and Acrobat handles the password work itself. If you are using a digital ID that resides in a file you can set the password timeout option through the Acrobat UI. In the Security Setting dialog expand Digital IDs in the tree view and then select Digital ID Files. From there you can click on the Password Timeout button and adjust how often you want to be prompted for a password to access the private key.
Here's a picture of what you are looking for:
If you are using a digital ID listed under Keychain Digital IDs let me know and I'll work up those steps for you.
Hope this helps,
Steve

Sign pdf document and email to others for their signature

I created a pdf from a word document using the pdf converter in word. i create a digital id to sign the document,
email to a co-worker hoping they can do the same, but the sign menu is greyed out, how can i accomplish this.

Splitting document - Acrobat Pro.
An experienced programmer could write JavaScript to pick up the customer numbers and do something with it, but it's not for the faint hearted.

Acrobat X Pro crashes when signing a document

Acrobat crashes on any attempt to sign a document. Error is as follows:
Problem signature:
Problem Event Name:          APPCRASH
Application Name:          Acrobat.exe
Application Version:          10.1.0.534
Application Timestamp:          4ded1a14
Fault Module Name:          AcroForm.api
Fault Module Version:          10.1.0.534
Fault Module Timestamp:          4ded283d
Exception Code:          c0000005
Exception Offset:          000dc6ad
OS Version:          6.1.7601.2.1.0.256.48
Locale ID:          1033
Additional Information 1:          0a9e
Additional Information 2:          0a9e372d3b4ad19135b953a78882e789
Additional Information 3:          0a9e
Additional Information 4:          0a9e372d3b4ad19135b953a78882e789
Tried updating to current version and Acrobat crashed completely. Restored to 10.0.1.
Eric

Yes it is up to date.
I can use the stamp tool and flatten it after with no problems, but the typewriter tool crashes it upon attempting to flatten.

Signing a document, generates a "Timestamp signature property generation error: Verification error."

Similar Messages

Maybe you are looking for