sql server reporting services: We have a confusing problem and need some guidance.

We are trying to use URL access to generate and display a report. We =
have tried two ways--building the URL string and popping up a new =
browser with the Reporting Services URL access string and simply using =
an anchor tag and setting its URL parameter to the Reporting Services =
URL access string. Both options don't work--well, one works for the =
local server and the other works for client computers (not the server), =
but neither work for both.

Basically, we're having trouble using localhost vs. servername in our =
URL access string.

The examples below use localhost.
These work fine from the server which Reporting Services and IIS are =
running, but not from other computers (because of the "localhost").
// Build the URL for the report
url =3D =
"http://localhost/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:f=
ormat=3DHTML4.0&rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";
// Build the javascript to display the message
string sScript =3D "<script language=3D\"javascript\" =
type=3D\"text/javascript\">window.open(\"" + url + "\", =
\"ReportsDateSelectionGenerateReport\", =
\"height=3D675,width=3D975,left=3D0,top=3D0,copyHistory=3Dno,directories=3D=
no,location=3Dno,menubar=3Dno,resizable=3Dno,scrollbars=3Dno,status=3Dno,=
toolbar=3Dno\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), =
"LinkButtonGenerateReport_Click", sScript);


<a id=3D"runreport" runat=3D"server" target=3D"_blank" =
style=3D"font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef =3D =
"http://localhost/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:f=
ormat=3DHTML4.0&rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";


The examples below use the servername for URL access.
These work fine from other computers (because of the server name), but I =
get the Connect to <servername> popup asking for User name and Password =
when I run from the server which Reporting Services and IIS are running.
// Build the URL for the report
url =3D "http://" + <servername> + =
"/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:format=3DHTML4.0&=
rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";
// Build the javascript to display the message
string sScript =3D "<script language=3D\"javascript\" =
type=3D\"text/javascript\">window.open(\"" + url + "\", =
\"ReportsDateSelectionGenerateReport\", =
\"height=3D675,width=3D975,left=3D0,top=3D0,copyHistory=3Dno,directories=3D=
no,location=3Dno,menubar=3Dno,resizable=3Dno,scrollbars=3Dno,status=3Dno,=
toolbar=3Dno\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), =
"LinkButtonGenerateReport_Click", sScript);


<a id=3D"runreport" runat=3D"server" target=3D"_blank" =
style=3D"font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef =3D "http://" + <servername> + =
"/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:format=3DHTML4.0&=
rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";



I guess the main issue is using the servername in the URL access string =
pops up the connect to server dialog wanting a user name and password, =
even though we're trying to access the report on the server running =
Reporting Services and IIS. We're using Windows Authentication and =
impersonation (in our Web.config file), and we're logged into the server =
as local Administrator. Therefore, we should have no permissions =
issues.

How can we use the servername in URL access for both the server and =
client workstation to generate and display reports?

Thanks Bruce.

Yes, you are correct, we are running Win 2003 server with SP1.

Well, it matters because the application will be an intranet application =
in which some users actually do their work on the server, while some =
other users do their work from client workstations. This reporting =
application is just one part of a bigger suite of software that we =
develop for our customers. So, our server, running this reporting =
application is not truly an IT file/print/web server in the normal sense =
of the term. We just need Win server software and SQL Server to run our =
entire suite of applications. Hope that makes a little sense.

I fear that when management hears that end-users have to "login" again, =
they won't like that too much. So, I was trying to figure out some way =
around this issue. So, you never were able to find a work-around?


[quoted text, click to view]
My guess is that you have Windows 2003 server with SP1. This has =
additional security for browsing from the server. I never saw this =
(popup prompting) until I upgraded from 2000 server to 2003 server. I =
tried putting every configuration I could think of in the safe zone of =
IE but it didn't help.

But, why does it matter to you? As long as the clients are working =
what difference does it make if you are prompted when you do this from =
the server? I would think it would be rare to be doing this. Also, by my =
tests, you are only prompted once.


--=20
Bruce Loehle-Conger
MVP SQL Server Reporting Services
[quoted text, click to view]
We have a confusing problem and need some guidance.

We are trying to use URL access to generate and display a report. =
We have tried two ways--building the URL string and popping up a new =
browser with the Reporting Services URL access string and simply using =
an anchor tag and setting its URL parameter to the Reporting Services =
URL access string. Both options don't work--well, one works for the =
local server and the other works for client computers (not the server), =
but neither work for both.

Basically, we're having trouble using localhost vs. servername in =
our URL access string.

The examples below use localhost.
These work fine from the server which Reporting Services and IIS are =
running, but not from other computers (because of the "localhost").
// Build the URL for the report
url =3D =
"http://localhost/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:f=
ormat=3DHTML4.0&rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";
// Build the javascript to display the message
string sScript =3D "<script language=3D\"javascript\" =
type=3D\"text/javascript\">window.open(\"" + url + "\", =
\"ReportsDateSelectionGenerateReport\", =
\"height=3D675,width=3D975,left=3D0,top=3D0,copyHistory=3Dno,directories=3D=
no,location=3Dno,menubar=3Dno,resizable=3Dno,scrollbars=3Dno,status=3Dno,=
toolbar=3Dno\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), =
"LinkButtonGenerateReport_Click", sScript);


<a id=3D"runreport" runat=3D"server" target=3D"_blank" =
style=3D"font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef =3D =
"http://localhost/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:f=
ormat=3DHTML4.0&rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";


The examples below use the servername for URL access.
These work fine from other computers (because of the server name), =
but I get the Connect to <servername> popup asking for User name and =
Password when I run from the server which Reporting Services and IIS are =
running.
// Build the URL for the report
url =3D "http://" + <servername> + =
"/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:format=3DHTML4.0&=
rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";
// Build the javascript to display the message
string sScript =3D "<script language=3D\"javascript\" =
type=3D\"text/javascript\">window.open(\"" + url + "\", =
\"ReportsDateSelectionGenerateReport\", =
\"height=3D675,width=3D975,left=3D0,top=3D0,copyHistory=3Dno,directories=3D=
no,location=3Dno,menubar=3Dno,resizable=3Dno,scrollbars=3Dno,status=3Dno,=
toolbar=3Dno\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), =
"LinkButtonGenerateReport_Click", sScript);


<a id=3D"runreport" runat=3D"server" target=3D"_blank" =
style=3D"font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef =3D "http://" + <servername> + =
"/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:format=3DHTML4.0&=
rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";



I guess the main issue is using the servername in the URL access =
string pops up the connect to server dialog wanting a user name and =
password, even though we're trying to access the report on the server =
running Reporting Services and IIS. We're using Windows Authentication =
and impersonation (in our Web.config file), and we're logged into the =
server as local Administrator. Therefore, we should have no permissions =
issues.

How can we use the servername in URL access for both the server and =
client workstation to generate and display reports?

My guess is that you have Windows 2003 server with SP1. This has =
additional security for browsing from the server. I never saw this =
(popup prompting) until I upgraded from 2000 server to 2003 server. I =
tried putting every configuration I could think of in the safe zone of =
IE but it didn't help.

But, why does it matter to you? As long as the clients are working what =
difference does it make if you are prompted when you do this from the =
server? I would think it would be rare to be doing this. Also, by my =
tests, you are only prompted once.


--=20
Bruce Loehle-Conger
MVP SQL Server Reporting Services
[quoted text, click to view]
We have a confusing problem and need some guidance.

We are trying to use URL access to generate and display a report. We =
have tried two ways--building the URL string and popping up a new =
browser with the Reporting Services URL access string and simply using =
an anchor tag and setting its URL parameter to the Reporting Services =
URL access string. Both options don't work--well, one works for the =
local server and the other works for client computers (not the server), =
but neither work for both.

Basically, we're having trouble using localhost vs. servername in our =
URL access string.

