Registering an SQL data source using enterprise ga...

camelenchanter · ‎04-17-2018

Hi,

I am trying to add an SQL data source via a data gateway and receive the following error:

I can the access SQL server via another machine or the server on which gateway distalled directly on Power BI desktop but unable to add it to the data source list,

Unable to connect: We encountered an error while trying to connect to xxx.xxx.xxx.xxx:11111. 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
Activity ID:   cafce48b-c9f2-4315-90a5-5f7e38e98646
Request ID:   30f84723-6c4d-4151-cd38-b30ca2006783
Cluster URI:   https://wabi-west-europe-redirect.analysis.windows.net
Status code:   400
Error Code:   DMTS_PublishDatasourceToClusterErrorCode
Time:   Tue Apr 17 2018 16:41:46 GMT+0300 (FLE Daylight Time)
Version:   13.0.5027.161
POWERBI:   Cannot connect to the server.
Underlying error code:   -2146232060
Underlying error message:   A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid)
DM_ErrorDetailNameCode_UnderlyingHResult:   -2146232060
DM_ErrorDetailNameCode_UnderlyingNativeErrorCode:   87

any help is much appreciated

Anonymous · ‎05-02-2018

HI @camelenchanter,

I'd like to suggest you to test connection status of your datasource on device which install the gateway.
According to error message, it seems like your datasource address not available.

Reference link:

Basics first : "UDL Test"

In addition, you can also check your port and firewall settings to ensure power bi can access to datasource through your gateway.

Microsoft Azure Datacenter IP Ranges

On-premises data gateway

Regards,

Xiaoxin Sheng

Anonymous · ‎04-17-2018

I see this message when the account you are using to Authenticate doesn't have access to the database. I would advise you to start looking at the account you are using to make the connection. Make sure you can login via SSMS to the database with the same account.