Forum Discussion

mrusu's avatar
mrusu
Advocate II
6 months ago
Solved

Experiencing random refresh errors after upgrading to Power BI RS January 2026

After we upgraded to January 2026 Report Server we started getting a random error with refresh schedules: “Failed to connect to AS” It can happen with any report, totally random, but when manually t...
"Need Help"
"Power BI Report Server "
  • V-yubandi-msft's avatar
    V-yubandi-msft
    6 months ago

    Hi mrusu ,

    I understand how frustrating this situation must be, especially since refresh reliability is important and everything worked well before the January 2026 upgrade. Given that the issue began after the update, occurs randomly across different reports, manual refresh is successful, and changing the timeout hasn’t helped, it doesn’t seem like a misconfiguration on your end. It’s possible the new build introduced this problem.

     

    At this stage, I don’t think it’s necessary for you to continue troubleshooting locally. I recommend submitting a Microsoft Support ticket so their team can investigate further. If it’s a build issue, that’s likely the fastest way to resolve it.

    Link:Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn

     

    Thank you for your patience with this.

    Regards,
    Yugandhar

mrusu's avatar
mrusu
Advocate II
6 months ago

Hi Yugandhar,

 

Thank you for your help. Note that the error is random and most of the refreshes work correctly. The hour when it occurs is also random, can be early morning or noon. Also, not specific to one report only, seems to happen with any of them.

 

I can see this kind of log entries in file RSPowerBI_2026_02_13_09_35_30.log:

 

2026-02-13 13:00:59.6288|ERROR|20|Error Processing Data Model Refresh: SessionId: ffbfd4b9-819b-46d2-b676-d5ab7d0f8010, Status: Error Failed to refresh the model, Exception Microsoft.PowerBI.ReportServer.AsServer.AsConnectionException: Failed to connect to AS ---> Microsoft.AnalysisServices.ConnectionException: A connection cannot be made. Ensure that the server is running. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

 

Regards.

  • V-yubandi-msft's avatar
    V-yubandi-msft
    Community Support
    6 months ago

    Hi mrusu ,

    Thanks for providing the log details this is very helpful.  The error message (connection forcibly closed by the remote host) suggests that the connection to Analysis Services is being interrupted during certain scheduled refreshes. Since the issue is random, affects different reports, and manual refreshes succeed, it likely isn’t a report specific problem. It may be related to temporary server, network, or resource issues.

     

    Could you check the following on the Analysis Services side around the time of the failure

    1. Any restarts or brief downtime of the AS service

    2. CPU or memory spikes on the server

    3. If multiple refreshes are scheduled together, try spacing them out

    These checks should help determine if the connection is being dropped due to server resource constraints or short interruptions.

     

    Please review and let us know what you find so we can proceed.