I have a problem when opening a sql 2000 report in a new window. As
soon as the the report is opened, asp.net post-backs will fail.
This is what I do:
window.open('http//:[ip address]/reportserver?/ReportFolder/
ReportName')
As soon as I do that, asp.net post-backs on the opener will 'do
nothing'.
strange thing is that if I open the report using the name of the
server rather than ip address, it works fine
window.open('http//:[server name]/reportserver?/ReportFolder/
ReportName')
it also works fine on a development machine using 'localhost'.
The behavior I describe happens when the application is deployed to a
production server. Our customer must use the ip address of the server
for various reasons.
I've tried using a relative url ('../../reportserver?...') and i get
the same behaviour.
Any ideas?Have you tried using Globals!ReportServerUrl
"ruben@.lindenservices.com" wrote:
> I have a problem when opening a sql 2000 report in a new window. As
> soon as the the report is opened, asp.net post-backs will fail.
> This is what I do:
> window.open('http//:[ip address]/reportserver?/ReportFolder/
> ReportName')
> As soon as I do that, asp.net post-backs on the opener will 'do
> nothing'.
> strange thing is that if I open the report using the name of the
> server rather than ip address, it works fine
> window.open('http//:[server name]/reportserver?/ReportFolder/
> ReportName')
> it also works fine on a development machine using 'localhost'.
> The behavior I describe happens when the application is deployed to a
> production server. Our customer must use the ip address of the server
> for various reasons.
> I've tried using a relative url ('../../reportserver?...') and i get
> the same behaviour.
> Any ideas?
>sql
No comments:
Post a Comment