SCCM empty report

dylanand2-7592 320 Reputation points
2024-07-31T14:59:16.7633333+00:00

Hi experts,

I have installed the Report Service Point with no error. However, the report is empty when I open the SCCM console and go to reports. It doesn't show any reports or folders. What's wrong here?

Microsoft Configuration Manager
{count} votes

Accepted answer
  1. glebgreenspan 2,230 Reputation points
    2024-07-31T15:04:00.1166667+00:00

    Hello Dylanand2

    It can be many reasons

    Can you follow these steps:

    1. Verify Report Server Configuration:
      • Open the Reporting Services Configuration Manager and ensure that the Report Server Web Service URL, Report Manager URL, and Database settings are all configured correctly.
        • Ensure that the service account used for the Report Server has the necessary permissions.
        1. Check Permissions:
          • Ensure that the appropriate user accounts have permission to view the reports. You may need to grant access to the roles that allow report viewing. Check the permissions in both SCCM and SQL Server Reporting Services (SSRS).
            • In SCCM, navigate to Administration > Security > Security Roles, and verify that the role assigned to your user has permissions to view reports.
            1. Validate SQL Server Reporting Services (SSRS) Availability:
              • Open the SSRS web portal (usually found at `http://<your-report-server>/Reports`) and check if the reports can be accessed directly from there. Confirm that SSRS is operational and does not have any issues.
              1. Ensure Catalog Items are Available:
                • Check to see if any reports exist in the SCCM database. Run a SQL query against the dbo.report table in the SCCM database to see if any reports are listed:
                  • If the table is empty, it might indicate an issue with the report packaging during installation or a misconfiguration.
                  1. SCCM Console Installation:
                    • Sometimes, the SCCM console may not be fully updated. Close and reopen the console or even consider restarting the server where the SCCM console is installed.
                    1. Update SCCM:
                      • Ensure that your SCCM environment is up to date with the latest updates and hotfixes. Sometimes, issues with the console can be resolved through updates.
                      1. Re-Register the Reporting Services Point:
                        • If issues persist, consider removing and then re-adding the Reporting Services Point:
                          - Go to **Administration > Site Configuration > Sites**.
                          
                                - Select your site and remove the Reporting Services Point.
                          
                                      - Re-add the Reporting Services Point and verify the settings.
                          
                                      1. **Check for Logs**:
                          
                                         - Review the logs related to the Reporting Services Point in SCCM. Look for logs such as `SMS_ReportServer.log` and `SMS_ReportingServices_Point.log` to identify any errors during the report point registration or SQL Server connectivity.
                          
                                         1. **Firewall and Network Issues**:
                          
                                            - Ensure that there are no firewall rules or network issues preventing communication between the SCCM site server, SQL Server, and the Reporting Services Point.
                          
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. AllenLiu-MSFT 43,951 Reputation points Microsoft Vendor
    2024-08-01T06:24:15.5766667+00:00

    Hi, @dylanand2-7592

    Thank you for posting in Microsoft Q&A forum.

    It's possible that the Report Server Service Account doesn't have Read permissions to the OU in which the user running the report resides, or to Users or Computers container in Active Directory Domain Services (AD DS). This can cause reports to not run as expected.

    To resolve this issue, you can grant the Report Server Service Account Read permissions to the OU in which the user running the report resides, and to both the Users and Computers containers in AD DS.


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.