Failed to connect to AS

[jcaballe_1]

I currently have a server running PBIRS Version 1.25.9558.32914 (January 2026), and I'm experiencing this type of error on several dashboards during automatic refreshes. "

Failed to connect to AS

"

What could be the problem? The server resources aren't overloaded, as I've monitored the CPU and RAM usage during these refreshes.

What can I check, given that this is happening so frequently?

[v-ssriganesh]

Hello @jcaballe_1,

We hope you're doing well. Could you please confirm whether your issue has been resolved or if you're still facing challenges? Your update will be valuable to the community and may assist others with similar concerns.

Thank you.

[v-ssriganesh]

Hi @jcaballe_1,

Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to @Juan-Power-bi for sharing valuable insights.

Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.

Thank you for being part of the Microsoft Fabric Community.

[Juan-Power-bi · Accepted solution]

"Failed to connect to AS" means PBIRS can't reach its internal Analysis Services instance during refresh. Since CPU/RAM look fine, the usual culprits are:

The AS service (PowerBIReportServer) restarting or becoming temporarily unavailable during concurrent refreshes
A port conflict or firewall rule blocking the internal AS connection
The refresh schedule overlapping — too many reports refreshing simultaneously overwhelming the AS instance even if the OS-level CPU looks okay

Check the PBIRS logs at C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles for more detail around the failure times. Also look in Windows Event Viewer for any Analysis Services service crashes or restarts coinciding with the errors. If it's happening on multiple reports at similar times, staggering the refresh schedules is a quick first test.