AD groups cannot see/run reports

  • setup

    domain: myDomain

    domain group: myDomainGroup

    domain user: myUser

    myUser is a member of myDomainGroup

    In Reporting Services, I created a report an put it in the home folder. In the Security properties for the Home folder, myDomain\myUser is in the Browse role. In the Security properties for the report, myDomain\myUser is also in the Browse role. This works just fine, and the user can go to the reporting services site and execute the report.

    But this does NOT work (and I don't understand why):

    remove myDomain\myUser from the Report's Browse security role and also remove the same user from the Home's Browse security role. Then, go to Home's security properties and add myDomain\myDomainGroup to the Browse security role and then add myDomain\myDomainGroup to the report's Browse security role. No when the user navigates to the reporting services url, there's nothing there, just the links "Home", "My Subscriptions" and "Help".

    Can someone explain to me why that is?

  • Seems like what you are doing should work. Try this though as a troubleshooting aid.

    Remove the explicit permissions on the report and just have it inherit from it's parent (aka Home or whatever folder it's in) there's a button at the stop of the security settings page that says revert to parent security.

    If that doesn't work...

    Make certain that the report's parent has the appropriate permissions. I.E yourdomain\yourgroup in the home folder's browse group. It seems that it already is since you are getting to that page although it is currently blank, which is why I think the above will work.

    Make sure you are not deploying the report to a location other than home, i.e. home/reports or that if you are that the group has the appropriate rights for that folder.

    -Luke.

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • On 'Properties' 'General Settings' ensure you have not got option 'Hide in list view' selected.

    Regards,

    Phil.

    -------------------------------------------------------------------------------------
    A neutron walks into a bar. "I'd like a beer" he says. The bartender promptly serves up a beer. "How much will that be?" asks the neutron. "For you?" replies the bartender, "no charge."

    Two hydrogen atoms walk into a bar. One says, 'I think I've lost an electron.' The other says 'Are you sure?' The first says, 'Yes, I'm positive... '

    Tommy Cooper

  • I had ca similar problem. The problem may lie in the type of AD group that you're using. I believe ( this problem was a while ago), that if I used distribution groups then I ran into problems, changing to a security group fixed things. I may have things mixed up, AD is by no means a speciality of mine.

  • Hi - I've got exactly the same issue on my SSRS 2005. I've looked at the AD group type (Security vs Distribution) and this makes no difference.

    I've found that by adding the AD group to the builtin\users group and then just giving the builtin\users group the relevant permissions on the report works, but this is not really an acceptable solution, especially as I have different permissions requirements for different reports/AD groups.

    Does anyone have any other suggestions?

    Thanks in advance,

    Daryl.

  • 2Tall (5/31/2010)


    On 'Properties' 'General Settings' ensure you have not got option 'Hide in list view' selected.

    Regards,

    Phil.

    Nope, not checked.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply