ConfigMgr Upgraded, Standard reports not working now

Question

We upgraded SCCM to the latest version. The PowerBI Reporting Services was failing with a SRSResource not found. Removed Site Reporting from the DB server, re-added it. rssrvpolicy.config was edited to account for SRSResource.dll path. Once we removed then re-added the site reporting the rssrvpolicy.config was missing the SRSResource assembly entry and the Registry Keys for SRSRP are missing

Subsequent removals and additions of Reporting Site for DB Server have yielded poor results. We noticed that the ConfigMgr Site Reporting software was iterating through the drives. Started with C and has now gone through all the drives. We do not know why. Custom reports that don't use RBAC work.

When looking at Reports on the report server through the browser a generic error appears.

Exception of type 'Microsoft.ReportingServices.ReportProcessing.ReportProcessingException' was thrown. (rsProcessingError)

When going to "Manage" and clicking on parameters another generic error pops up.

An error has occurred. Something went wrong. Please try again later.

Logs are unhelpful as they event viewer shows an error but with 0 details as to what it is.

Environment:
ConfigMgr App Server:

• OS: Windows Server 2022 Datacenter Version 21H2, Build: 20348.1487 Installed RAM: 24 GB Processor(s): 2 - 2.59 GHz Sockets , 4 vCPU

ConfigMgr DB Server:

• OS: Windows Server 2022 Datacenter Version 21H2, Build: 20348.1487 Installed RAM: 72 GB Processor(s): 8 - 2.20 GHz Sockets, 16 vCPU
• SQL Server: SQL Server 2019 Enterprise Edition CU 18
• Power BI Report Server - SQL Server Enterprise with Software Assurance Build: 15.0.1111.115 Report Server Mode: Native

Answer 1

Did you turn on remote error for pbrs? Or did you browse the reports on the pbrs server?

If custom reports that don't use rbac, work then the problem is with the dll / rbac detections. Exactly what account is running pbrs, is it a virtual account?

Answer 2

Hi,

Thank you for posting in Microsoft Q&A forum.

Here is a similar thread for your reference:

Configmgr Reports Leveraging SrsResources.dll display #Error instead of localized error descriptions

(Please Note: Since the website is not hosted by Microsoft, just for your reference.)

Thanks for your time. Have a nice day!

Best regards,

Simon

---

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.