none
Health Service Unloaded System Rule(s) alert on thin client computers

    Question

  • Hi I am running SCE 2010 and I am constantly getting alerts that say "Health Service Unloaded System Rule(s)" with descriptions that say

    "The health service 7BAFE284-8F9F-0727-5561-A155570864A5 running on host <THIN CLIENT> and serving management group with id {92902250-2C7A-716C-087D-25C188365460} is not healthy. Some system rules failed to load."

    Also, whenever I try to reinstall them, as suggested by product knowledge, it fails everytime.

    Friday, June 17, 2011 1:17 PM

All replies

  •  

    Hi,

     

    Based on my research, I would like to suggest the following:

     

    1.    Clear the HealthService queue on the server:

     

    1)    Stop System Center Management service.

    2)    Go to C:\Program Files\System Center Essentials\, and rename the “Health Service State” folder.

    3)    Restart System Center Management service.

     

    2.    Check SPN:

     

    SDK SPN Not Registered

    http://blogs.technet.com/b/jonathanalmquist/archive/2008/03/12/sdk-spn-not-registered.aspx

     

    Meanwhile, please also try the methods in the following post:

     

    Fixing troubled agents

    http://blogs.technet.com/b/kevinholman/archive/2009/10/01/fixing-troubled-agents.aspx

     

    Hope this helps.

     

    Thanks.
    Nicholas Li - MSFT
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, June 21, 2011 3:37 AM
  • Nicholas,

    I tried everything that you listed but it didn't work. Step one looked to have worked for a little while but then the alerts started coming back up again. Step two didn't look related to my problem at all.

    Thanks

    Tuesday, June 21, 2011 12:58 PM
  •  

    Hi,

     

    Thank you for your update.

     

    Please refer to the following articles:

     

    The Health Service does not process configuration files, and events 7022 and 1220 are logged every 30 minutes on a domain controller on which you installed the Operations Manager 2007 agent

    http://support.microsoft.com/kb/946428

     

    SCOM warnings and errors; event id 4503, 10703. 1103 and 10102

    http://social.technet.microsoft.com/Forums/en-US/exchangesvrmonitoring/thread/28516ca3-ae97-49a2-bb72-d6814750813f

     

    Health Service Unloaded System Rule(s) Event 1102

    http://ianblythmanagement.wordpress.com/2009/02/16/health-service-unloaded-system-rules-event-1102/

    Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

     

    Hope this helps.

     

    Thanks.
    Nicholas Li - MSFT
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by vengawn Tuesday, July 05, 2011 7:06 PM
    • Unmarked as answer by vengawn Tuesday, July 05, 2011 7:08 PM
    Friday, July 01, 2011 7:46 AM
  • Nicholas,

    The third article looks like the problem I am having, but the fix says to rename a file called "Program" on the root of C:\. I looked on the computers I was having this trouble with, but none of them have this file. The other two didn't seem relevant to my situation.

    Thanks

    Thursday, July 07, 2011 2:52 PM
  • Hi there,

    Try the following in case you did not solve it jet:

    - LogIn on the client machine and delete the Agent through the Configuration Panel;

    - Delete the Microsoft Monitoring Agent map from C:\Program Files;

    - Go to Agent Managed (under Administration in SCOM Console) and delete the agent of depending client;

    - Now for just in case, refresh the "Agent Managed" tab so you're sure agent is deleted;

    - At last install the agent again through the Operation Manager Console. Wait a few moments and the issue will automatically dissapear (in case if its an Monitor Alert automatically, Alert Rules needs to be closed manually).

    Please inform me if it succeeded. I had the same issue and that solved it :)

    Monday, June 23, 2014 8:53 AM