Error when refreshing Power BI Desktop

[rhashhab]

ODBC: ERROR [HY000] HTTP status code: 403 Received error: Code: 516. DB::Exception: reem: Authentication failed: password is incorrect or there is no user with such name. (AUTHENTICATION_FAILED) (version 22.1.3.7 (official build))

This error appears to me when I try to refresh data on Power BI desktop.

I'm connecting my Power BI to clickhouse through port forwarding in Visual Studio. 

My collegue connecting to the same connection with same user name and password; she doesn't have the same error I have; everything is working fine with her.

[Thomaslleblanc · Accepted solution]

In the desktop, there are Permission settings. In the desktop, try going to the permission and Clear permission for this pbix file. close and save, then re-open and try the credentials.

[rhashhab]

It worked for me thank you !

[v-echaithra]

Hi @rhashhab ,

Thank you for the update. I just wanted to check if the issue has been resolved on your end, or if you require any further assistance. Please feel free to let us know, we’re happy to help!

Thank you 
Chaithra E.

[Poojara_D12]

Hi @rhashhab 

The error you’re encountering — “ODBC: ERROR [HY000] HTTP status code: 403 … Authentication failed” — indicates that Power BI is unable to authenticate successfully with your ClickHouse database, even though your credentials appear correct. Since your colleague can connect using the same username and password, the issue is likely related to your local environment or connection path, not the database itself. Because you’re connecting through port forwarding in Visual Studio, it’s possible that your forwarded port session has expired, isn’t properly mapped, or is pointing to a different endpoint than your colleague’s. Another common cause is that your ODBC DSN or connection string stores cached credentials or references an older authentication method that ClickHouse rejects. To fix this, first verify that your port forwarding session is active and that the local port matches the one your colleague uses. Then, delete and recreate your ODBC DSN or Power BI connection to ensure it’s not using cached credentials. If the issue persists, try connecting via ClickHouse client or DBeaver using the same credentials — if that works, the problem lies specifically in your Power BI or ODBC configuration.

[v-echaithra]

Hi @rhashhab ,

Thank you @Poojara_D12  for your inputs.

May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.

Thank you.