Thanks Bruce for your response. I am starting to test with a user now and
that I would be putting the users in groups and assign permissions to the
group. My concern is that, whether the users needs to be on the local admin
group?. Am I missing anything?
No, definitely not. Do not put the user in the local admin group. I think
what you are missing is the process of adding to a role. Click on the home
directory, details, security (on the left panel). Then add a role and use
the new group that you have and give it browsing rights).

Signature
Bruce Loehle-Conger
MVP SQL Server Reporting Services
> Thanks Bruce for your response. I am starting to test with a user now and
> that I would be putting the users in groups and assign permissions to the
[quoted text clipped - 26 lines]
>> >
>> > Thanks!
Saravanan - 29 Jan 2007 22:16 GMT
Thanks for the patience to answer me Bruce.
Before adding into the local administrators group, I tried that option too.
I included the group onto the Browser Role on the Home of Reporting Services,
then created the folder and I selected assign specific rights to the folder
I uploaded the reports , went to the security tab of the folder and included
the group into the Browser Role. As it did not work, I included the group
into local admin.
Thanks!

Signature
Saravanan
> No, definitely not. Do not put the user in the local admin group. I think
> what you are missing is the process of adding to a role. Click on the home
[quoted text clipped - 31 lines]
> >> >
> >> > Thanks!
Bruce L-C [MVP] - 29 Jan 2007 22:40 GMT
When you assigned specific rights to the folder you overwrote the inherited
rights to Home. All the folders inherit from Home. First, try and get this
working without doing anything to the new folder.
Do this:
1. Add a user to a local group
2. Can they see Home (even if you don't have any folders)
3. Add a folder
4. Can they see this folder?
5. Add a report to the folder.
Again, don't touch any of the rights on the folder you should have to. The
only time to do this is if you want them in some folders and not others. In
that case you can give browsing rights to the folder and not to home and
then a link that brings them directly to the folder in question.

Signature
Bruce Loehle-Conger
MVP SQL Server Reporting Services
> Thanks for the patience to answer me Bruce.
>
[quoted text clipped - 53 lines]
>> >> >
>> >> > Thanks!
Saravanan - 30 Jan 2007 17:03 GMT
Hi Bruce,
Thanks for the step by step instructions. This is what I did
1. Created a Usergroup named ReportUsers
2. Included a Domain User into it (who does not have any access on the
machine)
3. I went to the Reporting services home and selected Properties > Security
and provided this group a role of Browser
4. I asked the user to go into the home page as
http://machinename/reports/Pages/Folder.aspx
5. The user is prompted with the a userid and password dialog box with the
machinename.domain.com in the dialog box above the userid text box.
Please let me know, if this makes sense.
Thanks for your support

Signature
Saravanan
> When you assigned specific rights to the folder you overwrote the inherited
> rights to Home. All the folders inherit from Home. First, try and get this
[quoted text clipped - 68 lines]
> >> >> >
> >> >> > Thanks!
Bruce L-C [MVP] - 30 Jan 2007 18:03 GMT
When prompted can they do this:
domainname\username put into the userid box and then their password?
I had this happen to me before and tore my hair out resolving it. For me the
issue was that the server did not have a fixed IP address, it was using
DHCP. Once I made it a fixed IP address then the problem went away.

Signature
Bruce Loehle-Conger
MVP SQL Server Reporting Services
> Hi Bruce,
> Thanks for the step by step instructions. This is what I did
[quoted text clipped - 102 lines]
>> >> >> >
>> >> >> > Thanks!
Saravanan - 30 Jan 2007 23:19 GMT
Hi Bruce,
Thanks for your ideas.
Even if they put their Domain userid and password it is not letting them in.
I checked the IP configuration and I can see that the IP has been assigned
static

Signature
Saravanan
> When prompted can they do this:
> domainname\username put into the userid box and then their password?
[quoted text clipped - 109 lines]
> >> >> >> >
> >> >> >> > Thanks!
Rowen - 30 Jan 2007 23:46 GMT
> > > 5. The user is prompted with the a userid and password dialog box with the
> > > machinename.domain.com in the dialog box above the userid text box.
This sounds to me like it is related to permissions required to access
the report manager website (permissions set in IIS) rather than
permissions to access the reports via report manager. You may need to
give the user/group permission to read the actual folder where the
report server website is installed (should be similar to 'C:\Program
Files\Microsoft SQL Server\MSSQL\Reporting Services\'). Check to
ensure the user has these privileges.
Rowen
Bruce L-C [MVP] - 31 Jan 2007 14:45 GMT
Unless IIS permissions have been changed from outside of RS there is never a
need to do anything with IIS permissions. However, if anyone has been
changing permissions with IIS then there could be a problem with a mismatch
between the two.

Signature
Bruce Loehle-Conger
MVP SQL Server Reporting Services
>> > > 5. The user is prompted with the a userid and password dialog box
>> > > with the
[quoted text clipped - 9 lines]
>
> Rowen
Saravanan - 31 Jan 2007 18:32 GMT
Thanks Rowen and Bruce. No body changed the permissions on the server, but
when I followed Rowen's idea it worked. Now the users are able see the report
without Admin priveliges on the report server machine.
Again! Thanks a lot

Signature
Saravanan
> Unless IIS permissions have been changed from outside of RS there is never a
> need to do anything with IIS permissions. However, if anyone has been
[quoted text clipped - 14 lines]
> >
> > Rowen
Rowen - 31 Jan 2007 23:06 GMT
On Feb 1, 5:32 am, Saravanan <Sarava...@discussions.microsoft.com>
wrote:
> Thanks Rowen and Bruce. No body changed the permissions on the server, but
> when I followed Rowen's idea it worked. Now the users are able see the report
[quoted text clipped - 26 lines]
>
> > > Rowen
Glad to hear this solved the problem. It may have been there since
reporting services was installed (particularly when using reporting
services 2003, which often requires manual configuration after
installation).
Rowen