we couldn't authenticate with the credentials provided. please try again - everyone connecting

[shoselvaraj]

Hi All, 

Recently, our new team member download the powerBI desktop and try to connect with the database. While everyone using the same credentials managed to connect with the database using the same credentials only this person got this error as " we couldn't authenticate with the credentials provided. please try again". 

Troubleshooting steps 

1. Uninstall powerBI desktop 

2. clear the data source setting permissions and re-entered database credentials still the same error 

3. edit the permissions as microsoft account and re-entered database credentials still the same error 

Could you please help me to identify the root cause of the issue? 

[Anonymous]

Hi @shoselvaraj ,

First of all, thank you nandic  for the quick reply. Did the reply help you solve your problem? If so, please mark it as a solution. If not, you can try the following:

You can try to check whether your server name is correct, you can try to use hostname/ip:port to try to reconnect your sql server.

You can also try to use the account and password to test whether you can connect to your sql server; or use a third-party tool (ssms) to test connectivity.

At the same time, I also found a similar connection problem, you can refer to it, I hope this will help you:
Solved: Re: Cannot authenticate credentials when connectin... - Power Platform Community (microsoft....

sql server - we couldn't authenticate with the credentials provided POWER BI - Stack Overflow

Best Regards,

Neeko Tang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

[nandic]

@shoselvaraj this seems more like database access issue than Power BI issue.
Check with database admin if the new user member has same access and roles as all existing users.
If credentials are the same for all users, maybe it requires some kind of whitelisting IP of new user.
But from my side, it is on database or license side, not on Power BI.

Alternative, try doing the same process via Excel instead of Power BI to see if it is up to the tool or database.

Cheers,
Nemanja Andic