Quantcast
Channel: Adobe Community : Popular Discussions - Commenting & Collaboration
Viewing all articles
Browse latest Browse all 14216

Sign and Certify (Visible Signature) issues

$
0
0

Hi everyone.

 

We have been having problems with Certify (Visible Signature) when signing a file.

The error we get is "There was an error when attempting to commit this signature. The document was not saved. The file may be read-only, or another user may have it open. Please save the document with a different name or in a different folder".

I must say that this happens randomly and I must add that nobody is using the file and the file has not the property "read only" enabled.

The version of the app is Adobe Acrobat Standard XI version 11.0.12, and the OS we are using is Windows 8.1 Pro 64 bit and the computer has RAM: 8 GB and processor Intel Core i7 5500U @ 2.40 GHz.

 

Also, when the error doesn't show up, sometimes the signature does not appear in the document, so we have to start all over again to sign a document.

Sometimes, we can sign only one document at a time. After that, we need to close the app (Acrobat) and open it up again to sign another document.

 

I have read several forums. I have run all the updates for Adobe Acrobat as well as Windows updates.

The security (enhanced) has been disabled and the appearance of the signature is set up as follow:

  • Configure Graphic --> Imported Graphic
  • Configure Text --> Show: Name, Date, Distinguished name, Logo, Labels.
  • Text property: Auto.
  • Default Signing Method: Adobe Default Security
  • Default Signing Format: PKCS#7 Detached.
  • When signing: Include signature's revocation status.

And in Page Display, the option Show large images is enabled.

 

We can sign near to 50 docs a day. All the docs we receive are in PDF and must be reviewed and approved by several users. The issue only happens in this computer and this person is the only one that have this particular computer with this OS and this version of Adobe Acrobat Standard.

Finally, we work with workflows. The issue happens during the workflow as well as with any other doc out of the workflow. I have double checked that the file is not in read only as well as nobody else is using it at the same time. As I said, It also happens out of the workflow.

 

I wait for any comment or remote support in the case you can provide it.

 

Thank you.


Viewing all articles
Browse latest Browse all 14216

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>