double authentication to get to a report? 2nd auth fails?

I recently implemented Reporting Services (w/ SP1) on a 2003 Server w/ SQL
Srvr 2000(SP3). On the server is a group of ID's from my company's domain.
This group is given the Browser role which works to a point of navigating
folders.
When the user chooses a report they are re-authenticated and the
authentication fails. In looking at the URL I notice everything is fine with
https://{server}/Reports/Pages/Folder.aspx but when you click on a report
https://{server}/Reports/Pages/Report.aspx is called and the authentication
pops up and declines the user (even though it's a valid login using
domain\user).
Other issues:
I received an error during set up which I found the work around for in an
MSDN KB. The reason why I mention it is that is has you create the virutal
directories manually after the fact so perhaps a permissions was missed?I have also started to have this problem. Although it is only on a large
dataset. Smaller reports seem to work fine.
Please post a solution if you get one.
-- Jesse
"Peter Capazzi" <PeterCapazzi@.discussions.microsoft.com> wrote in message
news:EC3D5EA2-DFD8-4554-89A1-EEC4B2BC3A2D@.microsoft.com...
>I recently implemented Reporting Services (w/ SP1) on a 2003 Server w/ SQL
> Srvr 2000(SP3). On the server is a group of ID's from my company's domain.
> This group is given the Browser role which works to a point of navigating
> folders.
> When the user chooses a report they are re-authenticated and the
> authentication fails. In looking at the URL I notice everything is fine
> with
> https://{server}/Reports/Pages/Folder.aspx but when you click on a report
> https://{server}/Reports/Pages/Report.aspx is called and the
> authentication
> pops up and declines the user (even though it's a valid login using
> domain\user).
> Other issues:
> I received an error during set up which I found the work around for in an
> MSDN KB. The reason why I mention it is that is has you create the virutal
> directories manually after the fact so perhaps a permissions was missed?|||I continued to work on this and found a solution... I gave the group
permission to ReportServer by right clicking in IIS Mgr and using permissions
there.
** I gave Read, Execute, and List Folders permissions. Is that too much? **
Jesse:
I would think if one user ID can access one report then that means all of
the permissions are set up to generate a report. I would look in the security
tab under properties and ensure the role that's attached to the group (or
user id) is there.
Also, do the reports use embedded ID's for pulling queries? Check that the
user ID in the Data Source has the proper permissions to the table... just
log into SQL Anlalyzer with the ID and execute the query there.
That's my 2 cents...
"Jesse Beveridge" wrote:
> I have also started to have this problem. Although it is only on a large
> dataset. Smaller reports seem to work fine.
> Please post a solution if you get one.
> -- Jesse
> "Peter Capazzi" <PeterCapazzi@.discussions.microsoft.com> wrote in message
> news:EC3D5EA2-DFD8-4554-89A1-EEC4B2BC3A2D@.microsoft.com...
> >I recently implemented Reporting Services (w/ SP1) on a 2003 Server w/ SQL
> > Srvr 2000(SP3). On the server is a group of ID's from my company's domain.
> > This group is given the Browser role which works to a point of navigating
> > folders.
> >
> > When the user chooses a report they are re-authenticated and the
> > authentication fails. In looking at the URL I notice everything is fine
> > with
> > https://{server}/Reports/Pages/Folder.aspx but when you click on a report
> > https://{server}/Reports/Pages/Report.aspx is called and the
> > authentication
> > pops up and declines the user (even though it's a valid login using
> > domain\user).
> >
> > Other issues:
> > I received an error during set up which I found the work around for in an
> > MSDN KB. The reason why I mention it is that is has you create the virutal
> > directories manually after the fact so perhaps a permissions was missed?
>
>