I admit I was wrong about the source of the problem. I also discovered the problematic certificates make MS Outlook crash as well when trying to attach a digital signature to an email. What became immediately clear after installing the new certificates from Symantec (formerly Verisign which ironically was one of the problematic certificates the other from Comodo) was a prompt for a pin before affixing a signature. Unless Acrobat became more selective in what certificates it plays well with in the most recent version, something must have gone wrong in the export/import of the problematic certificates. Having installed new digital certificates this morning, I discovered the problem was the certificates I was using rather than Acrobat. Moreover, yet another ticket number was created. I received yet another unintelligent email asking for yet another statement of the problem. I phoned and explained that the email reply does not amount to support and was assured I would get a call back. I received a reply email with a link to their generic site and there are no relevant FAQs or results on its search engine. "Support" at EchoSign this far has been nonexistent. End task is the only option which means the signature will always be invalidated.
Keep getting the spinning circle and message that Acrobat is not responding. Also tried to sign a document without any form fields and that failed too. Same result when trying to sign the new form created with EchoSign. Opting to reinvent the wheel by using Echo sign to create form fields anew was also a waste of time. I appreciate the rapid response but I already deactivated, uninstalled and reinstalled Acrobat Pro XI so it is unlikely the repair function would be of any use.Īs to Echo sign, when I tried to use it as opposed to "work with a certificate" I received a message that some of the fields on a particular form were not compatible.
0 kommentar(er)
