New Base OS SCOM MP (6.0.6958.0) and problems with report deployment

New Base OS SCOM MP (6.0.6958.0) and problems with report deployment
SHARE
Mark Blok,

Today I had my first expierence with the updated Windows Server OS Management Pack which can be downloaded at the following location: http://www.microsoft.com/download/en/details.aspx?id=9296

Of course I read the manual before importing it into a test Operations Manager Management Group. But I have to admit I oversaw one important comment in the guide.

So I imported all the .MP files and as normal practice I monitored the errors in the console and in the eventlog soon after the import finished. The error that appeared in the eventlog after a couple of minutes was the following:

Log Name:      Operations Manager

Source:        Health Service

Modules Date:          24-11-2011 10:23:46

Event ID:      31565

Task Category: Data Warehouse

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      <RMS FQDN>

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: '<DB ServerName>', 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: <RMS FQDN> Instance ID: {E5EEDF23-3C06-B007-D7F1-E6D2BA8659DF} Management group: <SCOM Management Group Name> Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">   <System>     <Provider Name="Health Service Modules" />     <EventID Qualifiers="49152">31565</EventID>     <Level>2</Level>     <Task>3</Task>     <Keywords>0x80000000000000</Keywords>     <TimeCreated SystemTime="2011-11-24T09:23:46.000000000Z" />     <EventRecordID>18630414</EventRecordID>     <Channel>Operations Manager</Channel>     <Computer><SCOM RMS FQDN></Computer>     <Security />   </System>   <EventData>     <Data><Management Group Name></Data>     <Data>Microsoft.SystemCenter.DataWarehouse.Deployment.Component</Data>     <Data><SCOM RMS FQDN></Data>     <Data>{E5EEDF23-3C06-B007-D7F1-E6D2BA8659DF}</Data>     <Data>DeploymentException</Data>     <Data>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: 'SCOM DB Server Name', 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'.</Data>   </EventData> </Event>

After 10 minutes the same error appeared in the Operations Manager EventLog and this keeps repeating every ten minutes. So I decided to pick up the guide again and once again it became clear why this step cannot be forgotten! The new management pack contains a new .MP called Microsoft.Windows.Server.Reports.mp

In the MP guide it is clearly stated that this MP is not compatible with SQL 2005 and only with SQL 2008. This means the new reports are not available if you are running the OpsMgr Databases on SQL 2005. The solution is of course simple, just delete te reports MP or move your databases to a SQL 2008 installation.

After deleting the MP the error events in the Operations Manager log are not reoccuring and the correlated Alert in the OpsMgr Console closed itself.

Blog: Virus Scan Exclusions in MOM 2005 / SCOM 2007 / SCOM …

  This Article will describe Virus Scan Exclusions in System Center Operations Manager 2007 / 2012.  Although there is current no official statement on these exclusions based on the previous article http://support.microsoft.com/kb/975931 I would rec…

Microsoft Assessment and Planning Toolkit 6.5 beta Now Avai…

Microsoft Assessment and Planning Toolkit 6.5 beta Now Available! The journey to the cloud is now smoother than ever with the Microsoft Assessment and Planning (MAP) Toolkit 6.5 Beta. The MAP Toolkit’s new capabilities help users to securely assess hete…

Hyper-V community event in Amsterdam on 19th of January

UPDATE: ALL PRESENTATIONS WILL BE IN ENGLISH! On January the 19th, 2012 the Hyper-V.nu crew will organise a very cool event again! Both the speakers and the subjects are valid reasons to visit this event and you may not miss it! Admission is free! This event …

Collecting Data from Hyper-V hosts and VM’s

There haven’t been any new blogs on Hyper-V.nu in the past weeks because of …. you know … an absolute dearth of time. It so happened that my other Hyper-V.nu colleagues had the same luxury problem in these economical challenging times. So while I was doing a …

The Experts Conference 2011

In the past week I attended TEC Europe 2011 in Frankfurt and presented a Hyper-V Storage Deep Dive session for a small but highly specialized audience. TEC2011 is certainly not known for its sheer size but because of its small size it is very easy to get into…

Blog: System Center Operations Manager 2012 “More tha…

This is part 4 of the More that meets the eye series and will explain the why the changes between 2007 R2 and 2012 are so really cool and interesting!! Part 1 - System Center Operations Manager 2012 “More that meets the eye” Part 1–SCOM2007R2–SCOM2012 Cla…

Remediation with the newly improved DCM feature in SCCM 2012

Remediation with the newly improved DCM feature in SCCM 2012
SHARE
mark,

One of the features I personally liked in SCCM 2007 was the DCM (Desired Configuration Management) feature. This gave you as an admin the ability to build all kinds of configuration items which were evaluated against the systems of choice. So you could check for example how many machines were compliant with respect to specific software versions. So it was very easy to report on application version management. You could also write your own scripts, and use those scripts to check all kinds of stuff on your machines and report on their compliancy. So pretty powerful!

Read More »

Follow Inovativ on Twitter Visit Inovativ.nl Visit Inovativ.nl
Most read
Search
Keywords
Archive