Some MP Reports Are Not Deployed to the Reporting Services Server

mgoedtel — Wed, 19 Dec 2007 19:45:00 GMT

Shortly after implementing Operations Manager 2007 and upgrading to RC Service Pack 1 in my customer's lab environment, I noticed the following errors in the Operations Manager Event Log on the RMS stating:

Failed to deploy reporting component to the SQL Server Reporting Services server. The operation will be retried. Exception 'UnauthorizedAccessMonitoringException': The user Domain\mgmtDR does not have sufficient permission to perform the operation. One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Report Instance name: SERVERNAME.Domain.com Instance ID: {BFA9FF77-3A74-02CE-B7ED-1E0835652EBE} Management group: MgmtGroup-01

The Event was generated from the SDK Service and the Event ID was 26319. When I was attempting to run some of the Active Directory and Windows Server Base OS Reports, the Root Container for the reports were listed, but not the individual reports themselves. Of course I did verify that we granted the Data Reader account the required rights, and obviously it did since the reports from other Management Packs were available in the Reports view. After doing some troubleshooting and not making any relevant progress, I raised a flag with the Product Group and they suggested adding the Data Reader account to the MOMAdmins Group (which basically gives it "GOD" rights in Operations Manager). After adding it to the Global Group and not the Operations Manager Administrators User Role directly, I recycled all the services on the RMS. Shortly thereafter the reports were successfully deployed to the Reporting Services server. I then removed the Data Reader account from the Global Group and recycled the services again on the RMS to restore the security settings back to the recommended configuration.

Some other colleagues and customers have experienced this with other Management Pack reports, such as the newly released DNS MP. Right now if you are working with RC Service Pack 1 and you encounter this issue, utilize this workaround until otherwise informed.

The Product Group is researching this to identify what the cause of the insufficient security permissions for the Data Reader account. Especially since we want to make sure that Service Pack 1 is solid when released early next year.

Installing ACS Reports

mgoedtel — Tue, 10 Jul 2007 15:26:00 GMT

I figured I would write a quick post regarding the ACS component in Operations Manager 2007, as I sometimes see people wonder why the reports are not available after they install the ACS Database and Collector component. The setup of the ACS Collector does not install the ACS Reports and it is not even an option. In order to instal the Reports on your SQL Server 2005 Reporting Services/Operations Manager Reporting Server, perform the following steps:

From the source installation media, go to the ReportModels\ACS folder.
Launch the script - UploadAuditReports.cmd with the following parameters:

UploadAuditReports {DatabaseServerAndInstance} {ReportingServiceURL} {ReportFolder}

Note: ReportFolder is the path to "<Installation Media>\ReportModels\ACS"

Example: UploadAuditReports DBServer\Instance1 http://DbServer/ReportServer$Instance1 D:\ReportModels\ACS

Now when you go into the Operations Console, Reports link you should see the pre-canned ACS Reports available for use.

Matt Goedtel on Operations Management : Reports

Some MP Reports Are Not Deployed to the Reporting Services Server

Installing ACS Reports