Tuesday, January 17, 2012

SCOM Zombie PSA#30: Event ID 21042

 

A few weeks ago someone (aka zombie) thought they were manually uninstalling a SCOM agent from a managed server. What they didn’t know was that they were NOT on the server they thought they were on but it was the Root Management Server. What comes next? They uninstalled the SCOM software from the Root Management Server. I knew this because I was on the server troubleshooting bad agents and everything closed out on me. I immediately check my event logs to see why, and the Operations Manager event log was GONE. I know, RIGHT! (aka Zombie Apocalypse)

But luck was on our side, and we were able to re-install SCOM back and apply the backup keys. everything was going good so we thought.

About 24 hours later the Root Management Server had the following alerts in the Operations Manager event log. I mean nothing but this event; it was pouring a lot of these event id every second.

There was not much out there in the world on this event id that we could find.


Event Type:       Information

Event Source:    OpsMgr Connector

Event Category: None

Event ID:           21042

Computer:        RMS.FQDN

Description:

Operations Manager has discarded 1 item in management group <Management Group Name>, which came from $$ROOT$$. These items have been discarded because no valid route exists at this time. This can happen when devices are added to the topology but the completed topology has not been distributed yet. the discarded items will be regenerated.


Funny thing was each of the management Servers that had agents report to them were being flooded with these alerts.


Event Type:       Information

Event Source:    OpsMgr Connector

Event Category: None

Event ID:           20000

Computer:         RMS.FQDN

Description:

A device which is not part of this management group has attempted to access this Health Service. Requesting Device Name: ServerName.FQDN 


The quick fix was to “”Re-Enter”” each of the Run-As accounts back manually. Once this was done, the 21042 alert went away. However many of the event id 20000 didn’t all clear up. it took some manual process of stopping the agent service and deleting the Health Service State folder and re-starting the service again to make the some of the agents communicate back.

In my lab I was able to re-create the issue and correct it by doing this. I don’t fully understand all the details just yet but I’m working on that, if I can get some more time to it.

SCOM Zombie PSA#29: Alerts in console not showing up

 

This caught me off guard just now. When I opened my web console, there was a couple of alerts but when I opened my console up no alerts displayed. funny since it stated 8 active alerts.

image

The quick fix was that my Alert Detail tab was all the way up, so I just dragged and dropped it down to expose my alerts.

image

Wednesday, December 21, 2011

HAPPY “ZOMBIE” HOLIDAYS

 

To all the IT Zombies out there, I’ll continue posting more stuff after the New Year, but until then I want to tell everyone to enjoy this with family, friends and co-workers.

I only ask that each of you take to stop and help total strangers; in return your actions should encourage them to do the same.

Monday, December 5, 2011

SCOM Zombie PSA#28: Windows Server Operating System Management Pack v6.0.6958.0 (BUGGY)


Last week I deployed this management pack into my lab OM07, fresh system with  no other management pack really on it. The odd thing was that the event logs was kicking out an event of 31565 about every ten minutes. My active alert, may or may not kick out an alert; it did generate an alert about every 6 hours or so.
Here is what I gotten in my event logs and eventfully the alert itself.
--------------------------------------------------------------------------------------------------------------------------
Description:
Failed to deploy Data Warehouse component. The operation will be retried. Exception 'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: Script, Id: '3a49a530-26a2-c525-35fe-69df5898f150', Management Pack Version-dependent Id: 'dbf18271-9643-32ff-4849-00d79d9e2a9d'; Target: Database, Server name: 'XXXXXX', Database name: 'OperationsManagerDW'. Batch ordinal: 1; Exception: Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon.
Incorrect syntax near ','.
Incorrect syntax near ','.
Incorrect syntax near ','.
Incorrect syntax near ','.
Incorrect syntax near the keyword 'ELSE'.

One or more workflows were affected by this.

Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Component
Instance name: xxxxx.xxxx.xxx
Instance ID: {4836F627-4378-5EDF-0DE7-97DAE0A2C939}
Management group: LAB
--------------------------------------------------------------------------------------------------------------------------
I found a couple of things on the web that suggested to do the following:
  • I tried to do a repair on the for the Reporting Data Warehouse
  • I restarted the services for SQL and OpsMgr
  • Verified nothing new was installed on my server since I noticed the issue
What worked, came from a friend of mine that suggested the Management Pack was buggy and not my system. So I removed the newest management pack from my system, and then deployed the older version I had. It appears to be working right now.  Have not seen anything from it in a while.
  • The final fix was to remove the management pack and revert to the old one.
I would love to know if other experienced this and if they knew any other working alternatives that may be an option.
------------------------------------------------------------------------------------------------------------------------


UPDATED INFORMATION:

There is another resolution I am told by a SCOM PFE that you can just uninstall the "Windows Server Operating System Reports" Management Pack. What this resolves is the two reports that only work on SQL 2008.

Bob Cornelissen & Marnix Wolf had blogged about this a while back and are requesting a better management pack.

But I’ve ran into another problem in a few production systems where removing the management pack was not an option. So the only option I was able to do at the time was turning this alert off via the overrides.

Wednesday, November 30, 2011

SCOM Zombie PSA#27: Microsoft SQL Server 2012 Release Candidate (RC)

I am not 100% sure when Microsoft released SQL Server 2012 Release Candidate (RC). And you can download it once you register for it. I am very interested in learning if System Center Operations Manager 2012 will play nice with it, and I don’t think there will be any support for OpsMgr 2007 R2. Here is what they have to say about it.

“SQL Server 2012 will deliver mission-critical confidence with AlwaysOn availability for faster failover and greater hardware utilization and in-memory ColumnStore for 10x the data warehouse performance gains. SQL Server 2012 will also enable breakthrough insights with business intelligence solutions such as Power View for stunning, interactive data visualizations and enhancements to PowerPivot. Lastly, SQL Server 2012 will uniquely support hybrid IT environments with common management and development tools, scale elastically, and extend applications directly to the cloud through SQL Azure.”

Register to access technical product resources—such as forums, solution accelerators, white papers, and webcasts—at the SQL Server 2012 Resource Page.

Review Microsoft SQL Server 2012 RC system requirements

Register for evaluation so that you may download and install the full-featured software for 180-day trial. Receive follow-up email with resources to guide you.

Additional Information:

  • Available in these editions: 32-bit and 64-bit
  • Available in these languages: Chinese (Simplified), Chinese (Traditional), English, French, German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, Spanish

Thursday, November 17, 2011

SCOM Zombie PSA#25: MMS 2012 Registration Open

 

Registration began today for Microsoft Management Summit 2012 (#MMS2012). If you register by January 27, 2012 you should be able to some cash. about $300 bones, for the early bird special. After that you can expect to pay $1800 for the conference itself and to stay at the  Venetian Hotel, it will cost $2776.

Everything you need or want to know can be found here.

As much as I would love to go, I don’t expect that I will be able to this year, unless something special happens. I should be following the twitter feeds to keep up on everything. I did attend #MMS2011, and it was a blast; I really expect that this year will be huge with a large focus SCOM 2012.