Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
When PostgreSQL/AWS password is “11COEde1%23”, but when stored within the registry as a flat text entry, the “%” character is probably not considered during the handshake process. By adding the appropriate ASCII encode “%25”, which is equal to “%”, the connection worked perfectly fine.
By adding the appropriate ASCII encode “%25”, which is equal to “%”, the connection worked
Has anyone ran into this?
Thanks.
Hi @Anonymous ,
Based on my test, I cannot reproduce your issue here.
What type of server do you connect to in the ODBC data source? And what version of Power BI Desktop do you use?
I make a test using SQL Server, everything works well if my login contains % or +. And I am able to import data from the ODBC data source that conatins SQL Server connection in Power BI Desktop 2.76.5678.541 64-bit (December 2019). In your scenario, I would recommend you check if the password is correct, you can also verify if the ODBC connection works in Excel.
Hi @Anonymous ,
Has your issue been solved? If so kindly mark my answer as a solution to close the case. Thanks in advance. Any other question, feel free to let me know please.
That is interesting and should be reported indeed, that sounds like a bug.
Proud to be a Super User!
Check out the September 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.
User | Count |
---|---|
104 | |
98 | |
97 | |
38 | |
37 |
User | Count |
---|---|
152 | |
121 | |
73 | |
71 | |
63 |