Capacity reports are missing from the SCOM console after import
After importing the OpsLogix capacity reports the reports do not appear and event 31567 is logged. On SQL Server Reporting Services 2019 and later, allow the SCOM resource extensions for upload.
Applies to: OpsLogix Capacity trending reports (all versions) · SCOM 2019, 2022, 2025 · SQL Server Reporting Services 2019 and later
Last updated: October 2026 · Reading time: 3 minutes
Symptoms
- The management pack is imported, but the capacity reports do not appear in the Reporting workspace of the SCOM console.
- The Operations Manager event log on the management servers shows event 31567: failed to deploy a reporting component to the SQL Server Reporting Services server.
Cause
SQL Server Reporting Services 2019 and later only accept uploaded files whose extension is on the list Allowed resource extensions for upload. SCOM uploads the report resources of a management pack with extensions that are named after the management pack elements, such as .CustomConfiguration, .Report and .Groups. They are not on the default list, so Reporting Services rejects the upload and SCOM cannot deploy the reports.
Fix
- Open SQL Server Management Studio and connect to Reporting Services (in Connect to Server, choose Server type Reporting Services) on the SCOM reporting server.
- Right-click the server, choose Properties and open the Advanced page.
- In AllowedResourceExtensionsForUpload, add these entries to the existing list, separated by commas: *.CustomConfiguration, *.Report, *.Groups. Keep the entries that are already there.
- Click OK.
- Wait for SCOM to deploy the reports again. SCOM retries by itself; restarting the Microsoft Monitoring Agent service (HealthService) on a management server makes it try again sooner. The reports appear in the folder OpsLogix.IMP.Capacity in the Reporting workspace.
If event 31567 still appears, read its description: it names the file that was rejected. Add that extension to the list in the same way.