We have an SSL cert in place on our production platform and for some reason
the help link in report manager is calling the help page through http, not
https and subsequently the call fails.
Does anyone know if it is possible to change the link to https somewhere in
the config files?
All other links work OK.
Thanks
DarrenHi Darren,
I have the same problem...
Did you manage to find a resolution?
Cant seem to find one on the newsgroups.
Many Thanks
Alex Young
"Darren" wrote:
> We have an SSL cert in place on our production platform and for some reason
> the help link in report manager is calling the help page through http, not
> https and subsequently the call fails.
> Does anyone know if it is possible to change the link to https somewhere in
> the config files?
> All other links work OK.
> Thanks
> Darren|||This is a known issue in RS. There is unfortunately no work around.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Alex Young" <Alex Young@.discussions.microsoft.com> wrote in message
news:86358E44-48A6-4549-B059-1EE867CD647B@.microsoft.com...
> Hi Darren,
> I have the same problem...
> Did you manage to find a resolution?
> Cant seem to find one on the newsgroups.
> Many Thanks
> Alex Young
> "Darren" wrote:
>> We have an SSL cert in place on our production platform and for some
>> reason
>> the help link in report manager is calling the help page through http,
>> not
>> https and subsequently the call fails.
>> Does anyone know if it is possible to change the link to https somewhere
>> in
>> the config files?
>> All other links work OK.
>> Thanks
>> Darren|||Thanks for this. In the end I got the firewall config changed to allow http
as well as https.
Darren
"Daniel Reib [MSFT]" wrote:
> This is a known issue in RS. There is unfortunately no work around.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Alex Young" <Alex Young@.discussions.microsoft.com> wrote in message
> news:86358E44-48A6-4549-B059-1EE867CD647B@.microsoft.com...
> > Hi Darren,
> >
> > I have the same problem...
> >
> > Did you manage to find a resolution?
> >
> > Cant seem to find one on the newsgroups.
> >
> > Many Thanks
> >
> > Alex Young
> >
> > "Darren" wrote:
> >
> >> We have an SSL cert in place on our production platform and for some
> >> reason
> >> the help link in report manager is calling the help page through http,
> >> not
> >> https and subsequently the call fails.
> >>
> >> Does anyone know if it is possible to change the link to https somewhere
> >> in
> >> the config files?
> >> All other links work OK.
> >>
> >> Thanks
> >> Darren
>
>|||Is this a known issue only with the "Help" link OR also with links such as
"Home", "My Subscriptions" etc in Report Manager?
"Daniel Reib [MSFT]" wrote:
> This is a known issue in RS. There is unfortunately no work around.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Alex Young" <Alex Young@.discussions.microsoft.com> wrote in message
> news:86358E44-48A6-4549-B059-1EE867CD647B@.microsoft.com...
> > Hi Darren,
> >
> > I have the same problem...
> >
> > Did you manage to find a resolution?
> >
> > Cant seem to find one on the newsgroups.
> >
> > Many Thanks
> >
> > Alex Young
> >
> > "Darren" wrote:
> >
> >> We have an SSL cert in place on our production platform and for some
> >> reason
> >> the help link in report manager is calling the help page through http,
> >> not
> >> https and subsequently the call fails.
> >>
> >> Does anyone know if it is possible to change the link to https somewhere
> >> in
> >> the config files?
> >> All other links work OK.
> >>
> >> Thanks
> >> Darren
>
>|||Just with the help link.
-Mo|||Alex and Darren,
Sorry to disagree with Daniel Reib. There is a work around.
1) Access the IIS Manager
2) Go to the Default Web Site. Find the 'Reports' virtual directory and
expand
3) Locate the folders that have a sub folder â'helpâ'.
4) Right click and select properties
5) Go to the Directory Security tab, click the â'Editâ' button under Secure
communications
6) Uncheck the checkbox for â'Require secure channel (SSL)â'.
7) All the sub folders with that contain a help file donâ't require
SSL â'deâ', â'enâ', â'esâ', â'frâ', â'itâ', â'jaâ', â'koâ'.
Your Help link should work. The Help files really don't require SSL anyway.
Cheers!
Showing posts with label production. Show all posts
Showing posts with label production. Show all posts
Monday, March 12, 2012
Friday, March 9, 2012
Report Manager blank
I've got a report that works fine in development (and in production too until
recently) but no longer loads in production. When I click "View Report", it
just reloads the page as it is, without generating a report.
I've tried deleting and reloading it clean into production, but with the
same results.
I'd think it was something wrong with my stored procedure, except that it
has been working fine in development (and working off the same database as in
production).
Is there anything like this that anyone else has run into?I have seen this as a credential problem (reason that it is blank). Check
that the credential for the report has the proper rights for the SP.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mike R" <MikeR@.discussions.microsoft.com> wrote in message
news:D737759F-EF2D-48C3-81B8-5205DF64C4DA@.microsoft.com...
> I've got a report that works fine in development (and in production too
> until
> recently) but no longer loads in production. When I click "View Report",
> it
> just reloads the page as it is, without generating a report.
> I've tried deleting and reloading it clean into production, but with the
> same results.
> I'd think it was something wrong with my stored procedure, except that it
> has been working fine in development (and working off the same database as
> in
> production).
> Is there anything like this that anyone else has run into?
recently) but no longer loads in production. When I click "View Report", it
just reloads the page as it is, without generating a report.
I've tried deleting and reloading it clean into production, but with the
same results.
I'd think it was something wrong with my stored procedure, except that it
has been working fine in development (and working off the same database as in
production).
Is there anything like this that anyone else has run into?I have seen this as a credential problem (reason that it is blank). Check
that the credential for the report has the proper rights for the SP.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mike R" <MikeR@.discussions.microsoft.com> wrote in message
news:D737759F-EF2D-48C3-81B8-5205DF64C4DA@.microsoft.com...
> I've got a report that works fine in development (and in production too
> until
> recently) but no longer loads in production. When I click "View Report",
> it
> just reloads the page as it is, without generating a report.
> I've tried deleting and reloading it clean into production, but with the
> same results.
> I'd think it was something wrong with my stored procedure, except that it
> has been working fine in development (and working off the same database as
> in
> production).
> Is there anything like this that anyone else has run into?
Wednesday, March 7, 2012
Report is rssuccess but browser continues until time out (no document returned)
Hi,
Basically, we're having a problem on our production servers, that is
that a report is running for 2h (this is expected, large data set) and
IE6 is setup up for a 4h timeout (via a registry entry). The browser
will display the spinning report generation icon for the entire 4h
before timing out. However, the server log is reporting that the report
had succeeded (rssuccess), 1.5 hours BEFORE the browser fails.
Servers/Services are Win2003, Reporting Services SP2, SQL Server 2000
SP3
The machines sit behind a load balancer, which might be important (HTTP
requests etc.).
We're stumped :-(
Any ideas?
Thanks
RolandoWhat happens after the browser fails? What indication points out that
the browser fails?
It gives you a "This application needs to be closed" error?
Is there a different error? It just freezes?|||Sorcerdon,
When the browsers times out at its designated timeout value (4 hours),
we get the standard IE6 "Page cannot be displayed" page.
Do you have some idea of what might be going on?
Thanks|||Try running it and turn off "Show friendly HTTP messeges" in the
browser options.
Go to Options --> ADvanced tab --> Its under Browsing.
This will provide you with a more detailed error messege.
BTW, where is this error show up? in the actual report window? or it
redirects to the error page?
regards,
Stas K.
Basically, we're having a problem on our production servers, that is
that a report is running for 2h (this is expected, large data set) and
IE6 is setup up for a 4h timeout (via a registry entry). The browser
will display the spinning report generation icon for the entire 4h
before timing out. However, the server log is reporting that the report
had succeeded (rssuccess), 1.5 hours BEFORE the browser fails.
Servers/Services are Win2003, Reporting Services SP2, SQL Server 2000
SP3
The machines sit behind a load balancer, which might be important (HTTP
requests etc.).
We're stumped :-(
Any ideas?
Thanks
RolandoWhat happens after the browser fails? What indication points out that
the browser fails?
It gives you a "This application needs to be closed" error?
Is there a different error? It just freezes?|||Sorcerdon,
When the browsers times out at its designated timeout value (4 hours),
we get the standard IE6 "Page cannot be displayed" page.
Do you have some idea of what might be going on?
Thanks|||Try running it and turn off "Show friendly HTTP messeges" in the
browser options.
Go to Options --> ADvanced tab --> Its under Browsing.
This will provide you with a more detailed error messege.
BTW, where is this error show up? in the actual report window? or it
redirects to the error page?
regards,
Stas K.
Report is rendered @ a smaller scale when printing from production
ISSUE: We have a report that prints at about 59% of normal size when printing
from production. Testing this report from the test server prints normally at
100%. Print Services and SQL servers have been rebooted, PrintService and
ReportServer stopped and restarted etc... What could cause this type of
behavior? Where should I begin to troubleshoot?On Sun, 3 Apr 2005 10:31:04 -0700, Jeremy
<Jeremy@.discussions.microsoft.com> wrote:
>ISSUE: We have a report that prints at about 59% of normal size when printing
>from production. Testing this report from the test server prints normally at
>100%. Print Services and SQL servers have been rebooted, PrintService and
>ReportServer stopped and restarted etc... What could cause this type of
>behavior? Where should I begin to troubleshoot?
Jeremy,
It's possible that someone will be have directly experienced this and
can offer an instant solution.
It's not 100% clear to me whether the problem is confined to a single
report or not. If it is a single report then that report would be the
focus. If it happens to multiple reports then it is a different
situation.
If not, I would suggest that you describe in more detail the setup
that works as expected and, more importantly, the setup that doesn't
behave as expected.
Andrew Watt
MVP - InfoPath
from production. Testing this report from the test server prints normally at
100%. Print Services and SQL servers have been rebooted, PrintService and
ReportServer stopped and restarted etc... What could cause this type of
behavior? Where should I begin to troubleshoot?On Sun, 3 Apr 2005 10:31:04 -0700, Jeremy
<Jeremy@.discussions.microsoft.com> wrote:
>ISSUE: We have a report that prints at about 59% of normal size when printing
>from production. Testing this report from the test server prints normally at
>100%. Print Services and SQL servers have been rebooted, PrintService and
>ReportServer stopped and restarted etc... What could cause this type of
>behavior? Where should I begin to troubleshoot?
Jeremy,
It's possible that someone will be have directly experienced this and
can offer an instant solution.
It's not 100% clear to me whether the problem is confined to a single
report or not. If it is a single report then that report would be the
focus. If it happens to multiple reports then it is a different
situation.
If not, I would suggest that you describe in more detail the setup
that works as expected and, more importantly, the setup that doesn't
behave as expected.
Andrew Watt
MVP - InfoPath
Subscribe to:
Posts (Atom)