Answered by:
Missing permission on DPM Report
Question
-
I just reinstalled a DPM server and restored the database. Everything seems to be working, except when I try to viewer the "Tage Management" report.
An error has occurred during report processing. (rsProcessingAborted) Query execution failed for dataset 'DataSet1'. (rsErrorExecutingCommand) The EXECUTE permission was denied on the object 'ufn_MM_GetPgLabels', database 'DPMDB_DKODPM01', schema 'dbo'.
If I view the "Recovery Point Status" report it Works fine.
I can't figure out what user/Group is missing permissions on SSRS or the database?
Answers
-
I solved it by adding the local "DPMR$Servername" account to the local security Group "DPMDBAdministrators$Servername".
When looking in http://servername/Reports_DPM , under the DPMReports_randomnumbershere, there is the DPMReportDataSource that shows the account used for DPM reports.
- Marked as answer by mbe-dk Monday, February 18, 2013 12:43 PM
All replies
-
Hi,
I have never heard or seen that before - lucky you.
Did you run DPMSYNC -Sync after you restored the DPMDB ?
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
-
-
I solved it by adding the local "DPMR$Servername" account to the local security Group "DPMDBAdministrators$Servername".
When looking in http://servername/Reports_DPM , under the DPMReports_randomnumbershere, there is the DPMReportDataSource that shows the account used for DPM reports.
- Marked as answer by mbe-dk Monday, February 18, 2013 12:43 PM
-
Hi,
in SQL Server Management Console set db_owner rights on DPMDB for DPMDBReaders$...
Cheers Matthias
- Proposed as answer by Matthias Schmitz Thursday, November 7, 2013 1:56 PM
-
-
-
Matthias's solution worked for me - cheer Matthias.
Our scenario was an in-place upgrade of DPM2012 to DPM2016, followed by an in-place upgrade of SQL2012 SP3 to SQL2014. Unfortunately I didn't try reporting before I upgraded SQL, so I couldn't tell at what point this issue may have arisen. Also needed to copy over the reporting .dll's from the old SQL server instance (a known issue when upgrading DPM SQL), and then arrived here with only the Tape Management report giving this permission error.
Seems odd, especially as it didn't need to be db_owner on the previous installation? I did try all of the other SQL permissions to see if anything else worked but only db_owner did the trick.
If anyone has a less brute force solution to this I'd be very interested. :)
Ben.
-