If most SCCM reports are blank, first determine where they are blank. “No items found” in the Configuration Manager console usually indicates a reporting services point, SSRS catalog, URL, or permissions problem. Reports that open but return zero rows usually indicate missing Configuration Manager data, incorrect parameters, delayed processing, or database-query permissions. A report that works in the SSRS web portal but not in the console points primarily to a console URL or authorization problem.
Microsoft now calls SCCM Configuration Manager, but the traditional reporting path still uses SQL Server Reporting Services (SSRS).
As an Amazon Associate I earn from qualifying purchases.
Identify the type of blank report
| Symptom | Likely failure layer | First check |
|---|---|---|
| Monitoring → Reporting → Reports shows “No items found” | Reporting services point, SSRS catalog, console URL, or permissions | Open the SSRS web portal and inspect the report folder |
| The folder exists but contains no reports | Reporting-point synchronization or deployment | Review srsrp.log, srsrpsetup.log, and srsrpMSI.log |
| Reports appear, but clicking Run fails | SSRS URL, credentials, permissions, or query execution | Read the exact SSRS processing error |
| A report runs and returns zero rows | Parameters, collections, inventory, discovery, deployments, or site data | Test a known-populated collection and suitable date range |
| The report works in a browser but not in the console | Console report-server configuration or console-user permissions | Compare the console’s URL with the current SSRS Web Service URL |
| Only one report category is empty | Report-specific prerequisites or query problem | Confirm that the relevant clients have submitted that type of data |
| Everything became empty after migration or a password change | Account, data source, URL, SQL permissions, or SSRS configuration | Compare reporting settings and credentials with the pre-change configuration |
Do not reinstall SQL Server merely because a report has no rows. Reinstallation cannot create inventory, discovery, deployment, or update data that has not reached the site database.
Free tools Windows power users keep installed
One-click scans. No signup required.
How Configuration Manager reporting works
The normal reporting path is:
Configuration Manager console → reporting services point → SSRS → Configuration Manager site database → report result
#1 Best Overall
Configuration Manager provides predefined report definitions. SSRS stores and renders those definitions, while the reports query the Configuration Manager site database when they run. Microsoft describes more than 400 predefined reports organized into more than 50 folders, although the exact inventory varies by Configuration Manager version, installed features, and deployment state. See Microsoft’s reporting overview.
The SSRS catalog and the site database have different jobs:
- The SSRS ReportServer database stores report definitions, folders, metadata, subscriptions, and related SSRS information.
- The Configuration Manager site database—commonly named
CM_<SiteCode>—contains the operational data queried by the reports.
Consequently, reports may exist in SSRS while the console cannot display them, or display correctly while returning no data. A healthy Configuration Manager site does not guarantee a healthy SSRS installation, and a working SSRS portal does not prove that SSRS can query the site database.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
1. Confirm whether the report definitions exist
In the console, open Monitoring → Reporting → Reports. Then open the SSRS web portal from a browser and locate the Configuration Manager report folder. Microsoft documents both the console and browser methods in its report-running procedure.
If you have appropriate SQL access, you can inspect the SSRS catalog:
Rank #2
SELECT Name, Path, Type, ModifiedDate
FROM <ReportServerDatabase>.dbo.Catalog
ORDER BY Path, Name;Run this against the SSRS report-server database, not the Configuration Manager site database. Do not assume the folder name; it depends on the reporting-services-point configuration.
Interpret the comparison
- Reports exist in SSRS but not in the console: investigate the console’s report-server URL, the console user’s permissions, and the site/reporting-point association.
- The Configuration Manager folder exists but is empty: investigate reporting-point synchronization, SSRS connectivity, account permissions, and reporting logs.
- The folder does not exist: the reporting services point may not have completed deployment or may target the wrong SSRS instance.
- Reports exist and work in the browser: focus on the console rather than rebuilding the SSRS catalog.
2. Verify the SSRS installation
On the SSRS server, open Report Server Configuration Manager and verify:
- Report Service Status is Started.
- The configured Web Service URL opens successfully.
- SSRS is running in Native mode.
- The Web Portal URL opens successfully.
- The configured SSRS database is the intended report-server database.
These checks establish that SSRS is reachable, but they do not prove that Configuration Manager report definitions were deployed or that the SSRS data source can query the correct site database. Use Microsoft’s reporting configuration guidance for the supported prerequisites.
3. Check the reporting services point
The reporting services point copies predefined report definitions to SSRS, configures reporting settings, and applies Configuration Manager reporting security.
Inspect it under:
Administration → Site Configuration → Servers and Site System Roles
Select the site system hosting Reporting services point and verify:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- the correct SQL Server and site database;
- the correct SSRS server and instance;
- the intended report-folder name;
- the reporting services point account;
- that the selected SSRS instance actually runs on that server.
The account used to set up the role needs read access to the site database. Microsoft also specifies Log on locally permission on the server hosting the Reporting Services database. In cross-domain deployments, users in another domain may also require a two-way trust for reports to run successfully.
4. Read the reporting logs
The main Configuration Manager logs are:
srsrp.logsrsrpsetup.logsrsrpMSI.log
They are normally in the Configuration Manager installation log directory on the relevant site system. Search for terms such as:
HTTP status 503SRS not detected as runningfailed to connectaccess deniedlogin failedreport foldercatalogpermissionfailed to decryptquery execution failed
Also inspect the SSRS logs when the portal returns HTTP 500 or 503, a report fails during processing, credentials are rejected, or a stored procedure produces a SQL permission error.
An HTTP 503 combined with “SSRS not detected as running” indicates an SSRS availability problem, not missing Configuration Manager inventory. Microsoft Q&A cases describe repairing or reinstalling SSRS and then reinstalling the reporting services point as a recovery in that situation. Treat that as an escalation after diagnosis, not as the universal first step.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Rank #4
5. Check permissions at every layer
Configuration Manager permissions
To run reports, a user generally needs:
- Read permission for the Site object;
- Run Report permission for the relevant secured objects.
Creating or modifying reports requires the corresponding report-modification permissions. A user may therefore open the Reporting workspace but still be unable to see or run particular reports.
SSRS permissions
Configuration Manager uses reporting roles such as ConfigMgr Report Users and ConfigMgr Report Administrators. The reporting services point periodically reapplies Configuration Manager’s role-based security. Manual changes made directly in Report Manager can therefore be overwritten.
SSRS native mode also uses roles such as Browser and Content Manager. See Microsoft’s documentation on SSRS roles and permissions.
SQL permissions
A report can be visible but fail at execution because its data-source identity can read a view but cannot execute a required stored procedure or function. For example, Microsoft documents Configuration Manager report-processing failures caused by an EXECUTE permission denial on fnIsCas. That is a database-permission error, not an empty-data condition.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchUse the exact SSRS error and the SSRS data-retrieval troubleshooting guidance before changing database permissions. Do not solve every account problem by making service accounts local administrators.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.6. Fix reports that run but return no rows
If the report opens and displays an empty grid, check the report’s data prerequisites:
- Rerun it with the correct site, collection, deployment, update group, computer, user, and date parameters.
- Test a collection that is known to contain members.
- Confirm that clients are active and communicating.
- Verify that the required hardware inventory, software inventory, discovery, compliance, update-scan, deployment, or status-message data has been collected.
- Allow for processing and summarization delays after a new deployment or inventory cycle.
- Compare the report with an appropriate console view or a read-only database query.
- Confirm that the reporting point uses the intended site database rather than an old or wrong database.
A new site with few clients, no inventory cycle, no deployment activity, or an empty collection can legitimately produce blank reports. Task-sequence, update, compliance, deployment, and inventory reports are especially dependent on the relevant feature having generated data.
7. Repair browser-versus-console mismatches
If a report works in the browser but is blank or unavailable in the Configuration Manager console, compare the report-server endpoint used by the console with the current SSRS Web Service URL. Test that URL from the console computer and verify that the console user has the required Configuration Manager and SSRS permissions.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsConfiguration Manager warns that changing the report-server URL after installing the reporting services point leaves the console using the old URL. If the URL must change:
- Remove the existing reporting services point.
- Change and verify the SSRS URL in Report Server Configuration Manager.
- Reinstall the reporting services point.
- Confirm that the console now reaches the new endpoint.
- Verify report deployment and permissions again.
This is particularly important after an SSRS migration, certificate change, server rename, or web-service URL modification.
SQL Server and SSRS migration checklist
- SSRS is installed on the server selected for the reporting services point.
- SSRS is in Native mode.
- The Web Service URL and Web Portal URL work.
- The reporting services point was recreated if the URL changed.
- The report data source points to the current Configuration Manager site database.
- The reporting account password was updated wherever it is stored.
- The site database name, SQL instance, DNS name, and firewall rules are correct.
- Windows authentication and any required domain trust work from the reporting server.
- The account has the required database and local-logon permissions.
- The SSRS catalog contains the expected Configuration Manager folders and report definitions.
Safe recovery sequence
Collect logs and identify the failing layer before rebuilding anything. Then use this order:
- Start or repair SSRS if its service is stopped.
- Correct SSRS URLs, Native-mode configuration, database settings, or service identity.
- Correct the reporting-point account and Configuration Manager permissions.
- Remove and reinstall the reporting services point.
- If SSRS itself is damaged, repair or reinstall SSRS, configure its database and URLs, and then reinstall the reporting services point.
- Confirm that reports repopulate in the SSRS catalog.
- Confirm that the console sees them.
- Run a simple report before testing complex inventory or deployment reports.
Do not casually delete the SSRS encryption key
SSRS encryption keys protect stored credentials and other encrypted report-server data. Deleting or resetting them can make existing encrypted content unusable and may require restoring or re-entering credentials. If encryption-key corruption is suspected, back up the SSRS encryption key and report-server databases first, then follow the applicable Microsoft SSRS recovery procedure. Key deletion is a destructive escalation, not a routine fix for blank SCCM reports.
Recommended Free Tools
Evidence to collect before requesting support
- Configuration Manager current-branch version and site code;
- SSRS version, server, instance, and URLs;
- whether reports work in the browser;
- the exact console or SSRS error;
srsrp.log,srsrpsetup.log, andsrsrpMSI.log;- relevant SSRS logs;
- recent SQL/SSRS migrations, password changes, certificate changes, upgrades, or server moves;
- the affected report name, parameters, collection, and expected data source.
Buying Power BI, Power BI Report Server, or a third-party tool such as Recast Software will not repair a stopped SSRS service, incorrect URL, missing report catalog, SQL permission, or absent client data. Fix the native reporting path first; consider an alternative platform only when the requirement is richer dashboards or analytics rather than recovery of built-in reports.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
