Agent disappeared automatically and it appeared in pending management after 6 months.

Question

We had a server (Windows server 2003 64 bit) which was installed and was working fine. Suddenly it disappeared automatically and it appeared in pending management after 6 months. We noticed it only when it came to pending management that the server disappeared
from Agents managed TAB. When we checked the server and found that SCOM was uninstalled or disappeared or what ever. We re installed SCOM now and now from past 1 week we see that the agent is fine.
We are using SCOM 2007R2 CU4 in our environment.
I want to know the reason for this. Post installation of SCOM after this incident we checked the event logs and found the data for the last working of SCOM in that server and found the below events. I was not able to get that much old data in the SCOM Management
server. But got the data from the Agent.
Screen shot:
===========================
Event id: 21033
103
101
21403
21402
5399
1000
45
Below are the contents of the event log
21033:
========
The Management Group CINSCOM was removed from the Microsoft Operations Manager Agent.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
=======================================================================
Event id: 103
==========
HealthService (2912) Health Service Store: The database engine stopped the instance (0).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
======================================================================
Event id:101
=========
HealthService (2912) The database engine stopped.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
==========================================================================
Event id :21403
============
The process started at 12:22:31 PM was terminated because the HealthService requested the workflow to stop, some data may have been lost.
Command executed: "C:\WINDOWS\system32\cscript.exe" //nologo "C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 112\4723\AD_Replication_Partner_Op_Master_Consistency.vbs"
cinmlgc25.e2k.ad.ge.com false
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 112\4723\ 
One or more workflows were affected by this.  
Workflow name: AD_Replication_Partner_Op_Master_Consistency.Monitor 
Instance name: CINMLGC25 
Instance ID: {E49A1DCD-88C3-5615-102B-E8321298AEFF} 
Management group: CINSCOM
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
================================================================================
Event id:21402
=============
Forced to terminate the following process started at 12:22:31 PM because it ran past the configured timeout 120 seconds.
Command executed: "C:\WINDOWS\system32\cscript.exe" //nologo "C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 112\4723\AD_Replication_Partner_Op_Master_Consistency.vbs"
cinmlgc25.e2k.ad.ge.com false
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 112\4723\ 
One or more workflows were affected by this.  
Workflow name: AD_Replication_Partner_Op_Master_Consistency.Monitor 
Instance name: CINMLGC25 
Instance ID: {E49A1DCD-88C3-5615-102B-E8321298AEFF} 
Management group: CINSCOM
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
=================================================================================
Event id 5399
==========
A rule has generated 50 alerts in the last 60 seconds.  Usually, when a rule generates this many alerts, it is because the rule definition is misconfigured.  Please examine the rule for errors. In order to avoid excessive load, this rule will be
temporarily suspended until 2013-10-21T12:32:11.0039243-04:00. 
Rule: Unexpected_SAM_Failure_5_Rule 
Instance: CINMLGC25 
Instance ID: {E49A1DCD-88C3-5615-102B-E8321298AEFF} 
Management Group: CINSCOM
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
===================================================================================
Eventid: 1000
==============
AD Replication Partner Op Master Consistency : The script 'AD Replication Partner Op Master Consistency' failed to executethe following LDAP query: '<LDAP://loumlgc02.e2k.ad.ge.com/DC=e2k,DC=ad,DC=ge,DC=com>;(&(objectClass=infrastructureUpdate)(fSMORoleOwner=*));fSMORoleOwner;Subtree'.
The error returned was 'Table does not exist.' (0x80040E37)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
======================================================================================
Event id:45
============
AD Replication Partner Op Master Consistency : Unable to determine infrastructure Op Master on domain controller 'loumlgc02'.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
=======================================================================================
Can any one please help...

Answer 1

Hi,
Based on my understanding, that you re-installed your SCOM, and now everything works fine. You want to know that why your SCOM run into problem 6 months before, right?
According to the event logs in your agent, we could not tell what happened to your Operation manager. What I can see is that the management group was removed from the agent then. And there are some errors when moniored by the former management group.
I would like to suggest you check out what actions have you do on your former management group 6 months before. Maybe we can check the operation manager logs on your management server.
Regards,
Yan Li
Regards, Yan Li