How to fix no reporting after installation of SCOM 2022 UR4?

Question

How to fix no reporting after installation of SCOM 2022 UR4?

anthony strother 586

Reporting categories are present, however no reports exist when selection any of the categories.

Selecting Administration/Operations Manager Products, Management Servers, Operations Console, Reporting Servers and Web Servers all show:

Update Rollup 4 Patch

KB5120166

Version: 10.22.12369.0

Installed this fix an issue where when adding Linux Servers via the Discovery Wizard, the process would error out.

This resulted in the opening of a support ticket with Microsoft. TrackingID#2608170040004708

The MS person told me that this issue was to fixed in the newly released SCOM 2022 UR4.

Assistance is greatly appreciated.

Tony

0 comments

3 answers

Your answer

Answer 1

Thank you for all the suggestions!

How did you get that to come up in a web browser to see and change that? Is that what is available with SSRS 2022?

I removed and reinstalled both SCOM Reporting and SSRS. Restarted the servers, waited until the next day.

Reinstalled SSRS 2019,v15.0.9395.19445 configured it, then reinstalled SCOM Reporting. Restarted.

After a couple of hours, all the report categories/reports began appearing. That was two days ago.

This morning I logged on, checked SCOM Reporting on BOTH SCOM 2022 Q and SCOM 2022 Prod, no categories or reports????

So confused!!

Tony

Answer 2

anthony strother 586

If these mp's are not present where would I obtain them to import them?

Manually verify or import the reporting management packs UR4 includes updated reporting-related MPs such as:

Microsoft.SystemCenter.DataWarehouse.Library.mp
Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
Microsoft.SystemCenter.DataWarehouse.Reports.mp
Microsoft.SystemCenter.OperationsManager.Reports.2007.mp

SChalakov 10,861 Reputation points MVP Volunteer Moderator

2026-09-14T07:25:10.68+00:00
Hey Tony,

did you already follow this one:

Operations Manager reports fail to deploy

If this is not the issue, then you need to check if the Data Source, which needs to pont to your Data Warehouse is present in the config of the Reporting Services:

