Forum Discussion
Unable to Connect to MySQL Database: "Remote Party Has Closed the Transport Stream"
- Anonymous9 years ago
Hi davestasiuk,
I don't think this issue is caused by power bi. Based on research, it seems a like a specify device issue.
Does these issue only appear on specific devices?
If this is a case, I think the issue may related to your hardware driver, mysql software version, OS version and ssl provider.
In addition, I'd like to suggest you to post this to mysql forum to get further support.
Regards,
Xiaoxin Sheng
Hi davestasiuk,
I don't think this issue is caused by power bi. Based on research, it seems a like a specify device issue.
Does these issue only appear on specific devices?
If this is a case, I think the issue may related to your hardware driver, mysql software version, OS version and ssl provider.
In addition, I'd like to suggest you to post this to mysql forum to get further support.
Regards,
Xiaoxin Sheng
- archinate9 years agoRegular Visitor
I have been having the same issue as davestasiuk on this. Re: connecting from PowerBI to a MySQL database.
Tableau, workbench, and even some custom software I am creating are all connecting successfully to the same MySQL database hosted on Azure. When I connect through PowerBI with the same DB credentials, "Remote Party Has Closed the Transport Stream" is given and I am unable to connect.
I have replicated the problem on other machines with fresh installations of PowerBI, etc too.
- archinate9 years agoRegular Visitor
I came to the forum looking for a solution to this exact same problem described by davestasiuk.
I am able to succesfully connect to the same Azure-hosted MySQL DB from Tableau, workbench, and some of my custom software. When I use the same login credentials with PowerBI, I get the same "Remote Party Has Closed the Transport Stream". This is true on other machines I am testing on as well.
Why would PowerBI not let me connect to the Azure DB, but other apps are successful on the same device, with the same creds, and drivers?
- davestasiuk9 years agoNew Member
Yes, it turned out to be related to the MySQLQ Connector.NET version.
- MarkEvansHW8 years ago
Helper II
Any tips on how to solve it? Which version were you using? How did you determine which one to use? I'm having the same issue.
- MarkEvansHW8 years ago
Helper II
Any tips on how to solve it? Which version were you using? How did you determine which one to use? I'm having the same issue.
- Arranafc198 years ago
Helper IV
Did you manage to resolve this ?