Alfred's New Ramblings

SCOM problems

Microsoft System Center Operations Manager or SCOM 2007 can be a blessing when it is working.  When it is not, it is a real pain to troubleshoot.

It all began when the database is full and it kept complaining until it stopped working.  The database could not be accessed as the admin account has been deleted.  So we changed to admin to another account.  Thereafter the management server turned gray and permanently refuse to go green.

We reentered the service accounts credentials in the Services MMC and in the console.  The status of the management server turned green.  This is good.  Unfortunately it stopped logging alerts.  No alerts  =  no notifications.

Some people suggested this could be due to SQL broker that is not working.  Yes it was running. Even though the status shows disabled.

Stopping and restarting the services on the monitored or client servers revealed that the communication is broken.  The clients reported events 20070

The OpsMgr Connector connected to, but the connection was closed immediately after authentication occured.  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.  Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.

That doesn’t sound good.  Google returns errors and solutions  relating to monitoring servers in the DMZ.  After about 1 month of troubleshooting, I threw in the towel and try to reinstall on to a virtual server.  It looks good, and soon the old non-functioning SCOM will be reinstalled.

Backup?  This was not done, as it was not considered production.  Duh!

SQL Broker

Leave a Reply

Your email address will not be published. Required fields are marked *