Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
Hi everyone,
I'm encountering an issue when trying to publish my report to Power BI Report Server (January 2025 version).
The report uses a SQL Server database with Basic Authentication. When I attempt to publish, I receive the following error message:
Error Message:
An unexpected error occurred.
Please try again later or contact support. If you contact support, please provide these details.
We couldn't connect to the Analysis Services server. Make sure you've entered the connection string correctly.
I've already double-checked the connection string and credentials. The report works fine in Power BI Desktop, but the error appears when publishing to the Report Server.
Has anyone else experienced this issue or knows what might be causing it?
Thanks in advance!
Solved! Go to Solution.
Hi @kharisma25 ,
Thank you for reaching out to us on the Microsoft Fabric Community Forum.
Please check the below things.
1. Credential Settings in Report Server
Even though the report works in Power BI Desktop, the Report Server needs stored credentials to access the data source (especially for Basic Auth).
Steps to fix: Open Power BI Report Server Web Portal. Find your report, click the ellipsis (•••) > Manage. Go to Data Sources. Make sure the connection string is correct.
Select Authentication type as Basic and Provide username and password & Check "Use as Windows credentials" if required (depending on your SQL Server setup).
2. Unsupported Authentication Method (Basic Auth)
Power BI Report Server has limited support for Basic Authentication in data source connections, especially with certain security settings.
Steps to fix: Try switching to Windows Authentication or use stored credentials if possible. Consider creating a SQL Server user with limited access just for report access and store its credentials.
3. Gateway/Service Account Permissions
The Power BI Report Server runs under a service account, which must have access to the SQL Server.
Steps to fix: Check what you have running the Power BI Report Server Windows Service (PBIRS). Ensure that you has at least read access to the SQL Server database you're querying.
4. Network Issues (shown in browser bar)
The browser bar shows "You must log in to this network before you can access the Internet" — indicating a captive portal or proxy login (common in corporate networks or guest Wi-Fi).
Steps to fix: Connect the server to the internet/network properly. Authenticate via the "Open network login page" prompt.
Ensure DNS resolution and SQL Server name/IP is reachable from the Report Server.
5. Check Analysis Services Connection Setting
If your report has live connection to SSAS (SQL Server Analysis Services), ensure The SSAS instance is accessible from the server. The credentials used have permissions.
Please refer community thread.
Solved: After January 2025 upgrade: We couldn't connect to... - Microsoft Fabric Community
If my response has resolved your query, please mark it as the "Accepted Solution" to assist others. Additionally, a "Kudos" would be appreciated if you found my response helpful.
Thank you
Hi @kharisma25 ,
Thank you for reaching out to us on the Microsoft Fabric Community Forum.
Please check the below things.
1. Credential Settings in Report Server
Even though the report works in Power BI Desktop, the Report Server needs stored credentials to access the data source (especially for Basic Auth).
Steps to fix: Open Power BI Report Server Web Portal. Find your report, click the ellipsis (•••) > Manage. Go to Data Sources. Make sure the connection string is correct.
Select Authentication type as Basic and Provide username and password & Check "Use as Windows credentials" if required (depending on your SQL Server setup).
2. Unsupported Authentication Method (Basic Auth)
Power BI Report Server has limited support for Basic Authentication in data source connections, especially with certain security settings.
Steps to fix: Try switching to Windows Authentication or use stored credentials if possible. Consider creating a SQL Server user with limited access just for report access and store its credentials.
3. Gateway/Service Account Permissions
The Power BI Report Server runs under a service account, which must have access to the SQL Server.
Steps to fix: Check what you have running the Power BI Report Server Windows Service (PBIRS). Ensure that you has at least read access to the SQL Server database you're querying.
4. Network Issues (shown in browser bar)
The browser bar shows "You must log in to this network before you can access the Internet" — indicating a captive portal or proxy login (common in corporate networks or guest Wi-Fi).
Steps to fix: Connect the server to the internet/network properly. Authenticate via the "Open network login page" prompt.
Ensure DNS resolution and SQL Server name/IP is reachable from the Report Server.
5. Check Analysis Services Connection Setting
If your report has live connection to SSAS (SQL Server Analysis Services), ensure The SSAS instance is accessible from the server. The credentials used have permissions.
Please refer community thread.
Solved: After January 2025 upgrade: We couldn't connect to... - Microsoft Fabric Community
If my response has resolved your query, please mark it as the "Accepted Solution" to assist others. Additionally, a "Kudos" would be appreciated if you found my response helpful.
Thank you
Hi @kharisma25 ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Thank you.
Hi @kharisma25 ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Thank you.
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Thank you.