• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1075
  • Last Modified:

ASP.NET - VS2005 (VB) - Report Viewer Control - Http status 401: Access Denied

Hello Experts,

I'm using the Report Viewer Control on an ASP.NET web page.  The report runs fine on my machine in VS2005.  I published it, and it runs fine on the server.  However, when I try to run it on a client machine from the server (ex: Http://servername/project.aspx) I get the following error message:

The request failed with HTTP status 401: Access Denied.

Stack Trace: at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.GetSecureMethods() at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.IsSecureMethod(String methodname) at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID) at Microsoft.Reporting.WebForms.ServerReport.GetExecutionInfo() at Microsoft.Reporting.WebForms.ServerReport.SetParameters(IEnumerable`1 parameters) at Agent_Incentive.Display_Report(Label lblAgent, DateTime strDate)

I'd really appreciate if someone could help me with this, I'd appreciate it.  My deadline is about to steam-roller me...

Thanks,
GRCHELPDESK
0
GRCHELPDESK
Asked:
GRCHELPDESK
  • 2
1 Solution
 
brwwigginsCommented:
The account your ASP.NET application runs under on the IIS server does not have permission to the report.
0
 
GRCHELPDESKAuthor Commented:
Hello brwwiggins,

I currently have anonomys access disabled, and I'm using windows authentication.  I need to do this because the page pulls the logon ID of the user and passes that parameter to the report.  (to show stats for only them)

Since I'm running the report, it's pulling my windows ID, and I have an ID built in SQL Services & the reporting side.  Sorry, I should have mentioned that in the post... I've been up for 26 hrs now my brain is mush.

Thanks!
GRCHELPDESK
0
 
GRCHELPDESKAuthor Commented:
Hey Everyone,

I've finally got this working.  I was running into the double-hop issue.  The problem is that the webpage resided on one server, and the report on a different server.  So when you viewed it on a client machine, it would pass the credentials along to server hosting the web page.  The web page would run and call the report from the server hosting the report... but apprently the credentials can't make that "double hop" to 2nd server.  So since they're not being sent, you get "Access Denied".  So when I setup the webpage on the same server as the report, it just worked.

One final note.  I then got a new error message "rsAccess Denied".  This is an error message from the Reporting Services.  Reporting Services knew exactly who was logging in, it was just denying them access to view the report.  

So we checked the settings in Report Manager and found the problem.  We needed to assign "Execute Report Definition" to a system role, and then add the user group to that role.  Then once we added that user group to folder associated with the report, it worked fine.

I hope this helps anyone else running into this issue.

Cheers,
GRCHELPDESK
0
 
Computer101Commented:
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now