The examples below use localhost.
These work fine from the server which Reporting Services and IIS are =
running, but not from other computers (because of the "localhost").
// Build the URL for the report
url =3D =
"http://localhost/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:f=
ormat=3DHTML4.0&rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";
// Build the javascript to display the message
string sScript =3D "<script language=3D\"javascript\" =
type=3D\"text/javascript\">window.open(\"" + url + "\", =
\"ReportsDateSelectionGenerateReport\", =
\"height=3D675,width=3D975,left=3D0,top=3D0,copyHistory=3Dno,directories=3D=
no,location=3Dno,menubar=3Dno,resizable=3Dno,scrollbars=3Dno,status=3Dno,=
toolbar=3Dno\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), =
"LinkButtonGenerateReport_Click", sScript);


<a id=3D"runreport" runat=3D"server" target=3D"_blank" =
style=3D"font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef =3D =
"http://localhost/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:f=
ormat=3DHTML4.0&rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";


The examples below use the servername for URL access.
These work fine from other computers (because of the server name), but =
I get the Connect to <servername> popup asking for User name and =
Password when I run from the server which Reporting Services and IIS are =
running.
// Build the URL for the report
url =3D "http://" + <servername> + =
"/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:format=3DHTML4.0&=
rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";
// Build the javascript to display the message
string sScript =3D "<script language=3D\"javascript\" =
type=3D\"text/javascript\">window.open(\"" + url + "\", =
\"ReportsDateSelectionGenerateReport\", =
\"height=3D675,width=3D975,left=3D0,top=3D0,copyHistory=3Dno,directories=3D=
no,location=3Dno,menubar=3Dno,resizable=3Dno,scrollbars=3Dno,status=3Dno,=
toolbar=3Dno\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), =
"LinkButtonGenerateReport_Click", sScript);


<a id=3D"runreport" runat=3D"server" target=3D"_blank" =
style=3D"font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef =3D "http://" + <servername> + =
"/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:format=3DHTML4.0&=
rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";



I guess the main issue is using the servername in the URL access =
string pops up the connect to server dialog wanting a user name and =
password, even though we're trying to access the report on the server =
running Reporting Services and IIS. We're using Windows Authentication =
and impersonation (in our Web.config file), and we're logged into the =
server as local Administrator. Therefore, we should have no permissions =
issues.

How can we use the servername in URL access for both the server and =
client workstation to generate and display reports?

Sorry. We are using SQL Server 2005. And, yes, we have developed an =
ASP.NET 2.0 (C#) application in which one of the pages builds the URL =
access string for end-users to click a link and generate and view the =
report.

I'll look into the new viewer control. Thanks. Any other suggestions?


[quoted text, click to view]
You didn't say if you are using RS 2000 or RS 2005. It sounds like you =
are using this from your own web page. What I suggest is to use the new =
control from VS 2005. My guess is this will get around your problem. The =
new control uses web services instead of URL integration. If you have to =
use RS 2000 then look into using web services if this is an important =
issue for you.


--=20
Bruce Loehle-Conger
MVP SQL Server Reporting Services


[quoted text, click to view]
Thanks Bruce.

Yes, you are correct, we are running Win 2003 server with SP1.

Well, it matters because the application will be an intranet =
application in which some users actually do their work on the server, =
while some other users do their work from client workstations. This =
reporting application is just one part of a bigger suite of software =
that we develop for our customers. So, our server, running this =
reporting application is not truly an IT file/print/web server in the =
normal sense of the term. We just need Win server software and SQL =
Server to run our entire suite of applications. Hope that makes a =
little sense.

I fear that when management hears that end-users have to "login" =
again, they won't like that too much. So, I was trying to figure out =
some way around this issue. So, you never were able to find a =
work-around?


[quoted text, click to view]
My guess is that you have Windows 2003 server with SP1. This has =
additional security for browsing from the server. I never saw this =
(popup prompting) until I upgraded from 2000 server to 2003 server. I =
tried putting every configuration I could think of in the safe zone of =
IE but it didn't help.

But, why does it matter to you? As long as the clients are working =
what difference does it make if you are prompted when you do this from =
the server? I would think it would be rare to be doing this. Also, by my =
tests, you are only prompted once.


--=20
Bruce Loehle-Conger
MVP SQL Server Reporting Services
[quoted text, click to view]
We have a confusing problem and need some guidance.

We are trying to use URL access to generate and display a =
report. We have tried two ways--building the URL string and popping up =
a new browser with the Reporting Services URL access string and simply =
using an anchor tag and setting its URL parameter to the Reporting =
Services URL access string. Both options don't work--well, one works =
for the local server and the other works for client computers (not the =
server), but neither work for both.

Basically, we're having trouble using localhost vs. servername =
in our URL access string.

The examples below use localhost.
These work fine from the server which Reporting Services and IIS =
are running, but not from other computers (because of the "localhost").
// Build the URL for the report
url =3D =
"http://localhost/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:f=
ormat=3DHTML4.0&rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";
// Build the javascript to display the message
string sScript =3D "<script language=3D\"javascript\" =
type=3D\"text/javascript\">window.open(\"" + url + "\", =
\"ReportsDateSelectionGenerateReport\", =
\"height=3D675,width=3D975,left=3D0,top=3D0,copyHistory=3Dno,directories=3D=
no,location=3Dno,menubar=3Dno,resizable=3Dno,scrollbars=3Dno,status=3Dno,=
toolbar=3Dno\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), =
"LinkButtonGenerateReport_Click", sScript);


