locked
SCCM 2012 not creating root folder in SSRS RRS feed

  • Question

  • I have been trying to resolve and issue where reports are not showing up in the SCCM console. When  I install the SCCM Reporting Point roll (SRPR) it does not create a root folder or data source in the in the SSRS virtual directory. From the SCCM console I am able to select the reporting instance and after the install I can connect to the Reports and ReportsManager sites using IE. Nothing is populated, no root folder not data source. Does anyone know how to trigger the Virtual Directory configuration, or manually configure it to point to the installed reports?

    SMSSRSRP Setup shows:

    <04/13/15 09:02:45> ====================================================================
    <04/13/15 09:02:45> SMSSRSRP Setup Started....
    <04/13/15 09:02:45> Parameters: \\Server.domain.com\Q$\SMS\bin\x64\rolesetup.exe /install /siteserver:Server SMSSRSRP 0
    <04/13/15 09:02:45> Installing Pre Reqs for SMSSRSRP
    <04/13/15 09:02:45>         ======== Installing Pre Reqs for Role SMSSRSRP ========
    <04/13/15 09:02:45> Found 1 Pre Reqs for Role SMSSRSRP
    <04/13/15 09:02:45> Pre Req SqlNativeClient found.
    <04/13/15 09:02:45> SqlNativeClient already installed (Product Code: {3965C9F9-9B9A-4391-AC4B-8388210D3AA0}). Would not install again.
    <04/13/15 09:02:45> Pre Req SqlNativeClient is already installed. Skipping it.
    <04/13/15 09:02:45>         ======== Completed Installation of Pre Reqs for Role SMSSRSRP ========
    <04/13/15 09:02:45> Installing the SMSSRSRP
    <04/13/15 09:02:45> Passed OS version check.
    <04/13/15 09:02:45> .NET Framework 4.0 Full profile is installed.
    <04/13/15 09:02:45> Clean up old files
    <04/13/15 09:02:45> No versions of SMSSRSRP are installed.  Installing new SMSSRSRP.
    <04/13/15 09:02:45> Enabling MSI logging.  srsrp.msi will log to Q:\SMS\logs\srsrpMSI.log
    <04/13/15 09:02:45> Installing Q:\SMS\bin\x64\srsrp.msi SRSRPINSTALLDIR="Q:\SMS_SRSRP" SRSRPLANGPACKFLAGS=0
    <04/13/15 09:02:48> srsrp.msi exited with return code: 0
    <04/13/15 09:02:48> Installation was successful.
    <04/13/15 09:02:48> CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe" "Q:\SMS_SRSRP\srsserver.dll" /unregister
    <04/13/15 09:02:49> CTool::RegisterManagedBinary: Registered Q:\SMS_SRSRP\srsserver.dll successfully
    <04/13/15 09:02:49> Unregistered DLL Q:\SMS_SRSRP\srsserver.dll
    <04/13/15 09:02:49> CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe" "Q:\SMS_SRSRP\srsserver.dll" /codebase
    <04/13/15 09:02:50> CTool::RegisterManagedBinary: Registered Q:\SMS_SRSRP\srsserver.dll successfully
    <04/13/15 09:02:50> Registered DLL Q:\SMS_SRSRP\srsserver.dll
    <04/13/15 09:02:50> No versions of SMSSRSRP are installed.  Installing new SMSSRSRP.
    <04/13/15 09:02:50> Enabling MSI logging.  srsrp.msi will log to Q:\SMS\logs\srsrpMSI.log
    <04/13/15 09:02:50> Installing Q:\SMS\bin\x64\srsrp.msi SRSRPINSTALLDIR="Q:\SMS_SRSRP" SRSRPLANGPACKFLAGS=0
    <04/13/15 09:02:56> srsrp.msi exited with return code: 0
    <04/13/15 09:02:56> Installation was successful.
    <04/13/15 09:02:56> Installation was successful.
    <04/13/15 09:02:56> ~RoleSetup().

    After installing the Reporting Point the srsrp.log shows:

    MS_EXECUTIVE started SMS_SRS_REPORTING_POINT as thread ID 8312 (0x2078).  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:02:59.517+240><thread=7968 (0x1F20)>
    This is a SRS Reporting Point Role as SRSRP registry key exists.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:03:14.522+240><thread=8312 (0x2078)>
    ~Waiting for changes for 0 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:03:14.526+240><thread=8312 (0x2078)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:03:14.526+240><thread=8312 (0x2078)>
    Check state~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:03:14.526+240><thread=8312 (0x2078)>
    Check server health.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:03:14.526+240><thread=8312 (0x2078)>
    Registry change~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:03:14.526+240><thread=8312 (0x2078)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:03:14.527+240><thread=8312 (0x2078)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:04:14.530+240><thread=8312 (0x2078)>
    Check state~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:04:14.530+240><thread=8312 (0x2078)>
    Check server health.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:04:14.530+240><thread=8312 (0x2078)>
    Registry change~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:04:14.530+240><thread=8312 (0x2078)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:04:14.531+240><thread=8312 (0x2078)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:05:14.534+240><thread=8312 (0x2078)>
    Check state~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:05:14.534+240><thread=8312 (0x2078)>
    Check server health.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:05:14.534+240><thread=8312 (0x2078)>
    Registry change~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:05:14.534+240><thread=8312 (0x2078)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:05:14.535+240><thread=8312 (0x2078)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:06:14.538+240><thread=8312 (0x2078)>
    Check state~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:06:14.538+240><thread=8312 (0x2078)>
    Check server health.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:06:14.538+240><thread=8312 (0x2078)>
    Registry change~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:06:14.538+240><thread=8312 (0x2078)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:06:14.539+240><thread=8312 (0x2078)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:07:14.542+240><thread=8312 (0x2078)>
    Check state~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:07:14.542+240><thread=8312 (0x2078)>
    Check server health.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:07:14.542+240><thread=8312 (0x2078)>
    Registry change~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:07:14.542+240><thread=8312 (0x2078)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:07:14.543+240><thread=8312 (0x2078)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:08:14.546+240><thread=8312 (0x2078)>
    Check state~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:08:14.546+240><thread=8312 (0x2078)>
    Check server health.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:08:14.546+240><thread=8312 (0x2078)>
    Registry change~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:08:14.546+240><thread=8312 (0x2078)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:08:14.547+240><thread=8312 (0x2078)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:09:14.550+240><thread=8312 (0x2078)>
    Check state~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:09:14.550+240><thread=8312 (0x2078)>
    Check server health.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:09:14.550+240><thread=8312 (0x2078)>
    Registry change~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:09:14.551+240><thread=8312 (0x2078)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:09:14.551+240><thread=8312 (0x2078)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:10:14.555+240><thread=8312 (0x2078)>
    Check state~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:10:14.555+240><thread=8312 (0x2078)>
    Check server health.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:10:14.555+240><thread=8312 (0x2078)>
    Registry change~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:10:14.555+240><thread=8312 (0x2078)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:10:14.556+240><thread=8312 (0x2078)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:11:14.559+240><thread=8312 (0x2078)>
    Check state~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:11:14.559+240><thread=8312 (0x2078)>
    Check server health.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:11:14.559+240><thread=8312 (0x2078)>
    Registry change~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:11:14.559+240><thread=8312 (0x2078)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:11:14.560+240><thread=8312 (0x2078)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:12:14.563+240><thread=8312 (0x2078)>
    Check state~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:12:14.563+240><thread=8312 (0x2078)>
    Check server health.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:12:14.563+240><thread=8312 (0x2078)>
    Registry change~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:12:14.563+240><thread=8312 (0x2078)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:12:14.564+240><thread=8312 (0x2078)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:13:14.568+240><thread=8312 (0x2078)>
    Check state~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:13:14.568+240><thread=8312 (0x2078)>
    Check server health.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:13:14.569+240><thread=8312 (0x2078)>
    Registry change~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:13:14.569+240><thread=8312 (0x2078)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:13:14.569+240><thread=8312 (0x2078)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:14:14.573+240><thread=8312 (0x2078)>
    Check state~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:14:14.573+240><thread=8312 (0x2078)>
    Check server health.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:14:14.573+240><thread=8312 (0x2078)>
    Registry change~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:14:14.573+240><thread=8312 (0x2078)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:14:14.574+240><thread=8312 (0x2078)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:15:14.577+240><thread=8312 (0x2078)>
    Check state~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:15:14.577+240><thread=8312 (0x2078)>
    Check server health.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:15:14.577+240><thread=8312 (0x2078)>
    Registry change~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:15:14.577+240><thread=8312 (0x2078)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:15:14.578+240><thread=8312 (0x2078)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:16:14.581+240><thread=8312 (0x2078)>
    Check state~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:16:14.581+240><thread=8312 (0x2078)>
    Check server health.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:16:14.581+240><thread=8312 (0x2078)>
    Registry change~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:16:14.582+240><thread=8312 (0x2078)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:16:14.582+240><thread=8312 (0x2078)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:17:14.585+240><thread=8312 (0x2078)>
    Check state~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:17:14.585+240><thread=8312 (0x2078)>
    Check server health.~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:17:14.585+240><thread=8312 (0x2078)>
    Registry change~  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:17:14.585+240><thread=8312 (0x2078)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><04-13-2015 09:17:14.586+240><thread=8312 (0x2078)>

    Monday, April 13, 2015 3:51 PM

