Paginated Report throws Sys.WebForms.PageRequestManagerServerErrorException (503 Error)

[MORATHO]

Hello,

I am facing the problem that my paginated reports are returning the following error: Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned by the server was: 503

The event log shows the following error:

Application: ReportingServicesService.exe
Framework version: v4.0.30319
Description: The process terminated due to an internal error in the .NET runtime at IP 00007FFC343C5A7B (00007FFC342A0000) with exit code 80131506.

Further analysis has shown that this behavior occurs after applying patches KB 5050182 and KB5050008 (reverting the patches results in a working environment).

We have the problem with 2 Versions of PBIRS:

Version1.22.9153.7886(Januar 2025) 

Version1.20.8944.34536(Mai 2024) --> Running smoothly since months till we applied the patch. After this we have the same issue

[MORATHO · Accepted solution]

Hello, here an update:

It looks like the trellix endpoint security service was the reason. We created a policy to exclude the directory "C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer".
Now it works

[Poojara_D12]

Hi @MORATHO 

The Sys.WebForms.PageRequestManagerServerErrorException (503) error in Power BI Report Server (PBIRS) occurs after applying patches KB5050182 and KB5050008, causing the ReportingServicesService.exe process to crash due to a .NET runtime issue (exit code 80131506). Reverting the patches restores functionality, indicating a compatibility issue introduced by the updates. Since the May 2024 version (1.20.8944.34536) has been running smoothly, the problem likely affects newer builds. To address this, you can rollback the updates, check Microsoft forums for known issues, and verify if the .NET Framework version has been impacted. Restarting PBIRS and reviewing logs (C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles) may provide more insights. If necessary, contact Microsoft Support for guidance or wait for a future patch to resolve the issue. Testing updates in a non-production environment before applying them in production can help avoid similar disruptions in the future.

 

[MORATHO]

Hello,

oh, SSRS 2024 ran smoothly until the patches came out. Now also the Mai 2024 version causes the same issue.

We are forced to update the server so not applying the Server Patches ar ento an option

The logs (C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles) have no entry for the requests which are causing the error. This make sense, since the whole service is crushing (out of the windows Event logs)

Greetings

[MORATHO]

Hello,
maybe the situation was not that clear.

We have the issue on both SSRS Environmente (Mai 2024 and January 2025).
I just meant that the May 2024 version ran fine until this patches.

Greetings

[v-jtian-msft]

Hi,@MORATHO .Thank you for your reply.
It looks like the problem is caused by an incompatibility between the new version and the version you specified with the patch. I suggest you create a support ticket to report this issue and get more help.

[MORATHO]

Hello,

it seems that the link you provides is not working

[v-jtian-msft]

Hi,@MORATHO .I am glad to help you.

Based on the log information you provided:
The issue mentioned in the logs occurs after applying patches KB 5050182 and KB5050008, and rolling back these patches restores normalcy. This indicates that these patches may have introduced changes that are incompatible with your environment.

This suggests that the earlier version (1.20.8944.34536) was stable over a long period of time, whereas the newer version (January 2025) had problems after applying the patches, which may indicate that the newer version or patches introduced incompatible changes
You can try rolling back SSRS to an even older version (rather than the latest version) to see if that solves the problem.
URL:
Upgrade and migrate Reporting Services - SQL Server Reporting Services (SSRS) | Microsoft Learn

If the above still doesn't help you, you can create a support ticket for further help (maybe the problem is that the new version is not compatible)

It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

URL:

Microsoft Fabric Support and Status | Microsoft Fabric

I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[MORATHO]

I created a support ticket and I'm currently in exchange with MS support.

[v-jtian-msft]

Hi,@MORATHO .
Thanks for sharing, I'll be following up on this issue.