<a id=3D"runreport" runat=3D"server" target=3D"_blank" =
style=3D"font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef =3D =
"http://localhost/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:f=
ormat=3DHTML4.0&rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";


The examples below use the servername for URL access.
These work fine from other computers (because of the server =
name), but I get the Connect to <servername> popup asking for User name =
and Password when I run from the server which Reporting Services and IIS =
are running.
// Build the URL for the report
url =3D "http://" + <servername> + =
"/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:format=3DHTML4.0&=
rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";
// Build the javascript to display the message
string sScript =3D "<script language=3D\"javascript\" =
type=3D\"text/javascript\">window.open(\"" + url + "\", =
\"ReportsDateSelectionGenerateReport\", =
\"height=3D675,width=3D975,left=3D0,top=3D0,copyHistory=3Dno,directories=3D=
no,location=3Dno,menubar=3Dno,resizable=3Dno,scrollbars=3Dno,status=3Dno,=
toolbar=3Dno\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), =
"LinkButtonGenerateReport_Click", sScript);


<a id=3D"runreport" runat=3D"server" target=3D"_blank" =
style=3D"font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef =3D "http://" + <servername> + =
"/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:format=3DHTML4.0&=
rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";



I guess the main issue is using the servername in the URL access =
string pops up the connect to server dialog wanting a user name and =
password, even though we're trying to access the report on the server =
running Reporting Services and IIS. We're using Windows Authentication =
and impersonation (in our Web.config file), and we're logged into the =
server as local Administrator. Therefore, we should have no permissions =
issues.

How can we use the servername in URL access for both the server =
and client workstation to generate and display reports?

You didn't say if you are using RS 2000 or RS 2005. It sounds like you =
are using this from your own web page. What I suggest is to use the new =
control from VS 2005. My guess is this will get around your problem. The =
new control uses web services instead of URL integration. If you have to =
use RS 2000 then look into using web services if this is an important =
issue for you.


--=20
Bruce Loehle-Conger
MVP SQL Server Reporting Services


[quoted text, click to view]
Thanks Bruce.

Yes, you are correct, we are running Win 2003 server with SP1.

Well, it matters because the application will be an intranet =
application in which some users actually do their work on the server, =
while some other users do their work from client workstations. This =
reporting application is just one part of a bigger suite of software =
that we develop for our customers. So, our server, running this =
reporting application is not truly an IT file/print/web server in the =
normal sense of the term. We just need Win server software and SQL =
Server to run our entire suite of applications. Hope that makes a =
little sense.

I fear that when management hears that end-users have to "login" =
again, they won't like that too much. So, I was trying to figure out =
some way around this issue. So, you never were able to find a =
work-around?


[quoted text, click to view]
My guess is that you have Windows 2003 server with SP1. This has =
additional security for browsing from the server. I never saw this =
(popup prompting) until I upgraded from 2000 server to 2003 server. I =
tried putting every configuration I could think of in the safe zone of =
IE but it didn't help.

