Forum Discussion

DKHUghes55's avatar
DKHUghes55
Resolver I
2 years ago
Solved

Power BI Report Server not Rendering reports. .Net error

Hi Fabric Community,

I have an issue with our Power BI Report Server instance.  We are running September 2023 currently.

The error the users see is Service Unavailable, HTTP 503.

What I see on the server is 

Application: ReportingServicesService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFD86433714 (00007FFD86410000) with exit code 80131506.

 

I have tried a Repair operation to correct the issue then rebooted the server.  It worked for about 2 days then the error returned.

This has my site down at the moment.  Any suggestions?

 

Thanks,

DKHughes55

4 Replies

  • Hi Fabric Community

    Another piece of the puzzle. The Service Unavailable issue is only with the pagenated reports.  The Power BI Reports work fine on the server.

     

    Thanks,

    DKHughes55

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi, DKHUghes55 

    Ensure that the report server's application pool is running. Sometimes, the application pool may stop, resulting in a 503 error. Make sure you have the latest version of the .NET Framework installed. Some users have solved similar issues by updating to the latest version. You can refer to the following post:

    Solved: HTTP Error 503. The service is unavailable - Microsoft Fabric Community


    There may be an issue with SSL certificate binding. Updating the web service URL and web portal URL in Reporting Services Configuration Manager can be helpful to others. You can check the following post:

    Solved: Report Server January 2024 - HTTP Error 503. The s... - Microsoft Fabric Community


    Verify that the service account running the Power BI Report Server service is the same as the one configured in Report Server Configuration Manager.

    HTTP Error 503. The service is unavailable in Power BI - deBUG.to

     

    How to Get Your Question Answered Quickly

    Best Regards

    Yongkang Hua

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

    • DKHUghes55's avatar
      DKHUghes55
      Resolver I

      Hi v-yohua-msft,

      There were a couple of things causing the issue.  One of them was the cert binding on the web service URL.  The other issue was the server was patched/updated on Sunday night and there was a microsoft installer stalled on a few .Net modules.  All is well now.  

      Thank you for the help.  

      I will mark this as an accepted solution.

       

      DKHughes55

  • Hi Fabric Community,

    We found the issue.  There was a setting in th McAfee configuration that was blocking some .Net operations.  This was the setting: AMSI unchecked policy.

     

    This has been resolved.

    DKHughes55