Friday, April 24, 2015

Teaser: How To Solve Event ID‘s 11502, 33333 & 4502

Quiet recently I had to solve an issue where the SCOM 2012x Management Server logged these nagging and BAD Event ID’s:

  1. 11502
    The Microsoft Operations Manager Connector Framework Alert Forwarding module failed to mark an alert for forwarding because the connector the module is configured for no longer exists. Connector Id: [GUID]

  2. 33333
    Data Access Layer rejected retry on SqlError. The UPDATE statement conflicted with FOREIGN KEY constraint "FK_Alert_ConnectorId". The conflict occurred in database "OperationsManager", table "dbo.Connector", column "ConnectorId"

  3. 4502
    A module of type "Microsoft.EnterpriseManagement.Mom.Modules.McAlertWriteAction" reported an exception System.Data.SqlClient.SqlException (0x80131904): The UPDATE statement conflicted with the FOREIGN KEY constraint "FK_Alert_ConnectorId:. The conflict occured in database "OperationsManager", table "dbo.Connector", column 'ConnectorId'.

It took me a while to get to the bottom of it all, but finally I FIXED it! The last days I didn’t have the time to write an article about it. But soon I’ll write a posting for it. What caused it, and how to solve it. So stay tuned!

Free eBook: Microsoft System Center Operations Manager Field Experience

A few days ago Microsoft released a new FREE ebook, titled: Microsoft System Center Operations Manager Field Experience.

The book is written by people who have a lot of experience with SCOM. They work on a daily basis in the ‘trenches’ so they know what they’re talking about.

Intended audience (taken directly from the website): ‘…If you’re responsible for designing, configuring, implementing, or managing a Microsoft System Center Operations Manager environment, then this book is for you. This book will help you understand what you can do to enhance your Operations Manager environment, and will give you the opportunity to better understand the inner workings of the product, even if you are a seasoned Operations Manager administrator…’

And: ‘…This book assumes that you have a deep working knowledge of the Operations Manager product and its concepts, that you understand the concept of management packs, and that you are basically familiar with Microsoft Azure as an infrastructure-as-a-service platform. This is a book about best practices, design concepts, how-tos, and in-depth technical troubleshooting. It covers the role of the Operations Manager product, the best practices for working with management packs, how to use the reporting feature to simplify managing the product, how to thoroughly troubleshoot, and how to use and install Operations Manager in a Microsoft Azure Public Cloud environment…’

Book can be downloaded from here. The book also has companion content, to be downloaded from here.

Monday, April 20, 2015

What’s The Diff Between SCOM 2007 R2 Default MP & SCOM 2012 R2 Default MP?

Issue
Bumped into a SCOM 2012 R2 environment which was built from the ground up in order to migrate away from an existing SCOM 2007 R2 environment. So many unsealed MPs from the SCOM 2007 R2 environment were exported from it and imported into the SCOM 2012 R2 environment.

Among all those unsealed MPs it turned out that the Default MP of SCOM 2007 R2 slipped through and was imported into the SCOM 2012 R2 environment as well. And yes, even though the version number of that MP is lower than the default MP which was present in the SCOM 2012 R2 environment.

However, versioning is ONLY enforced when the MP is sealed. For unsealed MPs version numbers aren’t enforced. Ever…

Is it really an issue?
However, since the SCOM 2007 R2 MP contained many custom Views and so on, it was hard for me to really know the difference between these two Default MPs. So it was time to run a comparison between both Default MPs as they’re to be found on the installation media.

For SCOM 2012 R2 it’s really easy. Simply mount the iso and browse to the folder ~:\ManagementPacks and copy the file Microsoft.SystemCenter.OperationsManager.DefaultUser.xml to a dedicated temp folder.

