Although SCOM and SSRS often works seamlessly, recent versions of SSRS 2022 have introduced issues running performance-related reports in SCOM 2022.
A few weeks ago one of our customers running SCOM 2022 has reported an error with Reports in their SCOM 2022 installation. Some of them were working fine while the ones related or linked to Performance were getting “System.ArgumentNullException: Value cannot be null.” error as follows
Date: 8/1/2024 4:18:30 PM
Application: Operations Manager
Application Version: 10.22.10605.0
Severity: Error
Message: Cannot initialize report.
System.ArgumentNullException: Value cannot be null.
Parameter name: GroupList
The environment was running SCOM 2022 UR2 and SSRS version was 16.0.8886.1775 (May 2024). To investigate and recreate the issue we checked our SCOM 2022 installation and realised that we had exactly the same problem which was not there previously. The only change we had done was to update SSRS recently. An action which is not mostly done.
Suspecting the version to be the root cause, we checked another test installation with an older version of SSRS, 16.0.8564.33454 (June 2023) and seen no issues but upgrading this set to latest SSRS version, 16.0.8898.18912 (May 2024), the problem started occurring in this one as well. We have tried to upgrade SSRS to the July 2024 version, and the problem with the performance reports is still there.
We are not able to test every version seperately but it is clear that an SSRS 2022 version in between 16.0.8564.33454 and 16.0.8886.1775 is causing the issue.
Currently we have reported the issue to Microsoft and they are investigating. The only workaround available for now is to use an older version of SSRS 2022 with SCOM 2022.
We advice not to upgrade your SSRS 2022 installation until a fix is released if you have a working set of SCOM 2022 & SSRS 2022.
Also, a problem was introduced in the May 2024 versions of SSRS 2022, that caused a clean install of SCOM Reporting Services 2022 to fail. It seems that using the July 2024 version of SSRS 2022 takes care of that problem. Meaning just the performance reports issue remains from there.
Please check this blog post again as we will update it once a fix or other workaround is released.