SCOM 2019 Reporting-- Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.RunReportJob(Object sender, ConsoleJobEventArgs args

Raj Bhaskar W 21 Reputation points
2022-08-18T10:39:43.767+00:00

Getting below error while running custom report in SCOM 2019

Note: The following information was gathered when the operation was attempted. The information may appear cryptic but provides context for the error. The application will continue to run.

System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.RunReportJob(Object sender, ConsoleJobEventArgs args)

Checked Already:

  • Report able to run from report server URL
  • Data source connectivity is fine

Could someone Please suggest here .

System Center Operations Manager
System Center Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,608 questions
{count} votes

Accepted answer
  1. Denis Orlov 81 Reputation points
    2022-09-15T08:35:08.027+00:00

    Issue located

    I make it work with SCOM 2019 console on SCOM 2022 & SSRS 2019 environment

    On separate server been installed SQL CLR Types 2014, Report Viewer 2015 and SCOM 2019 Console (directly with msi file) without any UR for it
    All custom reports now working
    Removed SCOM 2022 console from Management Server, installed SCOM 2019 one - and it works
    Yes, its dirty workaround, but we have about 20 critical custom SCOM related reports, and work this them on browser not really convenient

    Now, next challenge (if only Microsoft wont fix this) is to make it work with SCOM 2022 console
    First obsticle is that there is no newer version ReportViewer runtime available, now its inside Microsoft Report RDLC Designer for Visual Studio...

    @DG Malcolm , did you install any SCOM 2019 UR4 just before that happen? Try clean console installation on separate server

    1 person found this answer helpful.

7 additional answers

Sort by: Most helpful
  1. Raj Bhaskar W 21 Reputation points
    2022-08-22T10:17:36.133+00:00

    Could someone please assist me here.

    Thanks in advance.

    0 comments No comments

  2. SChalakov 10,576 Reputation points MVP Volunteer Moderator
    2022-08-24T11:29:09.357+00:00

    Hi @Raj Bhaskar W ,

    can you please check the Application event Log on your Reporting Server, do you find associated events? What do they state?
    Would you please also check the events logs (Operations Manager) on your management servers. Do you see events related to the Reporting or events related to the Datawarehousse sync?
    Since when does this happen?
    What SSRS version are you using?
    I am not sure if this could also cause such behaviour, but would you please check and follow this:

    Operations Manager 2019 and 1807 reports fail to deploy
    https://learn.microsoft.com/en-us/troubleshoot/system-center/scom/cannot-deploy-operations-manager-reports

    Please post the status aftwerwatds, I will try to help you out!

    ----------

    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
    Regards
    Stoyan Chalakov

    0 comments No comments

  3. DG Malcolm 1 Reputation point
    2022-08-29T15:11:08.867+00:00

    Found this thread after opening the exact same issue on the MS Tech Community
    -- (https://techcommunity.microsoft.com/t5/system-center/scom-2019-reporting-error-quot-cannot-execute-report-quot/m-p/3611775)

    I am running SCOM 2019 UR4

    • Windows Server 2016 on all servers
    • 2 x Management Servers
    • 1 x SQL server with SSRS
    • -- SQL 2019 CU8 (15.0.4073.23)
    • -- SSRS 2019 August 2020 Release (15.0.1102.861)

    All of the out-of-box reports that I've tested run successfully. One report, an after-market logical disk space report, fails with the exact error message in this thread. The report was imported into SCOM in March 2021 and I've been running 4 scheduled reports against it 5 days a week ever since. Until last week - on Tuesday all 4 reports ran normally but on Wednesday all 4 reports were blank. When I tried to run the report from the console, I got the error:

    Application: Operations Manager
    Application Version: 10.19.10569.0
    Severity: Error
    Message: Cannot execute report.

    System.NullReferenceException: Object reference not set to an instance of an object.
    at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.RunReportJob(Object sender, ConsoleJobEventArgs args)

    This morning I modified the name of the .RDL and imported it again. No trouble importing the report but same error with the new one. As far as I know there were no changes last week.

    TIA
    ~DGM~

    0 comments No comments

  4. Denis Orlov 81 Reputation points
    2022-09-14T16:57:17.983+00:00

    Have same issue

    SCOM 2022 - 2 MS
    SQL 2019 - AlwaysOn 2 noides
    SSRS 2019 - standalone
    all of them on Windows 2016 Server

    Unable to execute any of custom reports from SCOM console
    But, all of that reports work just fine in case of executing them from browser
    This issue somewhere on SCOM console side, INHO
    Tested console installed right on reporting server, getting this error all the time, and no single event related to this issue in log on SSRS server and MS servers

    Noticed
    I have one custom report with preconfigured parameters, and it works from console, immediately showing all data, but... if I change anything in parameters (DateTime for example) this report start showing same error message...

    Cannot find any solution so far


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.