Viewing Reports over the internet -- sql server reporting services

StvPl
11/25/2004 8:47:04 AM

This is a continuation of a previous question I asked, I've made progress but
still not quite there!

To simplify testing and remove as many variables as possible I have prepared
a very simple report based on the Northwind database and deployed it to a
Windows 2003 server.

If I access //servername/reportserver I can veiw and run the report. However
if I try to access http://www.domain.co.uk/reportserver I can see the report
listing directory and run it but it always hangs on the 'Report is being
generated' screen.

The final goal is to have a C# developed asp.net application producing
reports over the intranet and when necessary the internet but this is showing
the same symptoms. I'm presuming there must be a permissions issue somewhere
and once solved on the simple northwind report the asp one should follow suit.

We have installed Reporting Services evaluation edition along with RS
Service pack 1 on a Windows 2003 server - per cpu licensing and no ssl
security was selected. Sql server standard edition is installed on the same
server.

The report's data component connection has been set to use a user with
enough permissions on the database (briefly tried sa, again with the same
result).

So far I have:-
Tried every combination of <ReportServerUrl>, <ReportServerExternalUrl> and
<ReportServerVirtualDirectory> settling on the latter.

Tried many folder permissions on the physical ReportServer directory.

Also, although we are behind a hardware firewall the server was briefly set
as a DMZ with no success.

Thanks in advance

Mike Hanson
11/25/2004 10:45:02 AM

Have you checked the <UrlRoot> element in RSReportServer.config.

I had a similar problem, despite setting the url values in
RSWebApplication.config I noticed that once a report had been requested and
got to the generating report message, subsequent requests were being directed
to the machine name rather than the FQ domain name I had configured. I
figured this must be something to do with the ReportServer configuration, as
it had generated the report viewing frameset now hosted in ReportManager.
That was when I found the entry mentioned above, changed it to a FQ the FQ
domain name and bingo reports were displayed properly.

Hope this helps
Mike Hanson

[quoted text, click to view]

Wayne Gadberry
12/6/2004 4:48:33 PM

i finally got my platform to work a few minutes ago. in the
<ReportServerExternalUrl> XML attribute, i had to include "http://" and add
an additional "/" at the end of the attribute as follows:

<ReportServerExternalUrl>http://xxxx.domainname.com/ReportServer/</ReportServerExternalUrl>

Wayne

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server reporting services

sql server reporting services : Viewing Reports over the internet