We could not register this data source for any gateway instances within this cluster.

[caseycook]

While attempting to add a new SQL Server datasource to our On-Prem gateway I received the following error message:

Unable to connect: We encountered an error while trying to connect to . Details: "We could not register this data source for any gateway instances within this cluster. Please find more details below about specific errors for each gateway instance."Hide details

Error Code: DMTS_PublishDatasourceToClusterErrorCode

Underlying error message: Error occurred while decoding OAEP padding.

I have:

• Verified that the credentials have access to the database.
• Restarted the gateway
• Used sysadmin credentials
• Updated to July realase of Gateway

I have the gateway logs available.   However, I don't see a way to attach them here.

[caseycook]

Sorry for the late response.  I ended up reaching out to Microsoft support.  They had to restart our environment.

[djrome13]

Casey,

Did you find a resolution for this? We are experiencing it as well. Thanks!

[v-piga-msft]

Hi @caseycook,

Was on-premise data gateway installed on the same machine as SQL Server database hosted?

If it is convenient, please upload a screenshot for your details error message, so that I could find the cause for this issue.

For reference, you could have a view of this similar thread which has been solved.

Best  Regards,

Cherry

[caseycook]

No, gateway is not on the same SQL server.  However, existing connections are still pulling data.

[v-piga-msft]

Hi @caseycook,

As SQL Server and on-premise data gateway exist on different machines, can you verify from the machine host the data gateway can access the SQL Server Database, make sure those two machines can communicate each other. 

Also check if your network requires proxy, if it does, please follow this article to finish settings.

Best Regards,

Cherry

[RMDNA]

Hi @caseycook,

If you want to share files, put them in Google Drive/Dropbox/OneDrive and post a download link.