MBAM rrRenderingError Error: Subreport could not be shown

Question

hi,
i create a two server setup , database/report and application for MBAM application
i secure with ssl and all work
mbam client are installed and client send data to database:
compliance report with computer detail , volume and key

I access to my "Microsoft BitLocker Management and Administration" web page , select Reports
Then under enterprise compliance report i se my pc
then i click one pc and i have the computer details

the problem come when i clic on + near pc to see the volume information, and i receive this error
Error: Subreport could not be shown.

i try to access direct to database address and i receive this
Reporting Services Error
For more information about this error navigate to the report server on the local server machine, or enable remote errors
SQL Server Reporting Services

so i log directly under server and try to download a csv format

Reporting Services Error
Error: Subreport could not be shown.(rrRenderingError)
Error: Subreport could not be shown..
SQL Server Reporting Services

i check database
tables and i see that the records of the volumes are there

i really not understand what is the problem. Maybe i miss some feature to install or some prerequisite for SSRS?

Answer 1

hi,
i check database and the data are correctly filled in view

then i check storage procedure and function and seems permission are right to execute

then i try to connect to SSRS and ask for volume report and i have this

i check the permission and not understand why i havn't permission to execute. Or is the application web user that must have the permission? that user have already write permission

where is the trouble?

Answer 2

Hi @The All ,

Error while processing the report. (RsProcessingAborted)
Unable to query for dataset 'VolumeDataSet'. (RsErrorExecutingCommand)
The EXECUTE permission was denied on the object 'GetComplianceStatusForVolume', database '' MBAM Complicance Status;, schema 'ComplianceCore'

First, did you try what was suggested in the error:
navigate to the report server on the local server machine

Have you checked "db_datareader", "db_datawriter" and "public" for database roles in database 'VolumeDataSet'.
In the database section of the Object Explorer (Databases > VolumeDataSet > Security > Users), see if the Active Directory group is listed, and in the properties for this under "Membership" both 'db_datareader' and 'db_datawriter' are ticked. please make sure AGs set for datasource and dataset are properly checked.

The following threads are for your reference:
Query Execution Failed for Dataset - permissions
Find Deny permissions on database objects.
Best Regards,
Joy

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

VolumeDataSet is a collection of data not a database

those are databases

and the function is on database "MBAM Compliance Status"

check permission and are ok

Answer 4

hi,

nothing still have same error

not understand what is the problem , maybe "Volume Report.rdl" to rdlc?

Answer 5

hi,

after many troubles i figured out the problem
This is an error on MBAM 2.5 sp1 2.5.1100 with upgrade october 2.5.1152
when you deploy the mbam report from configuration wizard it create many sql user without login like
complianceCore
complianceRead
complianceWrite

but the wizard miss some permission.

The subreport is need to executed by complianceRead.
And this user have no execute permission on this function "GetComplianceStatusForVolume"

Maybe there are better solution but i give only this permission in a easy way

• Create a db_executor role
  CREATE ROLE db_executor
• Grant execute rights to the new role
  GRANT EXECUTE TO db_executor
• grant execute to the function(permission security)
  
• add role to the user "complianceRead"
  

And now i see the report as expected

Hope this helps someone else , without lose hours for an setup error. i hope they fix next upgrade.

Cya