Adobe Reader HFT error when signing PDF Documents

I've created a form for work and have been getting this error message sometimes, but not all the time.  The form requires three signatures.  I've been testing out the form by signing all three spots myself.  The second signature spot contains javascript to send an email and make the reset button invisible.  The final signature makes everything read only. 

Is there a solution to the HFT error message???

• We don't use drop box
• There are no hidden files
• I've tried saving it as different file names. (changing 1 or 2 letters or changing the name completely)
• I've tried saving it in different locations.

I don't know if this will help, but the form will be utilized in the following manner:

• Download it, fill it out, sign it, and email to supervisor.
• Supervisor will review and sign it then email to procurement
• procurement reviews and emails it to chief for final signature.

I think I have solved the problem. Microsoft windows indexer service locks file for adobe. The solution for me is to work in an unindexed folder

Hi,

I got the same error when I wanted to sign a PDF form.

I do not have any Dropbox synching.

What helped for me: When you want to save choose another file name.

Best regards

Winfried

We have this issue too and have exhaustively researched every option I can without a fix so far

I have the same issue. And i do not have any dropbox or any other sync going on my laptop. Still i get this error.

Any solution for this?

10 days later and the answer remains the same: A live synch desk top connection appears to be the issue.

I have processed about 30 forms at work, a county government agency, and saved to both a desktop folder and to folders represented by alias from sub-addresses in the server for our Aviation Operations division.

Not one issue with any file NOT saved to Dropbox. Any file saved to Dropbox would bring up the HFT error box and the file would remain open, awaiting a signature. In the background, I could see that a copy of the document had actually been saved to Dropbox. So, I would sign again and make no change in the title to see if I could overwrite - no go. The message was the usual - that file was open and could not be replaced. I would enter any thing - a space, a dash - to the title and it would be saved. When I open the first saved version with the correct title, there is no signature but all other data has been entered. Opening the copy with the modified title would show it signed, but the signature was not valid and I could not validate it.

At home, I just updated the Mac to developer Sierra, 10.12.4 Beta and the iPhone 7 to developer Beta 10.2+ (unlike the Mac, you cannot view the sub numbers). I re-verified the iCloud (a pain!) and about an hour ago, I signed a copy of one of the one-page forms I use at work. Saved to the desktop Documents folder. No issue. I then signed a copy and saved to the Cloud, which, like Dropbox has a live folder in my Users area. No problem. I then signed a copy and saved to Dropbox. After about an hour of the pinwheel and watch icon, it was accepted and the signature is valid.

What may work for Macs apparently will not work for Windows. Also, at home, I use Acrobat DC while at work, Acrobat XI ( and not "Pro").

I consider the issue solved and Dropbox appears to be the issue. Box is another option, but I gave up on them long ago because of price and convenience. Dropbox can be installed on a protected, administered system, much like Chrome and a few other useful tools, without administrator privileges. Considering that I work in the Aviation division of a Government-owned top-20 airport where net security is so tight I can't even modify the look of fonts without permission, I consider adding anything I keep safe to be a victory or sorts.

This may well be a Widows issue with certification to a Dropbox platform, but I have found that NOT SAVING TO DROPBOX IS THE ANSWER FOR ME and apparently others as well.

lloyd

edit: In reviewing all the posts one more time, there are comments about turning off synching. I'm not going to try that because it is not required. If you must have a copy in Dropbox, finish your work and move a copy to that portal. Leaving synching on appears to have no effect if you do not save to Dropbox.

If this is what I believe it is, the following steps should fix it.

>make sure the file is closed

>in windows explorer, navigate to the folder where the document is located.

>change the options to view hidden files

>look for a copy of the file with the icon slightly greyed out.  This is a copy windows uses while you are working on the file.  Changes are made on this hidden file, and only made to the actual file when you click save.

If the copy is there while the file is closed, delete it.  Occasionally the temporary copy does not automatically delete as it is supposed to.

Yes, it is happening to me too, and I don't know why, but I note below that Dropbox may be involved, so I will try to save to a non Dropbox synced location.

Hello all,

We don't use dropbox here.  But we did figure that if the outlook task with the link to the document that needs signing (Original resides on an internal server) was open, AND people had recently upgraded their OS or computer, then the issue was happening.  Closing the task before attempting to sign seems to have solved this.  Not ideal, but a work-around for now. 

Good luck everyone!