But, why does it matter to you? As long as the clients are working =
what difference does it make if you are prompted when you do this from =
the server? I would think it would be rare to be doing this. Also, by my =
tests, you are only prompted once.


--=20
Bruce Loehle-Conger
MVP SQL Server Reporting Services
[quoted text, click to view]
We have a confusing problem and need some guidance.

We are trying to use URL access to generate and display a report. =
We have tried two ways--building the URL string and popping up a new =
browser with the Reporting Services URL access string and simply using =
an anchor tag and setting its URL parameter to the Reporting Services =
URL access string. Both options don't work--well, one works for the =
local server and the other works for client computers (not the server), =
but neither work for both.

Basically, we're having trouble using localhost vs. servername in =
our URL access string.

The examples below use localhost.
These work fine from the server which Reporting Services and IIS =
are running, but not from other computers (because of the "localhost").
// Build the URL for the report
url =3D =
"http://localhost/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:f=
ormat=3DHTML4.0&rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";
// Build the javascript to display the message
string sScript =3D "<script language=3D\"javascript\" =
type=3D\"text/javascript\">window.open(\"" + url + "\", =
\"ReportsDateSelectionGenerateReport\", =
\"height=3D675,width=3D975,left=3D0,top=3D0,copyHistory=3Dno,directories=3D=
no,location=3Dno,menubar=3Dno,resizable=3Dno,scrollbars=3Dno,status=3Dno,=
toolbar=3Dno\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), =
"LinkButtonGenerateReport_Click", sScript);


<a id=3D"runreport" runat=3D"server" target=3D"_blank" =
style=3D"font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef =3D =
"http://localhost/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:f=
ormat=3DHTML4.0&rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";


The examples below use the servername for URL access.
These work fine from other computers (because of the server name), =
but I get the Connect to <servername> popup asking for User name and =
Password when I run from the server which Reporting Services and IIS are =
running.
// Build the URL for the report
url =3D "http://" + <servername> + =
"/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:format=3DHTML4.0&=
rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";
// Build the javascript to display the message
string sScript =3D "<script language=3D\"javascript\" =
type=3D\"text/javascript\">window.open(\"" + url + "\", =
\"ReportsDateSelectionGenerateReport\", =
\"height=3D675,width=3D975,left=3D0,top=3D0,copyHistory=3Dno,directories=3D=
no,location=3Dno,menubar=3Dno,resizable=3Dno,scrollbars=3Dno,status=3Dno,=
toolbar=3Dno\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), =
"LinkButtonGenerateReport_Click", sScript);


<a id=3D"runreport" runat=3D"server" target=3D"_blank" =
style=3D"font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef =3D "http://" + <servername> + =
"/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:format=3DHTML4.0&=
rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";



I guess the main issue is using the servername in the URL access =
string pops up the connect to server dialog wanting a user name and =
password, even though we're trying to access the report on the server =
running Reporting Services and IIS. We're using Windows Authentication =
and impersonation (in our Web.config file), and we're logged into the =
server as local Administrator. Therefore, we should have no permissions =
issues.

How can we use the servername in URL access for both the server =
and client workstation to generate and display reports?

No other suggestions. The new controls come with VS, they are not on the =
SQL Server disk. The controls are very nice and are a much better way to =
go than URL integration. I have only used the Winform control but the =
Webform control is supposed to have similar functionality.


