SSRS 2016 Sporatic Error rrRenderingError
up vote
0
down vote
favorite
I have an SSRS 2016 Report. When I run the report by clicking the report in the SSRS Site it runs fine. When I use the url to create the pdf like this:
http://vmbksa69901mdt/ReportServer_ssrs1p?/DAS/CDO_Suite/PortfolioHoldings&rs:Command=Render&ReportName=OCTAGO28_Portfolio_Holdings_pdf_1&rs:Format=PDF
It gives me the error:
The webpage at
http://vmbksa69901mdt/ReportServer_ssrs1p?/DAS/CDO_Suite/PortfolioHoldings&rs:Command=Render&ReportName=OCTAGO28_Portfolio_Holdings_pdf_1&rs:Format=PDF
might be temporarily down or it may have moved permanently to a new
web address. ERR_INVALID_RESPONSE
When I look at the view [dbo].[ExecutionLog3], it shows an error of rrRenderingError.
What's odd is that if I change the url and put the "format=Excel", it works fine. And then right away change it back to PDF it works fine.
So my guess is this is a timeout issue. Can anyone tell if that is a valid assumption? If it is, how do I go about changing that timeout? The underlying stored procedure for the report can take > 60s.
If it's not a timeout, how do I dig deeper into the logs to show me what the error really could be?
sql-server reporting-services ssrs-2016 edited Nov 8 at 16:19
jarlh
27.8k52137
asked Nov 8 at 16:13
Bill Schanks
53110
add a comment |
up vote
0
down vote
favorite
I have an SSRS 2016 Report. When I run the report by clicking the report in the SSRS Site it runs fine. When I use the url to create the pdf like this:
http://vmbksa69901mdt/ReportServer_ssrs1p?/DAS/CDO_Suite/PortfolioHoldings&rs:Command=Render&ReportName=OCTAGO28_Portfolio_Holdings_pdf_1&rs:Format=PDF
It gives me the error:
The webpage at
http://vmbksa69901mdt/ReportServer_ssrs1p?/DAS/CDO_Suite/PortfolioHoldings&rs:Command=Render&ReportName=OCTAGO28_Portfolio_Holdings_pdf_1&rs:Format=PDF
might be temporarily down or it may have moved permanently to a new
web address. ERR_INVALID_RESPONSE
When I look at the view [dbo].[ExecutionLog3], it shows an error of rrRenderingError.
What's odd is that if I change the url and put the "format=Excel", it works fine. And then right away change it back to PDF it works fine.
So my guess is this is a timeout issue. Can anyone tell if that is a valid assumption? If it is, how do I go about changing that timeout? The underlying stored procedure for the report can take > 60s.
If it's not a timeout, how do I dig deeper into the logs to show me what the error really could be?
sql-server reporting-services ssrs-2016 edited Nov 8 at 16:19
jarlh
27.8k52137
asked Nov 8 at 16:13
Bill Schanks
53110
depending on your setup there may be several areas that could timeout. It sounds like you are using a shared dataset though as this might explain why it works on subsequent runs. Check this link, it might be useful docs.microsoft.com/en-us/sql/reporting-services/report-server/…
– Alan Schofield
Nov 8 at 16:55
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have an SSRS 2016 Report. When I run the report by clicking the report in the SSRS Site it runs fine. When I use the url to create the pdf like this:
http://vmbksa69901mdt/ReportServer_ssrs1p?/DAS/CDO_Suite/PortfolioHoldings&rs:Command=Render&ReportName=OCTAGO28_Portfolio_Holdings_pdf_1&rs:Format=PDF
It gives me the error:
The webpage at
http://vmbksa69901mdt/ReportServer_ssrs1p?/DAS/CDO_Suite/PortfolioHoldings&rs:Command=Render&ReportName=OCTAGO28_Portfolio_Holdings_pdf_1&rs:Format=PDF
might be temporarily down or it may have moved permanently to a new
web address. ERR_INVALID_RESPONSE
When I look at the view [dbo].[ExecutionLog3], it shows an error of rrRenderingError.
What's odd is that if I change the url and put the "format=Excel", it works fine. And then right away change it back to PDF it works fine.
So my guess is this is a timeout issue. Can anyone tell if that is a valid assumption? If it is, how do I go about changing that timeout? The underlying stored procedure for the report can take > 60s.
If it's not a timeout, how do I dig deeper into the logs to show me what the error really could be?
sql-server reporting-services ssrs-2016 edited Nov 8 at 16:19
jarlh
27.8k52137
asked Nov 8 at 16:13
Bill Schanks
53110
I have an SSRS 2016 Report. When I run the report by clicking the report in the SSRS Site it runs fine. When I use the url to create the pdf like this:
http://vmbksa69901mdt/ReportServer_ssrs1p?/DAS/CDO_Suite/PortfolioHoldings&rs:Command=Render&ReportName=OCTAGO28_Portfolio_Holdings_pdf_1&rs:Format=PDF
It gives me the error:
The webpage at
http://vmbksa69901mdt/ReportServer_ssrs1p?/DAS/CDO_Suite/PortfolioHoldings&rs:Command=Render&ReportName=OCTAGO28_Portfolio_Holdings_pdf_1&rs:Format=PDF
might be temporarily down or it may have moved permanently to a new
web address. ERR_INVALID_RESPONSE
When I look at the view [dbo].[ExecutionLog3], it shows an error of rrRenderingError.
What's odd is that if I change the url and put the "format=Excel", it works fine. And then right away change it back to PDF it works fine.
So my guess is this is a timeout issue. Can anyone tell if that is a valid assumption? If it is, how do I go about changing that timeout? The underlying stored procedure for the report can take > 60s.
If it's not a timeout, how do I dig deeper into the logs to show me what the error really could be?
sql-server reporting-services ssrs-2016 sql-server reporting-services ssrs-2016 edited Nov 8 at 16:19
jarlh
27.8k52137
asked Nov 8 at 16:13
Bill Schanks
53110
edited Nov 8 at 16:19
jarlh
27.8k52137
asked Nov 8 at 16:13
Bill Schanks
53110
edited Nov 8 at 16:19
jarlh
27.8k52137
edited Nov 8 at 16:19
jarlh
27.8k52137
edited Nov 8 at 16:19
jarlh
27.8k52137
27.8k52137
asked Nov 8 at 16:13
Bill Schanks
53110
asked Nov 8 at 16:13
Bill Schanks
53110
asked Nov 8 at 16:13
Bill Schanks
53110
53110
depending on your setup there may be several areas that could timeout. It sounds like you are using a shared dataset though as this might explain why it works on subsequent runs. Check this link, it might be useful docs.microsoft.com/en-us/sql/reporting-services/report-server/…
– Alan Schofield
Nov 8 at 16:55
add a comment |
depending on your setup there may be several areas that could timeout. It sounds like you are using a shared dataset though as this might explain why it works on subsequent runs. Check this link, it might be useful docs.microsoft.com/en-us/sql/reporting-services/report-server/…
– Alan Schofield
Nov 8 at 16:55
depending on your setup there may be several areas that could timeout. It sounds like you are using a shared dataset though as this might explain why it works on subsequent runs. Check this link, it might be useful docs.microsoft.com/en-us/sql/reporting-services/report-server/…
– Alan Schofield
Nov 8 at 16:55
depending on your setup there may be several areas that could timeout. It sounds like you are using a shared dataset though as this might explain why it works on subsequent runs. Check this link, it might be useful docs.microsoft.com/en-us/sql/reporting-services/report-server/…
– Alan Schofield
Nov 8 at 16:55
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53211763%2fssrs-2016-sporatic-error-rrrenderingerror%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
depending on your setup there may be several areas that could timeout. It sounds like you are using a shared dataset though as this might explain why it works on subsequent runs. Check this link, it might be useful docs.microsoft.com/en-us/sql/reporting-services/report-server/…
– Alan Schofield
Nov 8 at 16:55