Creating a new data source for reporting against the Operational Database

Agent Proxy alerts - finding the right machine to enable agent proxy on using a custom report

Kevin Holman's OpsMgr Blog — Sat, 28 Jun 2008 00:04:22 GMT

Certain types of agents need the agent proxy setting enabled.  These are documented in various guides...

Which servers are DOWN in my company, and which just have a heartbeat failure, RIGHT NOW?

Kevin Holman's OpsMgr Blog — Sat, 28 Jun 2008 00:39:38 GMT

In OpsMgr 2007, when a agent experiences a heartbeat failure, several things happen.  There are

A report to show all agents missing a specific hotfix

Kevin Holman's OpsMgr Blog — Sat, 28 Jun 2008 01:11:51 GMT

  This is a continuation of my previous post on determining which agents are missing a hot-fix:

re: Creating a new data source for reporting against the Operational Database

Layne — Wed, 18 Feb 2009 03:36:09 GMT

Kevin, great blog. I setup the datasource as described here, but after importing your Agents_Missing_Hotfix.rdl and trying to run it, I get an error "the data source connection information has been deleted (rsInvalidDataSourceReference)". If I try to open it with Report Builder an error says the report cannot be opened because no data source is associated with it and to associate a model data source with the report and try again. This happens from the OpsMgr console and from SRS.

re: This datasource doesnt work for some reports?

kevinhol — Wed, 18 Feb 2009 03:43:42 GMT

Yeah - shame on me - I dorked up the data source in that report. Simply go to the reporting server url http://servername/reports, find the Agents Missing hotfix report - click it - get the error. Then - click properties, and on the left - click Data Sources - on shared data source - browse to the correct "OpsDB" we just made here... and then click ok, then apply, then your report will work.

Sorry... I guess I had a different data source when I wrote that one. But this is a good learning opportunity on how to change a data source in a report! :-)

re: Creating a new data source for reporting against the Operational Database

Layne — Wed, 18 Feb 2009 03:52:06 GMT

Uh, this is embarrassing, I just figured out I had to edit the report data source in SRS and choose a shared data source 'OpsDB'. So that problem is solved. Now the report lets me put in a hotfix KB number, but when I run the report, I get an error "An error has occurred during report processing. Cannot create a connection to data source 'OperationsManager'." That is the name of my operational database.

re: still not working....

kevinhol — Wed, 18 Feb 2009 03:59:56 GMT

paste your connect string....

re: Creating a new data source for reporting against the Operational Database

Layne — Wed, 18 Feb 2009 04:04:09 GMT

data source=iolopsmgr01;initial catalog=OperationsManager;Integrated Security=SSPI

I also noticed that in the .rdl of the report, it says <DataSource Name="OperationsManager">. I tried changing the name of my datasource from OpsDB to OperationsManager and I get the same error.

re: Creating a new data source for reporting against the Operational Database

Layne — Wed, 18 Feb 2009 04:18:20 GMT

Looks like a permissions issue. When I change my datasource to use "Credentials supplied by the user running the report" and also click "use as Windows credentials when connecting to the data source", I can run the report.