If I term serv to the web server in question and browse to the standalone
Report Manager (http://localhost/reports), it works. IE automatically
authenticates with IIS on the web server because "Automatic logon only in
Intranet zone" is set in IE and localhost is in the Intranet zone. Now when I
turn off "Automatic logon only in Intranet zone" and have it prompt me,
Report Manager's call to the SQL Server Reporting Service Web Service fail
with a 401 error. How strange is that?!?
Figuring it has something to do with automatic logon, I went to another
machine, turned on automatic logon in IE and hit the standalone Report
Manager on the web server. It automatically logged on, but when Report
Manager called the Reporting Services web service on the SQL Server, that
call failed with a 401 error.
I also created a simple custom web app that resides on the web server and
calls one web service method in the reporting server web service. It behaves
the exact same way as Report Manager (blowing up with a 401 error under all
the same situations), so I don't think it's anything intrinsically wrong with
Report Manager and how it calls the web service.
My custom web service used:
myProxy.Credentials= System.Net.CredentialCache.DefaultCredentials
I'm sure that's how Report Manager does it, too.
Anyone have any thoughts?
[quoted text, click to view] "FurmanGG" wrote:
> I followed the instructions for installing Report Manager and NOTHING else on
> a separate web server. The instructions came from:
>
>
http://groups-beta.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/9750be7e6c083a7b/6b15e50db9740949#6b15e50db9740949
>
> I'm pretty darn close and was wondering if Daniel Rieb (or anyone) can get
> me the rest of the way.
>
> The Report Manager web (and nothing else) is now on our web server. I've
> turned off anonymous access. When I browse to the new Report Manager website,
> I get the following error housed in the Report Manager look-and-feel:
>
> The request failed with HTTP status 401: Access Denied.
>
> I checked the IIS log for the Reporting Services server and it did hit the
> /ReportServer/reportservice.asmx web service under anonymous authentication
> and returned a 401 status. (That's because the ReportServer web service
> doesn't allow anonymous connections. If I temporarily turned on anonymous
> access, the Report Manager on our web server successfully takes you to a
> Report Manager home page with no items because of lack of role based security
> in Reporting Services for SQLServerName\IUSR_SQLServerName.) So I suspected
> that the security credentials from my web server logon weren't being passed
> through and that's why it was failing. I checked the web.config file in the
> ReportManager directory on our web server and found:
>
> <authentication mode="Windows"/>
> <identity impersonate="true"/>
>
> That's correct, I believe. Were there any other web.config settings I should
> check for the Report Manager web?
>
> If I just wanted to be able to view a few reports, it wouldn't matter that
> the standalone Report Manager always showed the personalization (My Reports,
> etc.) for SQLServerName\IUSR_SQLServerName. But that won't meet my needs
> because everyone needs their own personal "My Reports" section depending upon
> their login to the standalone Report Manager web.
>
> The issue, as I see it, is figuring out how to get IIS and the remote Report
> Manager web to pass through the Windows login of the user. Any help you can
> give would be MUCH appreciated.
>
> A separate question concerns licensing. I assume if all I have on the web
> server is a copy of the ReportManager web (no ReportServer, no SQL Server, no
> Reporting Services Service), that the web server would not need a SQL Server
