401 Error with ReportViewer

I'll try to best explain the issue I'm having and the setup I'm working with.
ISSUE - I'm getting a 401 Unauthorized error when trying to view a report
within a web page using the reportviewer control, even if I "Hardcode" the
username, Password, and domain for the credentials.
Setup - we have IIS 6.0 box that the asp.net 2.0 application is on with
basic authentication. The reporting services server uses Basic
authentication as well. The RS server and the IIS box are in our
DMZ(internet), and the user account exists for both the IIS server and RS
server, and using that username and password I can go in to the report in RS
and view it fine.
I am able, with the app to connect to another RS server in the same DMZ.
What can I have or ask the network admins to check to see what's wrong?
--
Mike Voissem
Lead Software Engineer
Donnelley MarketingOn Apr 21, 5:58 am, Mike Voissem
<MikeVois...@.discussions.microsoft.com> wrote:
> I'll try to best explain the issue I'm having and the setup I'm working with.
> ISSUE - I'm getting a 401 Unauthorized error when trying to view a report
> within a web page using the reportviewer control, even if I "Hardcode" the
> username, Password, and domain for the credentials.
> Setup - we have IIS 6.0 box that the asp.net 2.0 application is on with
> basic authentication. The reporting services server uses Basic
> authentication as well. The RS server and the IIS box are in our
> DMZ(internet), and the user account exists for both the IIS server and RS
> server, and using that username and password I can go in to the report in RS
> and view it fine.
> I am able, with the app to connect to another RS server in the same DMZ.
> What can I have or ask the network admins to check to see what's wrong?
> --
> Mike Voissem
> Lead Software Engineer
> Donnelley Marketing
I am having a similar issue - I'm using the Reporting Service and
Report Execution Service to dynamically render a report into a
ReportViewer control. Both web services are using the default
credentials. The Reporting Service is (and always has been) working
fine with these credentials - I can retrieve report parameters,
validate them, and so forth. The Report Execution Service however is
what is causing the 401. The Report Execution Service is required when
I set the properties of the ReportViewer control, so that I can assign
the ReportViewer an ExecutionId (why this is required I don't know -
I've used the ReportViewer control to display reports which were
determined at design time and that was fine?) but when I go to load
the report it gives the 401. Thing is, it was working in my local
environment (ASP.NET virtual server and a local Report Server
instance)... could anyone shed some light on this situation?
Cheers,
- Tokes|||On Apr 21, 9:31 am, Tokes <michael.to...@.gmail.com> wrote:
> On Apr 21, 5:58 am, Mike Voissem
>
> <MikeVois...@.discussions.microsoft.com> wrote:
> > I'll try to best explain the issue I'm having and the setup I'm working with.
> > ISSUE - I'm getting a 401 Unauthorized error when trying to view a report
> > within a web page using the reportviewer control, even if I "Hardcode" the
> > username, Password, and domain for the credentials.
> > Setup - we have IIS 6.0 box that the asp.net 2.0 application is on with
> > basic authentication. The reporting services server uses Basic
> > authentication as well. The RS server and the IIS box are in our
> > DMZ(internet), and the user account exists for both the IIS server and RS
> > server, and using that username and password I can go in to the report in RS
> > and view it fine.
> > I am able, with the app to connect to another RS server in the same DMZ.
> > What can I have or ask the network admins to check to see what's wrong?
> > --
> > Mike Voissem
> > Lead Software Engineer
> > Donnelley Marketing
> I am having a similar issue - I'm using the Reporting Service and
> Report Execution Service to dynamically render a report into a
> ReportViewer control. Both web services are using the default
> credentials. The Reporting Service is (and always has been) working
> fine with these credentials - I can retrieve report parameters,
> validate them, and so forth. The Report Execution Service however is
> what is causing the 401. The Report Execution Service is required when
> I set the properties of the ReportViewer control, so that I can assign
> the ReportViewer an ExecutionId (why this is required I don't know -
> I've used the ReportViewer control to display reports which were
> determined at design time and that was fine?) but when I go to load
> the report it gives the 401. Thing is, it was working in my local
> environment (ASP.NET virtual server and a local Report Server
> instance)... could anyone shed some light on this situation?
> Cheers,
> -Tokes
Update:
I reverted back to code that did not use the Report Execution Service,
and this now works in my local environment as well as my servers...
very strange behaviour! I also learned that I was using the 2000
Reporting Service web service instead of the 2005 one, which clarified
a couple of things for me (because I didn't understand why the Report
Execution Service did some things that the Reporting Service did too).|||Hi,
Please find my message according to this issue by clicking here:
news:9CD3F523-6D16-40D0-8F97-B9183E28C7D6@.microsoft.com
Regards,
Janos
"Mike Voissem" <MikeVoissem@.discussions.microsoft.com> wrote in message
news:D6CB015C-EEA4-4FBE-8653-4A3D7A34550B@.microsoft.com...
> I'll try to best explain the issue I'm having and the setup I'm working
> with.
> ISSUE - I'm getting a 401 Unauthorized error when trying to view a report
> within a web page using the reportviewer control, even if I "Hardcode" the
> username, Password, and domain for the credentials.
> Setup - we have IIS 6.0 box that the asp.net 2.0 application is on with
> basic authentication. The reporting services server uses Basic
> authentication as well. The RS server and the IIS box are in our
> DMZ(internet), and the user account exists for both the IIS server and RS
> server, and using that username and password I can go in to the report in
> RS
> and view it fine.
> I am able, with the app to connect to another RS server in the same DMZ.
> What can I have or ask the network admins to check to see what's wrong?
> --
> Mike Voissem
> Lead Software Engineer
> Donnelley Marketing