Key with name 'mykey' does not exist in the provider or access is denied. Provider error code: 3113. (Provider Error - No explanation is available, consult EKM Provider for details) RRS feed

  • Question

  • Verified Access Policy permissions using SQL Server Connector Template.  Uninstalled and Reinstalled the latest SQL Connector.  Created the regkey SQL Server.Cryptographic Provider and SQL Server Cryptographic Provider with full permissions to SQL Service login.  Event log shows following error

    The description for Event ID 2 from source SQL Server Connector for Microsoft Azure Key Vault cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event: 

    Vault Name: <vaultnameremoved>
    Operation: getKeyByName
    Key Name: MyTestKey
    Message: [error:113, info:403, state:0] The server responded 403, because the user does not have proper permission to perform the action. Please make sure you have the permission for the specified operation. At minimum,'get, list, wrapKey, unwrapKey' permissions are required.

    Tuesday, April 16, 2019 11:17 PM

All replies

  • Have you given proper permissions to the user on the access policy blade of Azure Key Vault.  
    Wednesday, April 17, 2019 9:47 PM
  • Hello,

    Please let us know if you find above reply useful. If yes, do click on 'Mark as answer' link in above reply. This will help other community members facing similar query to refer to this solution. Let me know if you have any other questions. Thanks

    Monday, April 22, 2019 5:58 AM