locked
SCCM Current Branch - Reporting Issue RRS feed

  • Question

  • Hello,

             I'm setting up new SCCM 1902 infra and I'm using remote reporting services point and remote SQL cluster for Reporting DB.

             I have completed the Reporting services point and configuration without any error, but I do see only 160 reports in the console, missing lot of reports.

             I tried reconfigure the Reporting DB and reporting services role without any luck.

             Can Someone help me with the fix.

            One more question, is it supported to install the Reporting DB on any of the clustered node as standalone instance?  

    Friday, January 10, 2020 10:24 AM

All replies

  • Review the rp logs for errors. Make sure that your account has full admin access.

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    Friday, January 10, 2020 12:22 PM
  • Hi,

    In addition to @Garth reply, check also the ssrs.log file located in "SCCM Install directory\Configuration Manager\Logs".

    For more details about the SSRS Log files:

    Regards,

    Youssef Saad

    ______

    Please remember to mark the replies as answer if they help, thank you!


    • Edited by SAAD Youssef Saturday, January 11, 2020 10:18 AM
    Saturday, January 11, 2020 10:18 AM
  • I checked the service account is local admin and sys admin on SQL, Site server and RSP servers.

    Initially I have 112 reports in reporting URL.

    After tried HKEY_Local_Machine\Software\Microsoft\SMS\SRSRP\ change the SRSInitializeState  key to 0 

    No. of reports increased to 165, still missing a lot.

    I'm using a custom dynamic high port.

    Error I see at "failed to retrieve existing folder security for folder"

    "

    System.Web.Services.Protocols.SoapException: The path of the item 'Hardware - Security' is not valid. The full path must be less than 260 characters long; other restrictions apply. 
    If the report server is in native mode, the path must start with slash. 
    ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidItemPathException: The path of the item 'Hardware - Security' is not valid. 
    The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash.

    "


    • Edited by Juliesmiley Monday, January 13, 2020 2:04 AM
    Sunday, January 12, 2020 3:48 PM
  • Hi,

    Security for reporting is much like other objects in Configuration Manager where you can assign security roles and permissions to administrative users. Administrative users can only run and modify reports for which they have appropriate security rights. To run reports in the Configuration Manager console, you must have the Read right for the Site permission and the permissions configured for specific objects.
    For more information on how to plan for role-based administration for reports, refer to the following articles for more details:
    https://docs.microsoft.com/en-us/configmgr/core/servers/manage/planning-for-reporting#BKMK_RoleBaseAdministration

    Best regards,
    Larry


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, January 13, 2020 7:47 AM
  • I checked the service account is local admin and sys admin on SQL, Site server and RSP servers.

    Initially I have 112 reports in reporting URL.

    After tried HKEY_Local_Machine\Software\Microsoft\SMS\SRSRP\ change the SRSInitializeState  key to 0 

    No. of reports increased to 165, still missing a lot.

    I'm using a custom dynamic high port.

    Error I see at "failed to retrieve existing folder security for folder"

    "

    System.Web.Services.Protocols.SoapException: The path of the item 'Hardware - Security' is not valid. The full path must be less than 260 characters long; other restrictions apply. 
    If the report server is in native mode, the path must start with slash. 
    ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidItemPathException: The path of the item 'Hardware - Security' is not valid. 
    The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash.

    "


    I have seen this error before but I have never gotten a good answer on how to solve it. It is basically hard to repro. My only suggest is to contact MS Support (CSS). 

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    Monday, January 13, 2020 9:55 PM
  • Okay, Thanks.
    Wednesday, January 15, 2020 6:00 AM
  • I should have added, you should open a support case with css. They might know a solution to this.

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    Wednesday, January 15, 2020 12:23 PM
  • Hi,

    Just checking in to see if there are any updates. Has this issue been solved? Please feel free to feedback and if the reply is helpful, please kindly click “Mark as answer”. It would make the reply to the top and easier to be found for other people who has the similar question.

    Thank you!


    Best regards,
    Larry

    Friday, January 17, 2020 1:43 AM
  • Nope, Still rebuilding the infra as it's my SIT infra.
    Monday, January 20, 2020 10:37 AM