The request failed with HTTP status 401: Unauthorized

  • Hi,

    Server Error in '/xyz.aspx' Application.

    --------------------------------------------------------------------------------

    The request failed with HTTP status 401: Unauthorized.

    Exception Details: System.Net.WebException: The request failed with HTTP status 401: Unauthorized.

    Line 124: parameters.Add(new Microsoft.Reporting.WebForms.ReportParameter("utype", UserType.ToString()));

    Line 125: Response.Write(parameters.Count);

    Line 126: ReportViewer1.ServerReport.SetParameters(parameters);

    Line 127: Response.Write("test" + parameters.Count);

    Line 128: ReportViewer1.ProcessingMode = ProcessingMode.Remote;

    Above error is triggering while generating from Web server.

    web server with IIS 6.0 and ASP.net frame 2.0

    Database on other server.

    Reports on other Server.

    Application is working fine

    I can access reports from application with out deploying on IIS Server

    After deploying on IIS when i am accessing Reports from application getting above error .

    I can access reports

    via Reportmanager/Report server.

    but through application that to after deploying on IIS this problem persists.

    In Report Manager access was given to following users

    BUILTIN\Administrators Content Manager

    BUILTIN\Users Content Manager

    NT AUTHORITY\ANONYMOUS LOGON Content Manager

    NT AUTHORITY\NETWORK SERVICE Content Manager

    Domain\Administrator Content Manager

    Domain\ASPNET Content Manager

    Domain\USER(SSRS Serivce) Content Manager

    Domain\Reprotserver$(system) Content Manager

    Domain\WEBSERVER$(system) Content Manager

    On web server

    IIS

    enable anonymous User ticked

    systemname\IUSR_systemname.

    Please do the needful to overcome the above issue...

    Awaiting for your valuable replies...

  • How did you resolve this issue? I'm having a similar problem. Was able to access reports fine until we added a certificate and started to use SSL etc. How it is failing the request with status 401.

  • I found a fix for our issue in disabling loopback checking via modification of the registry.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply