Comments on: Blog

By: Blake

Wed, 14 Sep 2011 21:14:25 GMT

I hate to beat a dead horse, but I'm still getting similar errors when I run any of the OM reports. The DW reports work fine.

I enabled remote errors on my SQL Reporting Server, so I have a little more detail. For instance when I run the Agents - Agent Hotfix Report (OM) report, I receive the following error:

An error has occurred during report processing.
Query execution failed for dataset 'OperationalDataBaseMain'.
Invalid object name 'MT_HealthService'. <--- REMOTE ERROR!!!!

Any ideas? I'm still digging. If I find the answer I'll repost; hopefully someone else has already crossed this bridge.

By: new2scc

Mon, 21 Mar 2011 12:10:13 GMT

Hi, just wondering if there is any news of Version 3 being made available and what new reports etc may be included?...

Cheers

By: Scom4v

Tue, 28 Sep 2010 10:33:15 GMT

Hi,

I have created the DataSource and Imported the MP but I have only 2 reports in the SCC Health Check reports folder :

Alerts - Alerts Resolved Closed by UserID (DW)

Misc - Management Packs (OM)

Thanks,

Abder

By: elb01pd

Thu, 29 Jul 2010 13:22:43 GMT

Everything is fine now, I had to tick "Impersonate the authenticated user after a connection has been made to the data source" as well.

By: new2scc

Thu, 29 Jul 2010 12:20:32 GMT

Oskar/Pete,

One alert report i've been struggling badly with and believe it would be VERY useful to have is a report to show all critcial alerts which are in resolution state NEW for > 24 hrs, which can be run for the previous week/month or whatever timeframe.

The purpose is that our organisation is introducing internal service level agreements were all critical alerts should be acknowledged within one working day. Therefore we need to be able to run reports to check what alerts fell outside the SLA, and therefore know the service/service owner who needs to address the issues. In my SCOM deployment I have created additional resolution states of Acknowledged (1), Work In Progress (2) ontop of the default New (0) and Closed (255) states.

At first glance I thought this would be quite straight forward but being a bit of a novice and the more I looked into it, the more difficult is seemed to achive (i posted about this on several sites and looked at others eg http://social.technet.microsoft.com/Forums/en-US/operationsmanagerreporting/thread/b13d7b90-193e-4633-b968-caaafb153798 - I think the problem lies in how to calc the correct time in a particular state since it seems to raise another entry for the alert with the changes resloution state.

If you have a sample SQL to do this it would be great if you could send me it and if you felt it was worth including in your V3 MP. Ideally if you could run a report to show alert Name/desc, Date/time created, Date/Time resolved, Lenthg to time in state (for NEW), closed By, Owner where you could maybe specify via params time period eg previous week/monthetc...

Anyway thats my suggestion - I hope it makes sense and if you (OR ANYONE ELSE) had any ideas of a SQL script which I could work with to get me going in the meantime I'd greatly appreciate it!!...

Many thanks

PS Had emailed this but not sure if you got it!!

By: elb01pd

Thu, 29 Jul 2010 09:29:14 GMT

hello, I'm using R2 as well and had the same error. I did the same as Layne and I got 6 of the reports working. For the rest of the reports I get the known error.

By: elb01pd

Thu, 29 Jul 2010 09:23:42 GMT

Write a comment...

By: Layne

Wed, 21 Jul 2010 22:15:39 GMT

Sameer, even though I'm using R2 I had the same error as you. I'm not sure if this will help you, but I had copied the connection string from the Data Warehouse Main datasource and changed the initial catalog. However, I needed to remove the Integrated Security=SSPI before the reports would work.

By: Sameer

Mon, 19 Jul 2010 14:23:45 GMT

Hi OsKar,

Yes, I did name it OperationalDatabaseMain. I just copy pasted of what you had in the document.

Edit-

OK, I checked on the name. In the document the name is supposed to be "OperationalDataBaseMain" I tried to change this name to "OperationalDatabaseMain" as Oskar advised. But still its giving me the same error.. :(

By: Oskar Landman

Fri, 16 Jul 2010 23:24:29 GMT

Sameer,

Did you named the data source OperationalDatabaseMain ?

I believe it is case sensitive.

By: Sameer

Fri, 16 Jul 2010 22:03:21 GMT

Thanks Guys. Great Reports, if I can get it working :)

I am using SP1 and did the changes that Pete suggested. Imported fine.

BUT am getting "An error occurred during report processing. query execution failed for the data set 'operationaldatabasemain' ... " error. I did change the credentials as suggested in the last part of the document. But that didn't help.

For some of the reports I also get "....Query execution failed for data set 'SQL_SCOM_OP'.." error.

Any help?

Thanks

Sameer

By: Oskar Landman

Fri, 16 Jul 2010 19:32:47 GMT

Thanks Peter!

Looks like this will help people who are still at SP1. Sorry I didn't mention R2..... :(

By: PeterW

Fri, 16 Jul 2010 12:47:15 GMT

Great stuff - Really helpful!
Since we are still on OpsMgr 2007 SP1 I could not import it for sure. So I changed the references in the XML and it worked perfectly.
Now I have all those nice reports available in SP1 and the best: They are working fine.
Here are the references I am using:

Alias="SC"
ID Microsoft.SystemCenter.Library
Version 6.0.6278.0

Alias="Windows"
ID Microsoft.Windows.Library
Version 6.0.6278.100

Alias="Health"
ID System.Health.Library
Version 6.0.6278.0

Alias="System"
ID System.Library
Version 6.0.6278.0

In case someone wants to try, please check your versions in the OpsMgr console and modify the XML accordingly.