Forum Discussion
Refresh failures for PBI dashboard
We are experiencing Power BI refresh failures for one of our Dashboard that connects to SQL Server through the on‑premises gateway using Windows Authentication. This dataset has been refreshing successfully for years.
error "DM_GWPipeline_Gateway_InvalidConnectionCredentials “The credentials provided for the SQL source are invalid (sqlprod03;abc)."
However, the credentials are correct. and tried to reconnect, but failed.
Again, We tried to re authenticate using O-Auth , bt failed and getting the message "A connection was successfully established with the server, but then an error occurred during the login process. SSL Provider: The certificate chain was issued by an authority that is not trusted"
Any insights or suggestions on how to resolve this would be greatly appreciated! Attached error messages and refresh failure messages for referance.
Thank you!
11 Replies
Hello mjoseph111 ,
Please check this: https://learn.microsoft.com/en-us/answers/questions/2157184/ssl-certificate-chain-not-trusted-error-in-sql-ser
Also in power bi service, go to Manage Gateways. Find your SQL Server data source and look for an option to "Trust server certificate" or "Encrypt connections".
If this solved your issue, please mark it as the accepted solution. ✅
Hi mjoseph111 , Thank you for reaching out to the Microsoft Community Forum.
I think the issue is SSL/TLS trust failure during the SQL login handshake as we can see “The certificate chain was issued by an authority that is not trusted” in the error message. Power BI/Gateway often surfaces this as InvalidConnectionCredentials even when the credentials themselves are correct. Since this worked for years, something likely changed recently such as a SQL Server certificate renewal, gateway/driver update, Windows patch or stricter TLS enforcement.
Please check whether the gateway server trusts the SQL Server certificate chain (root/intermediate CA certs), verify the SQL cert has not expired/changed, update the SQL drivers on the gateway machine and test with “Trust Server Certificate” enabled temporarily to confirm the issue. Also worth testing an SSMS connection from the gateway server itself to see if the same certificate warning appears.
Thanks for your response v-hashadapu . We’re in the earliest stages of transitioning from Microsoft ADFS to Microsoft Entra, and when my account was moved over, that’s when these issues began. Initially, several cloud connections broke, but we were able to reauthenticate those. However, this report failure appears to be tied to Windows authentication, and reauthentication isn’t resolving it.
This report also uses linked servers, so I’m not sure whether that’s contributing to the problem or if, as you mentioned, it could be certificate‑related. I’m not very familiar with testing or validating certificates, so if you have any documentation or guidance that could help me check that, I’d really appreciate it.
Hi mjoseph111 , Thanks for the additional context, now I think this is even more likely related to trust/authentication changes introduced during the ADFS -> Entra transition rather than the SQL credentials themselves being wrong.
Since this dataset had been working for years, something in the authentication/TLS chain likely changed when the identity migration started. Linked servers can also make Windows Authentication and Kerberos delegation more sensitive, so they could definitely be contributing here.
Try connecting to sqlprod03 from the gateway server directly in SSMS using the same Windows authentication method. If you see the same certificate warning there, then the issue is outside Power BI and confirms it is a SQL trust/certificate problem.
Also, as suggested before, please check whether the SQL Server certificate changed recently, whether the gateway server trusts the issuing Root/Intermediate CA certificates and whether the gateway machine’s SQL drivers are fully up to date.
Please read below documents for reference:
Encrypt Connections by Importing a Certificate - SQL Server | Microsoft Learn
Certificate Chain Not Trusted After Driver Upgrade - SQL Server | Microsoft Learn
Hi mjoseph111
I have had this issue come up in the past and what it was causing was due To the SQL server having logon triggers and that proposed causing the issue. The work of our advice to use an ODBC connection instead, which would not 'cause the logon triggers to fire.
Hi mjoseph111 , Hope you're doing fine. Can you confirm if the problem is solved or still persists? Sharing your details will help others in the community.
Hi v-hashadapu issue still persisting and im workig with microsoft to resolve it. i will update with the solution once it resolved. also if its any of the solutions you recommanded i will mark it as a solution. Appreciate all your help. Thank you!
Hi mjoseph111 , thanks for the update. If you have any other issues, please fell free to create new posts here in the community. We are always happy to help.
v-hashadapu Sure, Issue still persists and we are still working on it.
Hi mjoseph111 , Thanks for the update. Since the issue is still persisting and the error continues to point to SSL/certificate trust during the SQL login process, this now seems more likely to be an environment or infrastructure level issue rather than a Power BI credential issue itself. Given the ongoing ADFS -> Entra transition and the linked server involvement, it may be worth engaging your SQL Server/IT infrastructure team further and possibly opening a Microsoft Support ticket if the investigation stalls, as they may be able to help isolate whether the failure is coming from gateway trust configuration, SQL Server certificates or related authentication/security changes and solve the issue.
Below is the link to help create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Hi mjoseph111 ,
hope you are doing well.
Just wanted to know if your issue has been resolved through your support ticket with Microsoft? If so, we would greatly appreciate it if you could share the insights here, as they may benefit others with similar issues.
If you have any other queries, please feel free to raise a new post in the community. We are always happy to help. Thank you.
