SQL Server 2005 Reporting Svces Set Up

[dhulbert]

I'm having a problem with a SQL Server 2005 Reporting Svces Set Up.

When I access the reporting services home page I see eveyting correctly and I can publish etc, but when other users access the pages they only see the top part of the home page (down to the Blue and Yellow Lines) but nothing below that.

I know it's a prmissions issue somewhere as if I make a user a local admin it works fine but otherwise not.

Any ideas would be appreciated.

Thanks.



I love deadlines. I like the whooshing sound they make as they fly by
Douglas Adams
(1952-2001)

 

[SgtJarrow]

Every object in your Reporting Services has a security link. If you have Admin rights on the Reports page, click the Show Details button on the top right of the page. Then click edit for any item (folder, report, data source) and add the users to the security, giving them the appropriate security.

Also, when you are at the Home page and change to Show Details, you should see a Permissions tab...you will need to add the users here as well.

Depending on your scenario, just adding them to the Home may be enough. This is because all objects inherit from its parent. So all folders on the Home page automatically get the same security as the Home page and so on.

I personally set all the permissions at the Home page level. Then anywhere I have a report I do not want specific users to have access to, such as Accounting reports, I go to the security for that folder and break the inheritance. I can then add specific users/groups at that folder's root and all the reports in that folder can only be accessed by certain individuals.

Hope this helps. Let me know if not.

=======================================
People think it must be fun to be a super genius, but they don't realize how hard it is to put up with all the idiots in the world. (Calvin from Calvin And Hobbs)

Robert L. Johnson III
CCNA, CCDA, MCSA, CNA, Net+, A+, CHDP
VB/Access Programmer

 

[dhulbert]

My user id is set up with an administrator role on reporting services and it still will not work unless I also have admin privialges on the box, I'm sure the problem must lie in either the IIS setup of the SQL server, any more ideas.

Cheers.

I love deadlines. I like the whooshing sound they make as they fly by
Douglas Adams
(1952-2001)

 

[SgtJarrow]

Your last response says that your ID is set up with Admin role on the SQL Reporting Security pages. BUT what about your users? Your original post stated that your USERS only see the little bar at the top of the page...but none of the folders or reports. Which one is the problem...your ID or your users trying to access the pages?

My experience has led me almost always to this being related to the USER not having a valid role (Browser usually for me) in the SQL Reporting Security pages.

=======================================
People think it must be fun to be a super genius, but they don't realize how hard it is to put up with all the idiots in the world. (Calvin from Calvin And Hobbs)

Robert L. Johnson III
CCNA, CCDA, MCSA, CNA, Net+, A+, CHDP
VB/Access Programmer

 

[dhulbert]

In my origianl post I stated that my ID works fine but that my users only work if they are given local admin rights on the box.

Your reply suggested that I needed to give the users permissions on reporting services.

My second reply was to show you that although my user ID had admin privs on Reporting services that without admin provs on the box that id doesn't work either.

So to state the original question again

ANY user id that does not have admin provialges on the server CANNOT use reporting services even if they have admin privialges within reporting services.

I'm therefore pretty sure the issues is NOT with the reporting services id's but it lies in the setup of eirhter the databases on SQL server or IIS,

Any more ideas before i have to go for a full reinstall.

I love deadlines. I like the whooshing sound they make as they fly by
Douglas Adams
(1952-2001)

 

[SgtJarrow]

My only other thought then does lead towards SQL server. The users still need at least db_datareader access to the databases they are trying to see data from. You can manage this in a couple ways. You can explicitly give each person access, give a group access to which the users belong, or - as my company does - create a "service account" (a user in active directory whose password expires only after a long period or not at all, which is an exception to our company policy) and give this account access. Then in all the datasources on your Reporting Services you go to the Properties -> General section and make the datasource use this account as its credentials for anyone who accesses the report.

One other thing as well...related to my previous posts, check that the users, groups etc have access to the Home page of Reporting Services. This is on the Properties tab of the Home page. I forgot that for a while the first time I setup this up.

Outside of that, I don't have anything else I can think of.

=======================================
People think it must be fun to be a super genius, but they don't realize how hard it is to put up with all the idiots in the world. (Calvin from Calvin And Hobbs)

Robert L. Johnson III
CCNA, CCDA, MCSA, CNA, Net+, A+, CHDP
VB/Access Programmer