All replies

  • Are you trying to install this on a Clustered SQL server? What exactly is Q:\?

    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Monday, April 13, 2015 4:34 PM
  • No Clustering. The system has several partitions and SCCM is picking the Q:\ drive because the is no D:\ drive on the system.
    Monday, April 13, 2015 4:41 PM
  • Can you access SSRS via IE and is it working?

    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Monday, April 13, 2015 4:54 PM
  • Are you talking about the configuration of SSRS rather than the install? Follow the below:

    http://prajwaldesai.com/deploying-sccm-2012-part-12-installing-and-configuring-reporting-services-point/


    Cheers Paul | http://sccmentor.wordpress.com

    Monday, April 13, 2015 4:55 PM
  • Yes I can access SSRS via IE.
    Monday, April 13, 2015 5:31 PM
  • SSRS is setup correctly. when I install the Reporting Point the reports do not get added to the virtual directly in SSRS. 
    Monday, April 13, 2015 5:33 PM
  • Yes I can access SSRS via IE.

    Both URLs? Reports and ReportServer

    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Monday, April 13, 2015 5:33 PM
  • Yes both work.
    Monday, April 13, 2015 5:40 PM
  • When I look in the ReportServer Database under dbo.DataSource do not see any data sources listed for any reports.
    Monday, April 13, 2015 6:17 PM
  • I am trying to find out what part of the install populates the reports and creates the DataSource. I installed a new reporting instance with new databases. SCCM sees the reporting point during the reports setup, the reports are all installed to the file system the reporting point show green in the Sight Status. I have removed and re-added the reporting point several times. The step that does not seem to be occurring is there is no root folder, no data source, no reports in SSRS. On the file system yes, no errors from the site none in the logs.
    Monday, April 13, 2015 6:31 PM
  • Where is SSRS in relation to CM12 Database?

    Where errors are showing up within the CM12 console?

    Is the firewall open?

    Is AV disabled?


    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Monday, April 13, 2015 7:12 PM
  • SSRS is installed on the SQL server. There are no errors anywhere, and that is why I sent the output of the log. Here is the registry
    Monday, April 13, 2015 7:59 PM
  • Monday, April 13, 2015 7:59 PM
  • Monday, April 13, 2015 8:09 PM
  • Monday, April 13, 2015 8:11 PM
  • what about my other questions?

    Firewall?

    CM12 database to SSRS server


    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Monday, April 13, 2015 8:56 PM
  • Hi,

    Is there any errors in site status and component status?


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

    Tuesday, April 14, 2015 5:28 AM
  • Have you already tried to re-create all custom reports? Set SRSInitializeState to 0 (HKLM\Software\Microsoft\SMS\SRSRP) and monitor srsrp.log.

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, April 14, 2015 6:12 AM
    1. Open Reporting Services Configuration Manager
    2. Connect to the server/instance
    3. Click on Web Service URL – make a fake change, such as changing the name of the virtual directory and then putting it back to ReportServer – and clicking Apply.  This will then create the new virtual directories.
    4. Click on Report Manager URL – again, make a change to the name and put back to just Reports – and click Apply to generate the new virtual directories.
    5. Close configuration manager
    6. Return to the CM12 site role setup program, click “Verify” for the database connection, and voila the instance is now populated correctly!

    Source: http://myitforum.com/myitforumwp/2012/10/10/reporting-services-site-role-setup-instance-blankempty/#!prettyPhoto

    NN



    • Edited by Naked Nuts Tuesday, April 14, 2015 11:36 AM
    Tuesday, April 14, 2015 11:35 AM
  • Unfortunate this did not work. Does any one know how SCCM populates the reports into the virtual directories? Normally you would see the reports and their data sources in the reports database under dbo.DataSource.

    Database is 2012, SCCM 2012, AV is off, no firewall issues.

    Wednesday, April 15, 2015 3:03 PM
  • SRSInitializeState to 0 (HKLM\Software\Microsoft\SMS\SRSRP) has never changed. it is still at 0 and I attached the SRSRP log to show that it never triggered the initialization state.
    Wednesday, April 15, 2015 3:05 PM
  • I sent a screenshot of the registry key see above.
    Wednesday, April 15, 2015 3:07 PM
  • Does any one know how "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SRSRP\SRSInitializeState" works? what application reads that key and if the value is 0 repopulates the reports?
    Wednesday, April 15, 2015 3:11 PM
  • Did you ever get this sorted out? I have the same issue after a reinstall.

    -Richard

    Tuesday, July 26, 2016 2:09 AM
  • I also have identical issue - just bizarre, no errors in logs.

    I have tried the sqlmgmproviderxpsp2up.mof reimport also to no avail

    Zero report in both console and web front end

    Thanks

    Mark

    Thursday, September 29, 2016 10:11 AM
  • I am having the same issue. It appears that the Reporting Services Point roll is not getting installed, despite the wizard stating it was successful. My site server does not have SRSRP.log file nor is the a registry entry for SSRS. HKLM\Software\Microsoft\SMS\SRSRP

    My reporting URLs all open from any machine just fine, the firewalls are turned off and AV is removed.

    Any updates on this? Anyone have success?


    MZ

    Tuesday, April 17, 2018 8:32 PM
  • And what does the srsrpMSI.log log say?

    Garth Jones

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

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

    Tuesday, April 17, 2018 8:35 PM
  • I do not have an srsrpMSI.log file nor a SMS_SRS_REPORTING_POINT log in Component Status Monitoring also there is no Site Syetm role showing for the site server under Site Status. Yet the attached image shows the install completes.


    MZ

    Tuesday, April 17, 2018 10:18 PM
  • Also the images attached are for the ReportServer URLs. Which appear to be working.


    MZ

    Tuesday, April 17, 2018 10:23 PM
  • Also the images attached are for the ReportServer URLs. Which appear to be working.


    MZ

    that is only half off ssrs working, what about the report url? keep in mind that you clearly have a named ssrs site.

    Garth Jones

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

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

    Wednesday, April 18, 2018 12:30 AM
  • Hi Garth,

    Thank you for you help in getting this resolved. I am new to SCCM and have never seen a working example of an install so I'm not sure what the working screens should look like. How should I be doing things differently with a names SSRS site?

    In the last post there are two screen shots.

    The first is the report server page that opens when clicking the link In reporting. The second with the "Home" is the Report Manager page that opens when clicking the link. These are the same pages that load when using the Links in the Reporting Services Configuration Manager. (Web Service and Report manager)

    I have two servers. SQL2014 running SQL Standard and is the site db server and I want it to be the Reporting Services Point. The other is the primary site server.


    MZ

    Wednesday, April 18, 2018 12:57 PM
  • lol. I have no idea how I missed the report URL above. my apologies. 

    The srsrpMSI.log should be SSRS server. (SQL Server), look in both the CM Client directory and SMS directory (if exists).


    Garth Jones

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

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

    Wednesday, April 18, 2018 2:25 PM
  • I had removed the CM Client as part of troubleshooting. Some post I read said it could conflict. I searched the entire server for srsrpmsi.log not found anywhere.

    MZ

    Wednesday, April 18, 2018 2:51 PM
  • I believe I fixed the problem. I'm not 100% certain because I was trying so many things.

    1. I made sure my site server computer account and the account being used to push the Reporting Services Role were local admins on the target (SQL) server.

    2. In addition the Application Event log on the SQL server had Event 18456: Login failed for user 'domain\<useraccount>'. Reason: Could not find a login matching the name provided. [CLIENT: x.x.x.x]. Researching this lead me to add the specified account (account being used to push install the role) to the SQL server logins and assigned it appropriate rights.

    3. Restarted the SMS_SITE_COMPONENT_MANAGER and the role was pushed and reports appeared within 10min.

    I was able to access the log files on the SQL server for verifying the status or the installs.

    I now have 470 reports listed under Monitoring - Reports


    MZ

    • Proposed as answer by Zirbesma Wednesday, April 18, 2018 8:07 PM
    Wednesday, April 18, 2018 8:07 PM
  • Hi All,

    I am still facing the same issue. Cant see any error in any log. Still cant see any of reports in console in Web. SRSRP.log always says Waiting for changes for 1 minutes and Timed Out.

    Monday, December 9, 2019 6:31 AM
  • Hi All,

    I am still facing the same issue. Cant see any error in any log. Still cant see any of reports in console in Web. SRSRP.log always says Waiting for changes for 1 minutes and Timed Out.

    Did you do all of the troubleshooting steps listed within the post? 

    Garth Jones

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

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

    Monday, December 9, 2019 3:34 PM