There was an error in the data gateway

[CIGRK]

Hello,

I'm getting an error when trying to set up a connection to my gateway.  The error is:

Unable to create connection for the following reason: There was an error in the data gateway.

It's not real helpful so I was looking at Event Viewer and I found this under Security:

Audit Failure - Event ID 5061

Cryptographic operation.

Subject:

Security ID: NT SERVICE\PBIEgwService

Account Name: PBIEgwService

Account Domain: NT SERVICE

Logon ID: 0x47739FD

Cryptographic Parameters:

Provider Name: Microsoft Software Key Storage Provider

Algorithm Name: RSA

Key Name: OdgAsymmetricKey

Key Type: User key.

Cryptographic Operation:

Operation: Decrypt.

Return Code: 0xC000000D

I've reinstalled a number of times now.  I'm trying to set the connection up to SQL Server using a Windows account.

[Mauro89]

Hi @CIGRK, 

I never came across such an error message but here are some troubelshooting ideas which came into my mind:

1. Reset gateway encryption keys

1. Uninstall the gateway completely
2. Delete the gateway folder: C:\Program Files\On-premises data gateway
3. Delete registry keys:
   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\On-premises data gateway
4. Restart the computer
5. Reinstall the gateway fresh
6. During installation, note the recovery key - save it securely

2. Check antivirus/encryption software

Some antivirus or disk encryption software might interferes with the gateway's cryptographic operations:

• Temporarily disable antivirus

Best regards!

PS: If you find this post helpful consider leaving kudos or mark it as solution

[CIGRK · Accepted solution]

Thanks.  I actually just got it fixed.  I just re-created a brand new on-prem gateway vs using the recovery key after reinstall.  Copilot gave me a reason why that is, but I would have thought a recovery would have restored any keys needed to create a valid connection.  I'm new to all this and learning though.

[v-shchada-msft]

Hello @CIGRK,

We appreciate your effort and are glad to hear that your issue has been resolved. Your update will also help other community members address similar issues more efficiently.

Thank you.