Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
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!
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
109 | |
98 | |
80 | |
64 | |
57 |
User | Count |
---|---|
145 | |
110 | |
91 | |
84 | |
66 |