Creating a Data Source for the Operational DB on OpsMgr 2012 R2 Reporting Server

Creating a data source to for the OpsMgr Operational DB is a very common practice. This is required for many 3rd party OpsMgr reports. Kevin Holman blogged the instruction here. In my case, I’m creating a data source called OperationalDataBaseMain for my favourite report MP SCC Health Check Management Pack. Other than the data source name difference between Kevin’s blog and what’s required for SCC Health Check MP, Kevin configured the data source with the option “Credentials are not required”, which is essentially using the SSRS service account (DW Reader account). In the SCC Health Check MP documentation, it suggests

“Data Aggregation” field became empty in OpsMgr 2007 linked Performance Report

Today I needed to change some parameters in a linked performance report in one of the OpsMgr 2007 R2 management groups at work. When I opened the report property, the Data Aggregation field somehow became blank and greyed out: As the result, when I tried to run the report, I get this error: I found a blog article from Dieter Wijckmans “SCOM 2007: Scheduled reports failing”, it indicates it’s because there are duplicate management group ID specified in the report parameters. Dieter’s fix doesn’t really apply to me as the my report is not a scheduled report, however, my approach

OpsMgr 2012 App Advisor Web Console Failed To Run Reports After DW Database Move

Previously I’ve blogged my experience in migrating from OpsMgr 2012 RTM to SP1 which involved moving all databases to a new database server running SQL 2012. Since then, I’ve noticed the instruction in moving Operational DB published in TechNet is actually missing a step, which I’ve blogged here. Over the last few days, since it was the long weekend down here in Victoria, I spent some time setting up the Talking Heads web application to explorer APM in OpsMgr 2012. I was following the instructions in Chapter 9 in the Mastering System Center 2012 Operations Manager book. The instructions in

“Cannot initialize report” Error When Running SCOM Reports

Yesterday, I noticed I get this error when I tried to run some reports in the System Center Central Health Check Reports MP in my home SCOM 2007 R2 environment: “Value of 01-Jan-01 12:00:00 AM” is not valid for ‘value’. ‘Value’ should be between ‘MinDate’ and ‘MaxDate’. I then realised I get exactly the same error on any reports which contain datetime pickers in the report. Long story short, after spending some time troubleshooting this issue, including updating my SCOM 2007 R2 environment from CU5 to CU6 as this blog post has suggested: SCOM 2007 R2 – Reporting : Value

Using SCOM To Count Logs and Produce Reports

Recently, I’ve been asked twice to produce daily reports involves counting some kind of logs: Scenario 1: The support team need to count number of Application event log entries of events with a specific event ID. A daily report is required to list the number for each computer. Scenario 2: An application produces a log file each day. The support team need to count the number of a specific phrase appeared in previous day’s log file. A daily report is required to list the count number for each computer. The solution I produced for both scenarios are very similar. so

Reports not updated in SCOM SQL Reporting Service When the Management Pack was Updated

I ran into an issue today. I have updated a report in a management pack. After I updated the version number, sealed it and imported the updated management pack into SCOM, the report that I have modified did not get updated in SQL Reporting Service (SRS). Generally, once a new MP is imported into a management group, within few minutes, the reports within the MP should be deployed to SRS. This was the case when I updated the very same MP in Development environment, but in Production, I waited few hours and nothing has happened. After few hours, I finally

%d bloggers like this: