Get certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now
Solved! Go to Solution.
Update:
After making a lot of attempts and failures I finally got it solved and I found what was the problem.
Before the lastest update (January 2018) there were 3 login methods when connecting to SQL database:
Back then, I used to login using Organizational Account option.
Now, with the latest update the third option changed to: "Microsoft Account". So when I tried to login using this method, the validation proccess failed. Now, if I use the first option... voilà! I am able to connect to my organizational SQL server again!
It would be nice if someone could add some information about this change. I searched the web and I didn't find anything.
Greetings!
Wanted to add that there is a new issue we received a fix from MS from, looks fairly recent (starting Feb 13 2024). We were getting "certificate chain not trusted" errors on servers for Power BI Reports that previosuly worked no issue, no change anywhere.
Documented here, search "PBI_SQL_TRUSTED_SERVERS": https://learn.microsoft.com/en-us/power-query/connectors/sql-server
Can confirm after 3 days of trial and error, adding this environment variable (PBI_SQL_TRUSTED_SERVERS) to "Environment variables for your account" with the problem server name did the trick. I did have to clear out the Connection data (File > Options and Settings > Data source settings - select DB and Clear Permissions). Then add the data source back.
Adding this to all the top Google hits to hopefully save others the pain.
thanks for the link your the best. Others answers are **bleep**
It also worked for me. Thanks for sharing!
Update:
After making a lot of attempts and failures I finally got it solved and I found what was the problem.
Before the lastest update (January 2018) there were 3 login methods when connecting to SQL database:
Back then, I used to login using Organizational Account option.
Now, with the latest update the third option changed to: "Microsoft Account". So when I tried to login using this method, the validation proccess failed. Now, if I use the first option... voilà! I am able to connect to my organizational SQL server again!
It would be nice if someone could add some information about this change. I searched the web and I didn't find anything.
Greetings!
Awesome. Thank you for the post and solution!
How were you able to get that menu screen to select the options for signing in again? I'm stuck in a loop of it just giving me the error message and I can either edit and/or retry and it will just continue to fail and I do not get the option to change my login method.
Go to Power Query Editor ->Data Source Settings(on the Ribbon) -> Edit preferences->Edit Credentials->Choose Windows credentials to access the database
Actually it was working fine with Microsoft Account (and multifactor authenication on Office365) up to when i updated to the latest version (March 2019). I also had to change my password around the same time.
I reinstalled the prior PBI version, but the issue persisted.
So i'm not sure if it's related to the PBI version or it's due to the password change that wasn't correctly synched with Office365.
Switching to Windows Account solved it.
Check out the October 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.
User | Count |
---|---|
112 | |
95 | |
91 | |
82 | |
69 |
User | Count |
---|---|
161 | |
126 | |
121 | |
109 | |
95 |