Forum Discussion
Can no longer connect to MySQL Database (Cloud)
Hello all.
Something strange has happened to my connection to our companies MYSQL database.
Just starting a new document and trying to connect gives me this error:
Details: "An error happened while reading data from the provider: 'Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints.'"
Does anyone know what this means?
8 Replies
- AnonymousNot applicable
Hi Anonymous,
Did this issue appear on a new pbix report or after the refresh on existing power bi reports? It seems like your data structure has changed on your datasource side so that it did not match the data table design rules.
Can you please provide more detailed information to help us clarify your scenario?
How to Get Your Question Answered Quickly
Regards,
Xiaoxin Sheng
- amitchandak
Super User
Anonymous , Make sure you latest driver
https://www.edureka.co/community/41704/how-to-connect-to-mysql-database-from-power-bi
- AnonymousNot applicable
This happens when i try refreshing on exsiting report and when i just try connecting at all on a new report.
Im not sure if the mysql connector has drivers?
there seems to be only one version?
- Watsky
Solution Sage
Anonymous is this only happening in Power BI, or is this occuring outside of Power BI as well?
- Frank_LINew Member
Hi All,
All queries and connections worked fine last Friday with Power Query and MySQL.
We are using below version
And next Monday we found that we are having issue refreshing all power query linked to MySQL database
The error was showing as below. An error heppended while reading data from the provider: 'A call to SSPI failed, see inner exception.'
Then we fixed the issue by untick the Encrypt connections from Data source settings – Edit Permissions
Then we got another error message as below
Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints
And just now we found out that our Manila team can refresh the query with below Microsoft Office Version.
Therefore we assume it may relate to the latest Microsoft update and it’s not agreed to our MySQL server.
By any chance, you would have the same feedback from other clients or you would know how to fix this issue?
Thank you!