These forums are now Read Only. If you have an Acrobat question, ask questions and get help from one of our experts.

Acrobat/Reader hang while signing the file

Forum Index > Security > Acrobat/Reader hang while signing the file
2008-09-03 22:00:58
kendrew
Registered: Oct 27 2006
Posts: 29

Acrobat/Reader hang while signing the file, it appears the error message:
error event name is BEX
Error module is StackHash_a39a

And after restart the Acrobat/Reader, the file is modifed(Although I did not input my password for my smart card with Certificate), it seems very strange, click the signature, the document show Error that encountered while BER decoding.

My case only appears on windows Vista with acrobat/reader 8.0/9.0; I did not see it on Windows XP

Top
2008-09-06 14:57:43
#1
plevy
Expert
Registered: Jul 8 2008
Posts: 80
Possible causes of hangs while signing:

- smart card driver not installed properly or doesn't work with vista
- signing process involves internet requests for certificate revocation checking, but network or LDAP failed to respond in some unusual way (usually, this results in a timeout error, not a hang).
- windows firewall is blocking some needed port (again, usually timeout rather than hang)
- very unusual certificate chain with cross certifications
- bugs

To pursue more, you need to give more details of the setup and where in the signing process the hang occurs.
Top
2009-12-20 06:10:21
#2
sujitj
Registered: Dec 20 2009
Posts: 1
I am trying to sign a PDF form using Acrobat Reader 9 using a digital signature using an USB eToken. However, I keep getting the following error message - Error encountered during Signature Verifications. Error encountered during BER Decoding. Can anyone help me understand the reason for these error messages and if there is a solution to this. Thanks, Sujit J
Top
2010-01-06 11:24:59
#3
jbharris
Expert
Registered: Dec 17 2007
Posts: 18
(1) Upgrade to the latest version of Reader 9, and (2) upgrade to the latest version of the middleware from your smart card vendor, which I believe would be SafeNet / Aladdin.

This has to do with a change we made to the hashing algorithms (part of the digital signature process), and some of the smart card / token manufacturers did not necessarily anticipate this / correct for this change (which has been coming for some time, actually).

-John B Harris, Adobe

Top