Microsoft System Center Operations Manager or SCOM 2007 can be a blessing when it is working.\u00a0 When it is not, it is a real pain to troubleshoot.<\/p>\n
It all began when the database is full and it kept complaining until it stopped working.\u00a0 The database could not be accessed as the admin account has been deleted.\u00a0 So we changed to admin to another account.\u00a0 Thereafter the management server turned gray and permanently refuse to go green.<\/p>\n
<\/p>\n
We reentered the service accounts credentials in the Services MMC and in the console.\u00a0 The status of the management server turned green.\u00a0 This is good.\u00a0 Unfortunately it stopped logging alerts.\u00a0 No alerts\u00a0 =\u00a0 no notifications.<\/p>\n
Some people suggested this could be due to SQL broker that is not working.\u00a0 Yes it was running. Even though the status shows disabled.<\/p>\n
Stopping and restarting the services on the monitored or client servers revealed that the communication is broken.\u00a0 The clients reported events 20070<\/p>\n
The OpsMgr Connector connected to servername.xxx.yyy, but the connection was closed immediately after authentication occured.\u00a0 The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration.\u00a0 Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.<\/p><\/blockquote>\n
That doesn’t sound good.\u00a0 Google returns errors and solutions\u00a0 relating to monitoring servers in the DMZ.\u00a0 After about 1 month of troubleshooting, I threw in the towel and try to reinstall on to a virtual server.\u00a0 It looks good, and soon the old non-functioning SCOM will be reinstalled.<\/p>\n
Backup?\u00a0 This was not done, as it was not considered production.\u00a0 Duh!<\/p>\n