May 23, 2016 at 10:20 am
In SSRS, we have a few folders and associated reports that I can see in the "Catalog" table of the ReportServerDb. However, when looking for the folder and reports in Report Manager they are not there.
I thought it could be a security issue, but I believe I'm logged into the Report Manager as the same user which is the database owner. I also ran the below query and it shows that the user name has the following roles assigned: Browser, Publisher, My Reports, Content Builder, and Report Builder.
Any ideas?
SELECT C.Name
,U.UserName
,R.RoleName
,R.Description
,U.AuthType
FROM Reportserver.dbo.Users U
JOIN Reportserver.dbo.PolicyUserRole PUR
ON U.UserID = PUR.UserID
JOIN Reportserver.dbo.Policies P
ON P.PolicyID = PUR.PolicyID
JOIN Reportserver.dbo.Roles R
ON R.RoleID = PUR.RoleID
JOIN Reportserver.dbo.Catalog c
ON C.PolicyID = P.PolicyID
WHERE c.Name = @ReportName
ORDER BY U.UserName
May 23, 2016 at 11:27 am
add the column ReportServer.dbo.Catalog.Hidden to your query.
when a folder or report is marked as "hidden", you have to change the view in SSRS to "Details View" to see those hidden reports.
it's a functionality to hide little used reports to provide a more relevant dashboard kind of activity; semi-archiving little used reports, for example.
each folder or report has a checkbox that says "hide in tile view" if you go to Manage>>Prooperties
Lowell
May 28, 2016 at 8:40 am
It in fact turned out to be a security issue. I gave access to the site and the top folder, but apparently that doesn't apply to every folder. So I had to go to each folder and add the user separately.
May 28, 2016 at 8:46 am
ptownbro (5/28/2016)
It in fact turned out to be a security issue. I gave access to the site and the top folder, but apparently that doesn't apply to every folder. So I had to go to each folder and add the user separately.
you could have done the reverse, too.
go to the sub folder, and remove the current rights, and tell it to inherit from parent instead.
it depends on whether specific sub folders needed separate security, or someone accidentally assigned at a detail level instead of allowing inheriting from the top.
Lowell
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply