You are browsing the archive for 2012 July.

System Center 2012 CU2 available

10:01 am in operations manager, SCOM, sysctr by Dieter Wijckmans

 

Microsoft is continuously developing and improving the System Center 2012 suite. A proof is the recent release CU2.

The majority of fixes are for DPM, Service manager and orchestrator but other minor fixes are also available for SCOM.

For a detailed overview of all the problems this CU2 fixes take a look here: http://support.microsoft.com/kb/2706783/en-us

Download for

DPM: http://www.microsoft.com/en-us/download/details.aspx?id=30413

SCOM: http://www.microsoft.com/en-us/download/details.aspx?id=30421

As more blog posts about installing CU2 emerge I’ll update the list below:

Kevin Greene already wrote a detailed blog post about installing the CU2 update on a SCOM installation: http://kevingreeneitblog.blogspot.be/2012/07/scom-2012-deploying-cumulative-update.html

SCOM: Install both SCOM2007R2 and SCOM2012 console

1:43 pm in operations manager, SCOM, sysctr by Dieter Wijckmans

 

In this blog post I’m going to show you how you install both consoles on your workstation. I visit a lot of customers lately who have either SCOM2007R2 or SCOM2012 installed. So I recently also installed the SCOM2012 management console on my laptop to have them both on my machine.

By default it’s not possible to install the SCOM2012 console on a workstation which have already SCOM2007R2 installed.

It will propose to upgrade the existing console but unfortunately there’s no option to install side by side.

SNAG-0049

So first upgrade the SCOM2007R2 console to SCOM2012.

Afterwards you need to reinstall the SCOM2007R2 console:

SNAG-0054

Select only the “User interfaces” option which is in fact the SCOM console:

SNAG-0055

So after you’ve installed open up the 2 consoles.

CAUTION: Because you have performed an upgrade the old connection to the SCOM2007R2 management group were still saved. So connect towards your new SCOM2012 management group and you’re all set:

SNAG-0056

So fill in your new server and hit connect:

SNAG-0057

Success!

SNAG-0058

SCOM: Failed to deploy Data Warehouse Component

12:38 pm in SCOM, SCOM 2007 by Dieter Wijckmans

 

During a recent health check at a customer site I found that the RMS in a SCOM2007 install was in critical state. During my health check this is basically the first thing I check because in SCOM2007 this is still the heart of your environment.

Check of  the health explorer revealed the following rather odd message:

Printscreen 1

The Data Warehouse Database Component Deployment Recovery State – (Data Warehouse Synchronization Server) is in critical error.

First step of my troubleshoot is to check the event log of the RMS server for errors indicating this issue.

The following message was reported which caused this monitor to go to critical state:

Printscreen 2

Full message:

Event ID:       31565

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: ‘c9942f8c-3e77-e09d-1864-16db528bc3d2′; Target: Database, Server name: “Dbaseserver”, 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’.

After troubleshooting the issue once more I found out that it happened right after I have implemented the new version of Windows Server Operating System Management Pack (6.0.6972.0) more specific the “Windows Server Operating System Reports” Management Pack which is a part of the management pack.

Printscreen 3

After carefully investigating I found in the Management pack guide (which can be downloaded here) following statement in the previous version which was not installed yet on the environment (page 8):

“The Microsoft.Windows.Server.Reports Management Pack will only import on systems that use SQL Server 2008 as the Database and is not currently supported on SQL Server 2005.”

As the customer is still on SQL 2005 dbase this was the cause. After removing the management pack from the environment the error disappeared and the RMS came back healthy again.

Lesson Learned here: Always check the management pack history fully and not just the latest changes.

SCOM: Update ACS: The curious case of the Invalid column name ‘DescHash’

10:43 pm in Uncategorized by Dieter Wijckmans

Recently I came across an issue where there was not much info on the web so I thought I would write it on my only sketch book (yep this blog) for my reference and if you have found this post you’ll probably have the same issue so here comes my solution!

Case:

After upgrading SCOM2007R2 CU5 to CU6 level I noticed that my ACS reports were not working anymore.

I’ve checked the server and found out my Audit Collector service wasn’t running anymore on my Collector.

After carefully investigating the event log on my ACS Collector Server I found the following message popping up in the Operations Manager Log:

Event 4618: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name ‘DescHash’.

SNAG-0019

Followed by the message that the service was unable to start due to this error and was shutting down.

SNAG-0020

Hmmm apparently something went seriously wrong during the upgrade in the field of SQL.

Solution

Here’s how I fixed it eventually:

First we need to make sure that we detect the active partition in the ACS Database by running the query below:

Select PartitionId from dbo.dtPartition where status=0

SNAG-0022

Now running the following statement towards the active partition to add the DescHash to the partition.

SNAG-0023

Restart the Audit Collection Service on your Audit Collection server and recheck for errors. Normally the Service should keep running and you should see some data coming in if you have already ACS forwarders set up.

Special thanks to Daniele Grandini for pointing this out to me.

SCOM: The great error messages of scom2012: Common.UnknownServiceException.

10:45 pm in Uncategorized by Dieter Wijckmans

Yesterday I launched my SCOM2012 environment in my lab to test some scripts to find the error message below when I started the management console:

printscreen-0100

No reason or indication is given for the error message. A quick search online showed that it had to do with the fact that my environment was still in eval instead of retail. Which is possible because I installed this version with the RTM bits and updated it to the retail version afterwards.

Consult KB 2699998 for this: http://support.microsoft.com/kb/2699998

So let’s get started.

If your eval is already expired your not able to connect to your management server anymore thus not able to set the new license key you’ll receive the message below when starting the PowerShell session:

1

The trick is to reset your servers date to a date within your eval period:

printscreen-0102

printscreen-0103

Hint: If you are running this machine in a Hyper-v environment make sure to temporarily disable the Time Synchronization integration service to prevent the server from reverting to the time of the Hyper-V host.

printscreen-0101

So now execute the instructions in the KB again to fill in your System Center 2012 product key (note that since System Center 2012 there are no separate product keys for the different products anymore but there’s 1 general key.

For copy purposes are these the commands to run:

import-module operationsmanager

New-SCOMManagementGroupConnection

Set-SCOMLicense “your licensekey”

To check the status: Get-SCOMManagementGroup | ft skuforlicense, version, timeofexpiration -a

 

printscreen-0105

The eval is still in there.

Now reboot your SCOM2012 management server and rerun the last command to double check your timeofexpiration:

SNAG-0029

Succes Smile

Last but not least: Don’t forget to reset your server clock to the correct time by either resetting it manually or enabling the Time synchronization service of Hyper-V again.

SCOM: The next generation of Authoring tools is finally here

10:41 pm in Uncategorized by Dieter Wijckmans

 

Finally the next generation of authoring tools has arrived to make your authoring life easier and use a combination of the different tools to develop your management packs faster and easier.

lolcat-hooray

Already showcased at MMS and now finally available for download.

Get them here:

Visio Management Pack Designer (VMPD): http://www.microsoft.com/en-us/download/details.aspx?id=30170

Visual Studio Authoring Extensions (VSAE): http://www.microsoft.com/en-us/download/details.aspx?id=30169

Make sure to check out the WIKI’s here:

VMPD: http://social.technet.microsoft.com/wiki/contents/articles/5235.visio-management-pack-designer-for-system-center-2012-operations-manager-en-us.aspx

VSAE: http://social.technet.microsoft.com/wiki/contents/articles/5236.visual-studio-authoring-extensions-for-system-center-2012-operations-manager-en-us.aspx

More to come on this 2 secret weapons in the warfare of creating your management packs.