You can check the data source for System Center Operations Manager (SCOM) Reporting Services by accessing the SQL Server Reporting Services Web Portal (typically http://<servername>/reports or http://<servername>/reports_instance).

Steps to Check and Verify the Data Source

Open the SSRS Web Portal:

Open your web browser and navigate to your SCOM Reporting Services URL (http://<servername>/reports). Log in with administrator privileges.

Navigate to the Data Source:

Browse through the folders to locate your SCOM reports (usually under the OperationsManager or custom folders).

Look for the shared data source item (commonly named something like Data Warehouse Main or similar connection objects).

Manage Data Source Properties:

Click on the details view or click the ellipsis (...) / drop-down menu next to the data source and select Manage.

Select Data Sources or look at the configuration settings on the left pane.

Review Connection String Details:

Verify the Data Source Type is set to Microsoft SQL Server.

Check the Connection string field. For SCOM, it typically follows this format: data source=<DBINSTANCE or Listener>;initial catalog=OperationsManagerDW;Integrated Security=SSPI

Verify the credentials or integrated security settings are correct, and click Test Connection to ensure it successfully reaches the SCOM Data Warehouse database.

Also, do you get any errors when restarting the SSRS service?

Regards

Stoyan
anthony strother 586 Reputation points

2026-09-14T13:14:52.2966667+00:00

I will do that today. Thank you.
anthony strother 586 Reputation points

2026-09-15T13:58:58.48+00:00

I cannot find anything similar to what you mentioned.....
SChalakov 10,861 Reputation points MVP Volunteer Moderator

2026-09-16T07:56:10.33+00:00

Hi Tony,

in this article of Blake you will find a screenshot of what I meant:

https://blakedrumm.com/blog/scom-db-move-tool/?utm_source=chatgpt.com

I had the issue that the Connections string was missing and I had to rebuild it.

Regards
Stoyan
anthony strother 586 Reputation points

2026-09-16T13:59:48.45+00:00

Thank you. I do not see any of that. Seems most everything is missing, even the reports I created and scheduled! Going to see if I can find a way to uninstall SCOM 2022 Reporting and reinstall it. Perhaps that will fix the issue?

Thanks again for your time and assistance!

Tony
anthony strother 586 Reputation points

2026-09-16T14:24:45.09+00:00

Yes sir, tried all of those, thank you.

Going to see if I can find any articles on how to uninstall and reinstall SCOM Reporting, perhaps that will fix the issue.

Tony
SChalakov 10,861 Reputation points MVP Volunteer Moderator

2026-09-18T08:27:27.0733333+00:00

Hi Tony,

you can do that for sure and most probabyl it will fix the issue, but you will lose your created and scheduled reports. :(
You could try to chose and existing reporting DB (where your custom and scheduled reports are) after the re-install, but from my experience the SSRS is so "fragile" that most of the times this does not work.

Regards

Stoyan
anthony strother 586 Reputation points

2026-09-18T15:41:02.68+00:00

Do you know if there is a document that covers doing this? I have searched and come up empty.

Thank you,

Tony
anthony strother 586 Reputation points

2026-10-05T15:34:52.4933333+00:00

Here is what I see after uninstalling and reinstalling SSRS and SCOM Reporting:

<DataSourceDefinition>

<Extension>SQL</Extension>

<ConnectString>data source=dot-sqlq06\scom;initial catalog=OperationsManagerDW;Integrated Security=SSPI</ConnectString>

<UseOriginalConnectString>False</UseOriginalConnectString>

<OriginalConnectStringExpressionBased>False</OriginalConnectStringExpressionBased>

<CredentialRetrieval>None</CredentialRetrieval>

<Enabled>True</Enabled>

</DataSourceDefinition>

Answer 3

For SCOM 2022 UR4, one documented fix is “Management Packs not updated/imported after install.” If reporting categories are present but the reports themselves are missing after UR4, the first corrective path is to make sure the reporting management packs were actually imported successfully.

Use this order:

Verify UR4 is installed on the reporting-related roles
- Management Server
- Reporting
- Web Console / Console as applicable
- UR4 version shown in the environment should be 10.22.12369.0.
Reapply the correct UR4 MSP packages from an elevated command prompt Apply the MSP that matches each installed role:
- KB5120166-amd64-Server.msp
- KB5120166-amd64-Reporting.msp
- KB5120166-amd64-Console.msp
- KB5120166-amd64-WebConsole.msp
The update guidance states that all MSP files relevant to a computer’s installed roles must be applied.
Manually verify or import the reporting management packs UR4 includes updated reporting-related MPs such as:
- Microsoft.SystemCenter.DataWarehouse.Library.mp
- Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
- Microsoft.SystemCenter.DataWarehouse.Reports.mp
- Microsoft.SystemCenter.OperationsManager.Reports.2007.mp
If those MPs were not updated/imported during UR4 installation, reporting folders can appear without usable reports.
If the management server update hit an MP import problem, mitigate it and rerun/import manually Earlier SCOM 2022 UR guidance documents a known management pack import failure during management server update and gives these mitigations:
- Install .NET Framework 3.5, then rerun the management server update, or
- Import the management packs manually
That mitigation is relevant when the update completes but MPs do not appear correctly afterward.
If reports are still blank or inconsistent after the MPs are present, check Data Warehouse write health On all management servers, review the Operations Manager event log for:
- HealthService 2115 events, or
- warning/error events from source Health Service Modules and category Data Warehouse
If management servers cannot write to OperationsManagerDW, reporting behavior can be incomplete or unpredictable.
If UNIX/Linux monitoring was part of the UR4 change, update those MPs separately after UR4 The UR4 process for UNIX/Linux is:
- Apply UR4
- Download the updated Linux/UNIX management packs
- Import the updated MPs
- Upgrade agents with Update-SCXAgent or the UNIX/Linux Agent Upgrade Wizard

A practical end-to-end fix path for this case is:

Re-run the UR4 MSPs for Management Server and Reporting from an elevated command prompt.
In the Operations console, confirm the reporting MPs listed above are imported and at 10.22.12369.0.
If they are missing, import them manually.
Then check management server event logs for 2115 or Data Warehouse errors if reports still do not populate.

References: