This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreGet Fabric Certified for FREE during AI Skills Fest. This week only. Secure your voucher now.
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 May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 24 | |
| 24 | |
| 21 | |
| 21 | |
| 18 |
| User | Count |
|---|---|
| 56 | |
| 52 | |
| 49 | |
| 26 | |
| 25 |