Forum Discussion
Getting Sys.WebForms.PageRequestManagerServerErrorException error
Hi All,
We have two nodes of Power BI Report Server with scale-out deployent. It was working fine untill last month, users are getting
"sys.webforms.PageRequestManagerserverErrorException: An unknown error occured while processing the request on the server. The status code returned from the server was: 500"
On troubleshooting, found that when more then one user try to run the same report at same time then it is throwing error.
Any suggestion on how to resolve this issue?
Thanks,
Hari
3 Replies
Hi Anonymous ,
Could you share us more details? For example,
1. What's the version and edition of your Report Server and SQL Server?
2. Which server will appear the error? Or both the two servers?
3. For all reports, the same issue will appear? Or just for one specific report?
Best Regards,
Icey
Hi Icey,
Below are the details,
1. What's the version and edition of your Report Server and SQL Server? - Report Server is May 2020 and 2018 SQL Server.
2. Which server will appear the error? Or both the two servers? - happens on both the servers, we are using a load balancing url. Checked with A10 team, no issues found on LB. And they mentioned that application may require some kind of client persistence configured so that a client request is always sent to the same server.
3. For all reports, the same issue will appear? Or just for one specific report? - Error shows up for all the reports. Throws error when multiple users run the same report at same time.
Thanks
Hi Anonymous ,
You can try to upgrade to the latest version: Jan 2022 to check if the issue is still there. Before upgrading, please backup your encryption keys, databases and configuration files.
Reference: Upgrade Power BI Report Server - Power BI | Microsoft Docs
You can also check the log of PBIRS at C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles.
Reference: Reporting Services Log Files and Sources - SQL Server Reporting Services (SSRS) | Microsoft Docs
You can also catch the browser trace with F12->Network. For detailed steps, please check: Collect a browser trace.
Note: For your data security, please don't share your logs here directly.
If all above still can't help you, you can create a support ticket to get further help.
Best Regards,
Icey
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