--=20
Bruce Loehle-Conger
MVP SQL Server Reporting Services
[quoted text, click to view]
Sorry. We are using SQL Server 2005. And, yes, we have developed an =
ASP.NET 2.0 (C#) application in which one of the pages builds the URL =
access string for end-users to click a link and generate and view the =
report.

I'll look into the new viewer control. Thanks. Any other =
suggestions?


[quoted text, click to view]
You didn't say if you are using RS 2000 or RS 2005. It sounds like =
you are using this from your own web page. What I suggest is to use the =
new control from VS 2005. My guess is this will get around your problem. =
The new control uses web services instead of URL integration. If you =
have to use RS 2000 then look into using web services if this is an =
important issue for you.


--=20
Bruce Loehle-Conger
MVP SQL Server Reporting Services


[quoted text, click to view]
Thanks Bruce.

Yes, you are correct, we are running Win 2003 server with SP1.

Well, it matters because the application will be an intranet =
application in which some users actually do their work on the server, =
while some other users do their work from client workstations. This =
reporting application is just one part of a bigger suite of software =
that we develop for our customers. So, our server, running this =
reporting application is not truly an IT file/print/web server in the =
normal sense of the term. We just need Win server software and SQL =
Server to run our entire suite of applications. Hope that makes a =
little sense.

I fear that when management hears that end-users have to "login" =
again, they won't like that too much. So, I was trying to figure out =
some way around this issue. So, you never were able to find a =
work-around?


[quoted text, click to view]
My guess is that you have Windows 2003 server with SP1. This has =
additional security for browsing from the server. I never saw this =
(popup prompting) until I upgraded from 2000 server to 2003 server. I =
tried putting every configuration I could think of in the safe zone of =
IE but it didn't help.

But, why does it matter to you? As long as the clients are =
working what difference does it make if you are prompted when you do =
this from the server? I would think it would be rare to be doing this. =
Also, by my tests, you are only prompted once.


--=20
Bruce Loehle-Conger
MVP SQL Server Reporting Services
[quoted text, click to view]
We have a confusing problem and need some guidance.

We are trying to use URL access to generate and display a =
report. We have tried two ways--building the URL string and popping up =
a new browser with the Reporting Services URL access string and simply =
using an anchor tag and setting its URL parameter to the Reporting =
Services URL access string. Both options don't work--well, one works =
for the local server and the other works for client computers (not the =
server), but neither work for both.

Basically, we're having trouble using localhost vs. servername =
in our URL access string.

The examples below use localhost.
These work fine from the server which Reporting Services and =
IIS are running, but not from other computers (because of the =
"localhost").
// Build the URL for the report
url =3D =
"http://localhost/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:f=
ormat=3DHTML4.0&rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";
// Build the javascript to display the message
string sScript =3D "<script language=3D\"javascript\" =
type=3D\"text/javascript\">window.open(\"" + url + "\", =
\"ReportsDateSelectionGenerateReport\", =
\"height=3D675,width=3D975,left=3D0,top=3D0,copyHistory=3Dno,directories=3D=
no,location=3Dno,menubar=3Dno,resizable=3Dno,scrollbars=3Dno,status=3Dno,=
toolbar=3Dno\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), =
"LinkButtonGenerateReport_Click", sScript);


<a id=3D"runreport" runat=3D"server" target=3D"_blank" =
style=3D"font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef =3D =
"http://localhost/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:f=
ormat=3DHTML4.0&rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";


The examples below use the servername for URL access.
These work fine from other computers (because of the server =
name), but I get the Connect to <servername> popup asking for User name =
and Password when I run from the server which Reporting Services and IIS =
are running.
// Build the URL for the report
url =3D "http://" + <servername> + =
"/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:format=3DHTML4.0&=
rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";
// Build the javascript to display the message
string sScript =3D "<script language=3D\"javascript\" =
type=3D\"text/javascript\">window.open(\"" + url + "\", =
\"ReportsDateSelectionGenerateReport\", =
\"height=3D675,width=3D975,left=3D0,top=3D0,copyHistory=3Dno,directories=3D=
no,location=3Dno,menubar=3Dno,resizable=3Dno,scrollbars=3Dno,status=3Dno,=
toolbar=3Dno\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), =
"LinkButtonGenerateReport_Click", sScript);


<a id=3D"runreport" runat=3D"server" target=3D"_blank" =
style=3D"font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef =3D "http://" + <servername> + =
"/ReportServer?/Reports/MyReport&rs:Command=3DRender&rs:format=3DHTML4.0&=
rc:Parameters=3Dfalse&rc:Zoom=3DPage Width";



I guess the main issue is using the servername in the URL =
access string pops up the connect to server dialog wanting a user name =
and password, even though we're trying to access the report on the =
server running Reporting Services and IIS. We're using Windows =
Authentication and impersonation (in our Web.config file), and we're =