Skip to main content
C
creativeclient
Participant
March 17, 2020
Answered

Windows Cryptographic Service Provider Error when attempting to digitally sign in acrobat 2017

  • March 17, 2020
  • 1 reply
  • 4050 views

I am attempting to digitally sign a document with Acrobat 2017 (updated version, 17.011.30166). The operating system is Windows 10 Enterprise x64. Previously there was installed Acrobat DC on the system, which was completely uninstalled and machine was rebooted before Acrobat 2017 was installed instead.

 

When signing I am getting the follwing error: The Windows Cryptographic Service Provider reported an error: The requested operation is not supported. Error Code 50. 

 

Under trust tab for particular certificate, the image looks as given below. Also, I have unchecked "use modern interface for signing" under application preferences / signatures / creation and apperance and that did not help. (With "modern interface"  option there was no error message but the button "sign" was not resulting in anything and after reading through forums I could see that unchecked option might help. After unchecking I was able to see the error). 

 

Are there any ideas for what might cause the error? 

 

Thanks in advance. 

 

This topic has been closed for replies.
Correct answer creativeclient

I will mark my question as solved. It turned out that the issue was not in Acrobat, but instead in outdated software accompanying digital signature. Hence, after updating the software (enabling AES-256 encryption) I was able to sign PDF files. For my Danish fellows who might have similar issues and who are using local digital signature provider I will direct them here.

1 reply

C
creativeclientAuthorCorrect answer
Participant
March 18, 2020

I will mark my question as solved. It turned out that the issue was not in Acrobat, but instead in outdated software accompanying digital signature. Hence, after updating the software (enabling AES-256 encryption) I was able to sign PDF files. For my Danish fellows who might have similar issues and who are using local digital signature provider I will direct them here.

    N
    Niels Dybdahl
    Participant
    May 23, 2020

    I have the same problem and I have installed the latest software from https://www.nemid.nu/dk-da/kom_i_gang_med_nemid/sikker_e-mail/signering_af_dokumenter/

    Do you have any hints on which other parts of the software needs update in order to enable AES-256?

      kimljac @ DGC
      kimljac @ DGC
      Participant
      November 24, 2021

      Removing the old version and installing from https://www.nemid.nu/dk-da/kom_i_gang_med_nemid/sikker_e-mail/send_og_modtag_sikker_e-mail/installation_paa_windows/ solved my problem. Thanks a lot Niels.

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices