Forum Discussion
Gateway configuration on external machine
OK, it looks like you have to check "Skip Test Connection" and go straight to scheduling the refresh in the workspace. It seems that testing the connection during the dataset setup uses different connection algorithms that fail. Oddly enough scheduling the refresh without testing the connection works fine.
Hi gvg ,
What error do you receive when you add the data source to gateway?
Keep the gateway as close to the data source as possible.
If you're planning to use Windows authentication, make sure you install the gateway on a computer that's a member of the same Active Directory environment as the data sources.
Could you please provide more detail about your error?
Best regards,
Community Support Team _ zhenbw
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi,
I get the 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.
However if I try to check mark "Use SSO via Kerberos for DirectQuery And Import queries" my Gateway says 'Connection successful' but refresh fails with the message 'The on-premises data gateway's service account failed to impersonate the user'.
Why should I keep my gateway as close to the data source as possible? This is just for productivity reasons I understand? If I am happy with long refreshes this should not be a problem?OK, it looks like you have to check "Skip Test Connection" and go straight to scheduling the refresh in the workspace. It seems that testing the connection during the dataset setup uses different connection algorithms that fail. Oddly enough scheduling the refresh without testing the connection works fine.