locked
SCOM Reporting service installation Error RRS feed

  • Question

  • Hi Team,

    I've newly installed evaluation SCOM in the SCOM MS while installed DB and DW in seperate server. I'm now installing the reporting service feature in DB server but getting an error. PFA. Please help me how to proceed. 

    Based on few inputs in other forums, I have tried re-creating the URL and it goes with the error "

    The attempt to connect to the report server failed.  Check your connection information and that the report server is a compatible version."

    ; cleared the encryption keys but in vain. Please guide further. 

    Monday, June 24, 2019 2:50 PM

Answers

  • I've encountered your given error before, especially with SQL Server Reporting Services 2017.

    Make sure you have performed according to the following steps:

    1. Install SQL Server 201X Reporting Services.

    2. Open the Reporting Server Configuration Manager.

    3. Create a new database within the SCOM SQL instance.

    4. Once created, go to Web Service URL and click "Apply".

    5. Then go to Web Portal URL and click "Apply".

    6. Restart the SCOM installation wizard. (might consider a reboot).

    7. Try installing the SCOM Reporting again.


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by Zikki_Asks Thursday, June 27, 2019 10:58 AM
    Monday, June 24, 2019 9:42 PM
  • Hi,

     

    Please check the setup log in detail to see when the error returned .  I find a link mentioned the error returned when connect to the UR for reporting. If you are the same, try the solution in the link to see if our issue is fixed.

    http://realscom.blogspot.com/2017/05/report-server-install-failing.html

    Note: This is just for your reference.

     

    Meanwhile, please make sure the steps below “Configure SQL 2017 Reporting Services” in the following article are also done in our environment.

    https://kevinholman.com/2019/03/14/scom-2019-quickstart-deployment-guide/

     

    Please try the above steps and if any update, please let us know.

     

    Best regards.

    Crystal


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

    • Marked as answer by Zikki_Asks Thursday, June 27, 2019 10:59 AM
    Tuesday, June 25, 2019 2:15 AM

All replies

  • Hi,

    Have you configured the following?

    • Report database (created a new/chose existing database)
    • Web Service URL
    • Web Portal URL

    Can you please check the installation log for more clues/details?

    You can find it over here:

    • %USERPROFILE%\AppData\Local\SCOM\LOGS\OpsMgrSetupWizard.log
    • %USERPROFILE%\AppData\Local\SCOM\LOGS\OMReporting.log


    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:


    • Edited by Leon Laude Monday, June 24, 2019 3:32 PM
    Monday, June 24, 2019 3:31 PM
  • Error code : 0x80131509
    Monday, June 24, 2019 3:59 PM
  • Which version of SQL Server / SQL Server Reporting Services do you have installed?

    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, June 24, 2019 4:01 PM
  • I've encountered your given error before, especially with SQL Server Reporting Services 2017.

    Make sure you have performed according to the following steps:

    1. Install SQL Server 201X Reporting Services.

    2. Open the Reporting Server Configuration Manager.

    3. Create a new database within the SCOM SQL instance.

    4. Once created, go to Web Service URL and click "Apply".

    5. Then go to Web Portal URL and click "Apply".

    6. Restart the SCOM installation wizard. (might consider a reboot).

    7. Try installing the SCOM Reporting again.


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by Zikki_Asks Thursday, June 27, 2019 10:58 AM
    Monday, June 24, 2019 9:42 PM
  • Hi,

     

    Please check the setup log in detail to see when the error returned .  I find a link mentioned the error returned when connect to the UR for reporting. If you are the same, try the solution in the link to see if our issue is fixed.

    http://realscom.blogspot.com/2017/05/report-server-install-failing.html

    Note: This is just for your reference.

     

    Meanwhile, please make sure the steps below “Configure SQL 2017 Reporting Services” in the following article are also done in our environment.

    https://kevinholman.com/2019/03/14/scom-2019-quickstart-deployment-guide/

     

    Please try the above steps and if any update, please let us know.

     

    Best regards.

    Crystal


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

    • Marked as answer by Zikki_Asks Thursday, June 27, 2019 10:59 AM
    Tuesday, June 25, 2019 2:15 AM
  • Now, the installation is successful after we newly installed the SSRS. Do I need to install anything in the management server. Currently I have installed reporting service in the DB server itself.  
    Thursday, June 27, 2019 11:00 AM
  • There's no need to install/configure anything else if you can you see the report templates under the Reporting tab in the Operations Console.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, June 27, 2019 11:04 AM
  • Yes, we installed SQL server 2014 reporting service. 

     Availability tracker shoes not monitored in the report. COuld you please let me know the reason?

    Please guide me once, windows operating system is not being monitored as well PFA. Please let me know what management pack should I install.. Even CPU , memory parameters are not being monitored. Note: I have newly build the scom test server.

     


    Thursday, June 27, 2019 12:20 PM
  • Hi,

    Windows OS monitoring is not part of the default management packs. You can downloaded them from here and import them on the SCOM server.

    http://www.microsoft.com/en-us/download/details.aspx?id=9296

    Hope the information can help.

    Best regards.

    Crystal


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

    Friday, June 28, 2019 6:39 AM