Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
I'm trying to connect to our MySQL database via PBI Desktop (Version: 2.112.1161.0 64-bit (December 2022) using the MySQL connector. I'm able to make an intial connection but then get the "A call to SSPI failed, see inner exception" error. I'm able to access the server with no issues in MySQL Workbench using the same credentials. Searching the forom I found what appears to be a solution here: "A call to SSPI failed, see inner exception" -> HE... - Microsoft Power BI Community.
I've unchecked the Encrypt Connection option, clicked the OK button, then close. But....then what? If I go back to Get Data and select MySQL again, it's forgotten I made that change and I get the SSPI failed error again. Is there something in File > Options and settings I need to enable/disable?
Solved! Go to Solution.
Thanks Amit. I had cleared the permissions and tried again but got the same error. The issue is apparently related to using Get Data in the home ribbon after clearing permissions and unchecking the Encrypt Connection option - PBI apparently thinks you're trying to open a new connection and ignors those altered settings. The workaround - in this case anyway - was to just launch a new query in PowerQuery after unencrytping the connection and not using the Get Data option in the home ribbon.
Thank you.
@THar01 , Clear Permission under Data source setting and try.
Also, make sure you have installed the latest version of .net driver
Thanks Amit. I had cleared the permissions and tried again but got the same error. The issue is apparently related to using Get Data in the home ribbon after clearing permissions and unchecking the Encrypt Connection option - PBI apparently thinks you're trying to open a new connection and ignors those altered settings. The workaround - in this case anyway - was to just launch a new query in PowerQuery after unencrytping the connection and not using the Get Data option in the home ribbon.
Thank you.
User | Count |
---|---|
123 | |
70 | |
67 | |
58 | |
53 |
User | Count |
---|---|
183 | |
92 | |
67 | |
62 | |
52 |