For SCOM 2007 R2 it’s a bit more work. Mount the iso and browse to the folder ~:\Server\AMD64 and open the file OMServer.cab. Copy the file F_Microsoft.SystemCenter.OperationsManager.DefaultUser.xml.540EA3C0_A5E9_41EA_A585_822C09EA2650 to a dedicated folder and rename it to Microsoft.SystemCenter.OperationsManager.DefaultUser.xml by removing all the ‘trimmings’.

So now we’ve got the two ORIGINAL Default MPs. One from SCOM 2007 R2 RTM and another from SCOM 2012 R2 RTM. Time to run a comparison.

Tooling required
For this you can use many different tools. Even though I am big fan of Notepad++, in this particular case XML Notepad 2007 does a better job. Simply because this really monolithic tool is aimed only at XML for MPs, so here it works great with the additional tool XmlDiff started within XML Notepad 2007. Kevin Holman has written a posting about how to use this tool just for this, so no need for me to repeat it here.

And with the tool XmlDiff it turned out there aren’t that many differences at all.

Findings
Besides the obvious (version numbers) there are two  major differences:

The ColumnInfo entry is set to 30 in SCOM 2012 R2, compared to SCOM 2007 R2:
image

And the Default MP for SCOM 2012 R2 contains a filled out LanguagePack section whereas the one for the Default MP for SCOM 2007 R2 RTM is completely empty.
image

So as you can see, it’s not that much of a difference.

What to do?
Easy. SCOM 2007 R2 is dead (mainstream support ended on 7/8/2014!) and SCOM 2012 R2 is alive and kicking (mainstream support until 7/11/2017). So no need to drag on all that old legacy stuff into SCOM 2012 R2. Time to leave it behind.

Also THE opportunity the put all the ‘lessons learned’ into the real world. And one of those Best Practices is NOT to use the Default MP for ANYTHING, also not for Views in the Console.

So first all the Views present in the SCOM 2007 default MP were put into a dedicated MP of it’s own in SCOM 2012 R2. Afterwards the SCOM 2007 R2 Default MP was deleted and replaced by the original SCOM 2012 R2 Default MP as found on the installation media.

End of story.

Friday, April 17, 2015

Cross Post: Ex2010 MP Correlation Engine Doesn’t Generate Alerts

As we all know the Exchange 2010 MP is a MP of a rare breed. It uses the ‘Correlation Engine’ (CE) in order to generate Alerts. Even though the theory behind it is good, the execution has ‘some’ issues and nags, like using most of the Custom fields of an Alert generated by the CE, causing many automated solutions, depending on those fields to turn sour.

So I was glad when Microsoft introduced Exchange Server 2013 MP and dropped the Correlation Engine for the MP in order to monitor it.

However, there are many organizations out there who still run Exchange Server 2010 and use SCOM 2007 to monitor it. When you want to migrate to SCOM 2012x changes are CE will stop functioning by not generating alerts anymore.

Gladly PFE Jimmy Harper bumped into this situation already. He solved it – with help of one of his colleagues – and blogged about it.

The posting is to be found here.

New MP: SCDPM 2012 R2 MP Version 4.2.1276.0

Yesterday Microsoft released the MP for monitoring System Center Data Protection Manager 2012 R2, version 4.2.1276.0.

This MP also contains a Reporting MP, enabling you to report about your SCDPM environment. Want to know more about the Reports in this MP? Read this posting on the System Center Data Protection Manager blog.

The MP itself can be downloaded from here.

KB3035262: Troubleshooting MMA Connectivity Issues

Microsoft has updated KB3035262 all about solving connectivity issues with your SCOM 2012x Agents (Microsoft Monitoring Agents).

Whenever you want to troubleshoot MMA connectivity issues this KB is an excellent starting point.

KB3054347: Error 800706D3 Occurs & Push Installation Fails a MMA To WS2012

Microsoft has published a new KB all about troubleshooting error 800706D3 occurs and a push installation fails for an Operations Manager 2012 agent to Windows Server 2012.

See KB3054347 about this issue, it’s cause and how to solve it.