Do you open your PDFs for signing in the desktop or in a browser? There are some differences between the two.
During the signing process Acrobat saves the signed PDF. This error relates to the file you save not the original PDF you're signing, although the two may be the same, you can save signed PDF in-place overriding the original PDF, although this is not a good practice. Do you have write rights in the location where you save? Do you have a PDF with the same file name in the location where you save? Is this PDF by any chance opened in another application (not the same Acrobat session where you sign)? If you have both Reader and Acrobat installed on your machine and you have PDF in the save location opened in Reader and you try to sign a PDF in Acrobat and save it in the same location with the same name as the PDF opened in Reader you'll get this error. The same may happen when you have PDF in the saved location opened in a browser and you try to save signed PDF in the desktop Acrobat in the same location/name.
Non of the above you mentioned happen. The PDF is opened in desktop version and it is not being used by anyone else except for the user that has full permissions and when signing the doc, Acrobat ask to save the file and we want to override the same file with the same info and with the signature added. The file is not opened with the Reader.
I want to let everybody knows that today we did an upgrade to Windows 10. We have been testing the app Adobe Acrobat Standard XI version 11.0.12 in Windows 10 and we haven't had errors today.
We will test the app two more days and if there is no error after 2 days, my solution will be to recommend to upgrade Windows 8.1 to Windows 10.
2 people found this helpful
I too have suffered with this problem for almost two years now and I think i have identified what the problem is, but I do not know how to solve it 100%. Are you by any chance trying to save the file into a network drive or to a place where it might sync to multiple devices like dropbox or something? After applying the signature try saving the signed file directly to your desktop and see if the problem goes away. That is what worked for me.
At random times when i try to sign the file and save it directly to dropbox the signature does not appear, sometimes if i try to sign again straight after then it is fine, but at other times not. Some times i get exactly the same error as you "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". When that happens i find that if you close the error message boxes and then close the document but do NOT save changes then when you open the document again the signature is infact there on the document, but it will not be validated.
Everytime if I save the signed document directly to my desktop or to a local folder on my hard drive only there is no problem this is what I have to do now, sign and save to desktop and then move the file to the folder where I want it. It would be good if Adobe told ushow to fix this.
I am using Adobe Acrobat XI Pro with Windows 8.1.
Most of the time, the signature was applied to a document that was saved in a drive that it is not located in the computer but in the network. However, we realized that if we save the file in the desktop or any other local folder, the error is decreased... but still was there. Let us say, if we save in a remote drive the error occurs 90% of the times. If the file is saved locally, the error occurs 10% of the times but the error is still there.
Due to every document here in the office is reviewed by every single person in the workflow, all the persons involved in the workflow must sign once they reviewed and approved the document. That means more than 70 docs reviewed by each one daily. Can you imagine now, if we save the doc locally and then "move" them later to the proper folder in the server? That takes you something like 30 secs to a minute searching the path and replacing each doc and, not to mention that this situation opens the doors to errors when someone is going to replace any document by the time they are moving their files.
The way we solved it was upgrading Windows 8.1 to Windows 10. It works perfect now. Also, we found out that the new Adobe Acrobat DC "Reader" allows you to sign the doc easily. So, for those who do not need to modify anything in the document, like adding sheets but they still need to read and approve or sign a doc, we will implement Adobe Acrobat DC Reader for them. Signing a document using the new application is so much easier than the previous versions of the application.
My advise to everyone is if you are experiencing this issue, upgrade your Windows 8 to 10.
Are you by any chance trying to save the file into a network drive or to a place where it might sync to multiple devices like dropbox or something? After applying the signature try saving the signed file directly to your desktop and see if the problem goes away. That is what worked for me.
THANK YOU. Attempting to add a signature and save the file in Dropbox was causing all the problems for me. I took your suggestion, saved to Desktop, then moved to Dropbox and everything worked. I was this close to giving up on working with digital signatures...
That's two Adobe programs I'm aware of now that don't play well with Dropbox currently, the other being Premiere Pro. Here's hoping things get smoother as time goes on.
1 person found this helpful
I had the same issue with Acrobat XI on Mac OS X 10.11.2. I was also trying to save from an open file in Dropbox. Disabling Enhanced Security in the preferences worked around the issue.
FYI, I had this exact issue on OS X 10.11.3 with Acrobat Pro 11.0.13. It ended up being that the PDF that I was trying to sign was inside a folder that had a leading space in it (I did that years ago to make it sort to the top). When I moved the file elsewhere (I put it on the Desktop), it worked fine. Strangely enough, I have been able to sign other PDFs in that same folder with the leading space, so maybe it's an intermittent thing, or something that only particular PDFs experience.
I guess the lesson is to move any troublesome PDFs that are giving this kind of error directly to a standard place like the Desktop and see if they suddenly start working.
I have this problem when trying to save to my desktop.