Event ID 1103 from source HealthService cannot be found.

asked 2021-04-30T10:43:38.69+00:00
Deepak 86 Reputation points

Hello All,

We have SCOM 2019 however in one of our SCOM management server we see the below Event iD in Application logs kindly assist us on this.

The description for Event ID 1103 from source HealthService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:

SCOM group Name: XXXX
15
1
The message resource is present but the message was not found in the message table

Event ID 1103
Source: Application

Operations Manager
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,200 questions
No comments
{count} votes

Accepted answer
  1. answered 2021-04-30T16:40:46.557+00:00
    Stoyan Chalakov 8,806 Reputation points Microsoft MVP

    Hi,

    the event generelly refers to workflows (rules, monitors, disocveries) failing and not being loaded. The exact description is:

    "Summary: xxxx rule(s)/monitor(s) failed and got unloaded, 1 of them reached the failure limit that prevents automatic reload. Management group “xxx”. This is summary only event, please see other events with descriptions of unloaded rule(s)/monitor(s)."

    In your case, sonsidering that the events do not contain the description in clear text, I assume it is:

    "Summary: 15 rule(s)/monitor(s) failed and got unloaded, 1 of them reached the failure limit that prevents automatic reload. Management group “xxx”. This is summary only event, please see other events with descriptions of unloaded rule(s)/monitor(s)."

    You need to identify what rules or monitors are exactly failing. For this purpose you need to find the other related events and do some debugging. Here is a nice giude on how to approach this:

    Debugging SCOM Workflows using PowerShell
    https://www.opslogix.com/knowledgebase/debugging-scom-workflows-using-powershell

    *The event is also mentioned in this article.

    this Social Technet Post can also give you some nice suggestions/ideas how to resolve this:

    Event ID: 1103
    https://social.technet.microsoft.com/Forums/en-US/88d6f386-162e-4217-be9c-87d53322961a/event-id-1103?forum=operationsmanagergeneral

    I hope I could help you out.


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

    Best regards,
    Stoyan

    No comments

0 additional answers

Sort by: Most helpful