cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
luk Frequent Visitor
Frequent Visitor

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

Hi,

I noticed there is a quite few related posts but none with this specific error message. I'm trying to add a data source to my on-premises gateway but getting an 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."

 

Activity ID:0cea33c6-749d-4b4d-9e6a-a3d8e6f16fcc
Request ID:7982f5e7-bbe7-1ba2-62fb-2bd024a01ca4
Cluster URI:https://wabi-us-east2-redirect.analysis.windows.net
Status code:400
Error Code:DMTS_PublishDatasourceToClusterErrorCode
Time:Mon Jan 21 2019 11:03:43 GMT-0500 (Eastern Standard Time)
Version:13.0.8074.169
LSI:Unable to connect to the data source undefined.
Underlying error code:-2147467259
Underlying error message:MySQL: Unable to connect to any of the specified MySQL hosts.
DM_ErrorDetailNameCode_UnderlyingHResult:-2147467259
Microsoft.Data.Mashup.ValueError.DataSourceKind:MySql
Microsoft.Data.Mashup.ValueError.DataSourcePath:usevsimsdb101d.cgukppq7uxqu.us-east-1.rds.amazonaws.com;prod
Microsoft.Data.Mashup.ValueError.ErrorCode:-2147467259
Microsoft.Data.Mashup.ValueError.Message:Unable to connect to any of the specified MySQL hosts.
Microsoft.Data.Mashup.ValueError.Reason:DataSource.Error

 

I used same login credentials, database name and server for setting up personal mode gateway with basic authentication method successfuly - It runs just fine. 

Any idea? 

 

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Community Support Team
Community Support Team

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

@luk,

 

The 400 ERROR means a bad http request. Please updata on-premise gateway to the lastest version. If you already have updated the gateway to the latest version, then you can refer to steps below for troubleshooting.

 

1. Check if the server is using a proxy and the proxy. Some proxies restrict traffic to only ports 80 and 443. By default, communication to Azure Service Bus will occur on ports other than 443.

2. You can force the gateway to communicate with Azure Service Bus using HTTPS instead of direct TCP. You will need to modify the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file. Change the value from AutoDetect to Https. This file is located, by default, at C:\Program Files\On-premises data gateway.

3. Restart the gateway and check if the issue persists. 

  • To stop the service, run this command:

    ''' net stop PBIEgwService '''

  • To start the service, run this command:

    ''' net start PBIEgwService '''

4. You may export the data gateway log by selecting Diagnostics and then selecting the Export logs link near the bottom of the page. Reference: https://docs.microsoft.com/en-us/power-bi/service-gateway-onprem-tshoot#tools-for-troubleshooting.

 

If the issue is very urgent, I would suggest you to create a support ticket to achieve deeper help.

 

Community Support Team _ Jimmy Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

5 REPLIES 5
Super User
Super User

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

If you were to log onto the server that hosts the On Premise Data Gateway, does it have the ability to access this data source?  For example if you loaded in Power BI Desktop to that server, could you open/refresh your PowerBI project from that server?

 


   

              Did I answer your question? Mark my post as a solution!
       

Proud to be a Datanaut!


   


Highlighted
Super User
Super User

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

@luk In addition, what do the log files say on the server for the gateway, do they provide any additional information? 

C:\Users\PBIEgwService\AppData\Local\Microsoft\On-premises Data Gateway\Gateway*.log

Near SE WI? Join our PUG MSBIWI
Community Support Team
Community Support Team

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

@luk,

 

The 400 ERROR means a bad http request. Please updata on-premise gateway to the lastest version. If you already have updated the gateway to the latest version, then you can refer to steps below for troubleshooting.

 

1. Check if the server is using a proxy and the proxy. Some proxies restrict traffic to only ports 80 and 443. By default, communication to Azure Service Bus will occur on ports other than 443.

2. You can force the gateway to communicate with Azure Service Bus using HTTPS instead of direct TCP. You will need to modify the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file. Change the value from AutoDetect to Https. This file is located, by default, at C:\Program Files\On-premises data gateway.

3. Restart the gateway and check if the issue persists. 

  • To stop the service, run this command:

    ''' net stop PBIEgwService '''

  • To start the service, run this command:

    ''' net start PBIEgwService '''

4. You may export the data gateway log by selecting Diagnostics and then selecting the Export logs link near the bottom of the page. Reference: https://docs.microsoft.com/en-us/power-bi/service-gateway-onprem-tshoot#tools-for-troubleshooting.

 

If the issue is very urgent, I would suggest you to create a support ticket to achieve deeper help.

 

Community Support Team _ Jimmy Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

luk Frequent Visitor
Frequent Visitor

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

Yeah, out of power bi desktop I am able to refresh data set. In fact, I have my personal mode gateway set up on the same server and database and it runs scheduled refreshes. 

luk Frequent Visitor
Frequent Visitor

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

 Thanks @v-yuta-msft and @Seth_C_Bauer. It seems like the issue was solved. I was running the refresh out of the virtual machine and so its IP adress needed to be added for the security. Right after that, I was able to add mysql data source.