Export to PDF - crashing for larger sets of data

Hi Group,
I posted this problem two days ago, but it went unanswered, so here I am,
giving it another try - it's really important for us !
Reformulation :
We have a report that we can run in ReportManager. It takes about 15-20
second to generate, but it displays the html on the screen.
It lets us navigate to the last page and back without any problem.
The problem comes when we try to export this report to PDF format : once I
click the export link, it waits for 60 to 90 seconds, then it displays the
error message :
*************************************************************
Server Application Unavailable
The web application you are attempting to access on this web server is
currently unavailable. Please hit the "Refresh" button in your web browser
to retry your request.
Administrator Note: An error message detailing the cause of this specific
request failure can be found in the application event log of the web server.
Please review this log entry to discover what caused this error to occur.
***************************************************************
Other information :
- the same report, for smaller amounts of data, works fine when exported to
pdf.
- the same report, when exported to either XML or CSV, works fine - the
files are created.
- we have a lot of other reports working fine when exported to pdf
The only connection we were able to make is related to the amount of data
selected to generate the report...
So I'm guessing it could be related to timeout settings, so I tried changing
in
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\RSReportServer.config the following keys :
<Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
nothing changed
<Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to 720 -
nothing changed
I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\web.config
the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
value looks big enough...
The configuration is as follows :
win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
We need a solution to this problem, because our whole application is based
on these reports, and if the reports fail to generate PDFs for larger sets
of data, then I can say our work was quite useless...:(
I appreciate any advice that could point us in the right direction !
Thanks,
Andrei.
I also tried running the report from the RS interface
(http://localhost/Reports). It generates the html view for the faulty
report, but when it comes to export to PDF format, the same error message
pops up.
Note : if I try to export the report to xml or csv, the operation completes
successfuly.
What could be the problem ? Please help !We did a lot of work in SP2 of Reporting Services to improve rendering. I
would suggest installing Service Pack 2 of Reporting Services and trying
this again.
If it continues to be a problem, then contact Microsoft PSS. If it is
indeed a bug, which it sounds like it is, all fees will be reimbursed.
--
| From: "andrei" <andrei.toma@.era-environmental.com>
| Subject: Export to PDF - crashing for larger sets of data
| Date: Thu, 29 Sep 2005 09:26:31 -0400
| Lines: 83
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
| Message-ID: <OSdxGqPxFHA.1132@.TK2MSFTNGP10.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: modemcable233.195-200-24.mc.videotron.ca 24.200.195.233
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:53351
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| Hi Group,
|
| I posted this problem two days ago, but it went unanswered, so here I am,
| giving it another try - it's really important for us !
| Reformulation :
|
| We have a report that we can run in ReportManager. It takes about 15-20
| second to generate, but it displays the html on the screen.
| It lets us navigate to the last page and back without any problem.
|
| The problem comes when we try to export this report to PDF format : once I
| click the export link, it waits for 60 to 90 seconds, then it displays the
| error message :
| *************************************************************
| Server Application Unavailable
| The web application you are attempting to access on this web server is
| currently unavailable. Please hit the "Refresh" button in your web
browser
| to retry your request.
|
| Administrator Note: An error message detailing the cause of this specific
| request failure can be found in the application event log of the web
server.
| Please review this log entry to discover what caused this error to occur.
| ***************************************************************
|
| Other information :
| - the same report, for smaller amounts of data, works fine when exported
to
| pdf.
| - the same report, when exported to either XML or CSV, works fine - the
| files are created.
| - we have a lot of other reports working fine when exported to pdf
|
| The only connection we were able to make is related to the amount of data
| selected to generate the report...
|
| So I'm guessing it could be related to timeout settings, so I tried
changing
| in
| C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
| Services\ReportServer\RSReportServer.config the following keys :
| <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
| nothing changed
| <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to 720
-
| nothing changed
|
| I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
| Services\ReportServer\web.config
| the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
| value looks big enough...
|
| The configuration is as follows :
| win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
|
| We need a solution to this problem, because our whole application is based
| on these reports, and if the reports fail to generate PDFs for larger sets
| of data, then I can say our work was quite useless...:(
|
| I appreciate any advice that could point us in the right direction !
|
| Thanks,
|
| Andrei.
|
|
|
|
|
|
|
|
|
| I also tried running the report from the RS interface
| (http://localhost/Reports). It generates the html view for the faulty
| report, but when it comes to export to PDF format, the same error message
| pops up.
|
| Note : if I try to export the report to xml or csv, the operation
completes
| successfuly.
|
| What could be the problem ? Please help !
|
|
|
|
|
||||We are having EXACTLY the same problem!
Questions:
1) did you upgrade to SP2?
2) did it solve your problem (sure hope so)
Thanks so much!
Al
"andrei" wrote:
> Hi Group,
> I posted this problem two days ago, but it went unanswered, so here I am,
> giving it another try - it's really important for us !
> Reformulation :
> We have a report that we can run in ReportManager. It takes about 15-20
> second to generate, but it displays the html on the screen.
> It lets us navigate to the last page and back without any problem.
> The problem comes when we try to export this report to PDF format : once I
> click the export link, it waits for 60 to 90 seconds, then it displays the
> error message :
> *************************************************************
> Server Application Unavailable
> The web application you are attempting to access on this web server is
> currently unavailable. Please hit the "Refresh" button in your web browser
> to retry your request.
> Administrator Note: An error message detailing the cause of this specific
> request failure can be found in the application event log of the web server.
> Please review this log entry to discover what caused this error to occur.
> ***************************************************************
> Other information :
> - the same report, for smaller amounts of data, works fine when exported to
> pdf.
> - the same report, when exported to either XML or CSV, works fine - the
> files are created.
> - we have a lot of other reports working fine when exported to pdf
> The only connection we were able to make is related to the amount of data
> selected to generate the report...
> So I'm guessing it could be related to timeout settings, so I tried changing
> in
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\RSReportServer.config the following keys :
> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
> nothing changed
> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to 720 -
> nothing changed
> I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\web.config
> the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
> value looks big enough...
> The configuration is as follows :
> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
> We need a solution to this problem, because our whole application is based
> on these reports, and if the reports fail to generate PDFs for larger sets
> of data, then I can say our work was quite useless...:(
> I appreciate any advice that could point us in the right direction !
> Thanks,
> Andrei.
>
>
>
>
> I also tried running the report from the RS interface
> (http://localhost/Reports). It generates the html view for the faulty
> report, but when it comes to export to PDF format, the same error message
> pops up.
> Note : if I try to export the report to xml or csv, the operation completes
> successfuly.
> What could be the problem ? Please help !
>
>
>|||This has to do with some timeout settings on the web server. Rendering to
PDF takes much longer than HTML. 20 seconds with HTML could take minutes
with PDF (Depends on the number of rows, the complexity etc). I think it
might be the web server itself, not a RS configuration.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Al Sherman" <Al Sherman@.discussions.microsoft.com> wrote in message
news:44A9AA81-DE65-44F5-85A7-3A266DCCA248@.microsoft.com...
> We are having EXACTLY the same problem!
> Questions:
> 1) did you upgrade to SP2?
> 2) did it solve your problem (sure hope so)
> Thanks so much!
> Al
> "andrei" wrote:
>> Hi Group,
>> I posted this problem two days ago, but it went unanswered, so here I am,
>> giving it another try - it's really important for us !
>> Reformulation :
>> We have a report that we can run in ReportManager. It takes about 15-20
>> second to generate, but it displays the html on the screen.
>> It lets us navigate to the last page and back without any problem.
>> The problem comes when we try to export this report to PDF format : once
>> I
>> click the export link, it waits for 60 to 90 seconds, then it displays
>> the
>> error message :
>> *************************************************************
>> Server Application Unavailable
>> The web application you are attempting to access on this web server is
>> currently unavailable. Please hit the "Refresh" button in your web
>> browser
>> to retry your request.
>> Administrator Note: An error message detailing the cause of this specific
>> request failure can be found in the application event log of the web
>> server.
>> Please review this log entry to discover what caused this error to occur.
>> ***************************************************************
>> Other information :
>> - the same report, for smaller amounts of data, works fine when exported
>> to
>> pdf.
>> - the same report, when exported to either XML or CSV, works fine - the
>> files are created.
>> - we have a lot of other reports working fine when exported to pdf
>> The only connection we were able to make is related to the amount of data
>> selected to generate the report...
>> So I'm guessing it could be related to timeout settings, so I tried
>> changing
>> in
>> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\ReportServer\RSReportServer.config the following keys :
>> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
>> nothing changed
>> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to
>> -
>> nothing changed
>> I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\ReportServer\web.config
>> the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
>> value looks big enough...
>> The configuration is as follows :
>> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
>> We need a solution to this problem, because our whole application is
>> based
>> on these reports, and if the reports fail to generate PDFs for larger
>> sets
>> of data, then I can say our work was quite useless...:(
>> I appreciate any advice that could point us in the right direction !
>> Thanks,
>> Andrei.
>>
>>
>>
>>
>> I also tried running the report from the RS interface
>> (http://localhost/Reports). It generates the html view for the faulty
>> report, but when it comes to export to PDF format, the same error message
>> pops up.
>> Note : if I try to export the report to xml or csv, the operation
>> completes
>> successfuly.
>> What could be the problem ? Please help !
>>
>>
>>|||Thanks,
Any idea which settings to try?
Sometimes even the large sets complete OK, but usually not.
"Bruce L-C [MVP]" wrote:
> This has to do with some timeout settings on the web server. Rendering to
> PDF takes much longer than HTML. 20 seconds with HTML could take minutes
> with PDF (Depends on the number of rows, the complexity etc). I think it
> might be the web server itself, not a RS configuration.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Al Sherman" <Al Sherman@.discussions.microsoft.com> wrote in message
> news:44A9AA81-DE65-44F5-85A7-3A266DCCA248@.microsoft.com...
> > We are having EXACTLY the same problem!
> >
> > Questions:
> > 1) did you upgrade to SP2?
> > 2) did it solve your problem (sure hope so)
> >
> > Thanks so much!
> >
> > Al
> >
> > "andrei" wrote:
> >
> >> Hi Group,
> >>
> >> I posted this problem two days ago, but it went unanswered, so here I am,
> >> giving it another try - it's really important for us !
> >> Reformulation :
> >>
> >> We have a report that we can run in ReportManager. It takes about 15-20
> >> second to generate, but it displays the html on the screen.
> >> It lets us navigate to the last page and back without any problem.
> >>
> >> The problem comes when we try to export this report to PDF format : once
> >> I
> >> click the export link, it waits for 60 to 90 seconds, then it displays
> >> the
> >> error message :
> >> *************************************************************
> >> Server Application Unavailable
> >> The web application you are attempting to access on this web server is
> >> currently unavailable. Please hit the "Refresh" button in your web
> >> browser
> >> to retry your request.
> >>
> >> Administrator Note: An error message detailing the cause of this specific
> >> request failure can be found in the application event log of the web
> >> server.
> >> Please review this log entry to discover what caused this error to occur.
> >> ***************************************************************
> >>
> >> Other information :
> >> - the same report, for smaller amounts of data, works fine when exported
> >> to
> >> pdf.
> >> - the same report, when exported to either XML or CSV, works fine - the
> >> files are created.
> >> - we have a lot of other reports working fine when exported to pdf
> >>
> >> The only connection we were able to make is related to the amount of data
> >> selected to generate the report...
> >>
> >> So I'm guessing it could be related to timeout settings, so I tried
> >> changing
> >> in
> >> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> >> Services\ReportServer\RSReportServer.config the following keys :
> >> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
> >> nothing changed
> >> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to
> >> -
> >> nothing changed
> >>
> >> I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> >> Services\ReportServer\web.config
> >> the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
> >> value looks big enough...
> >>
> >> The configuration is as follows :
> >> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
> >>
> >> We need a solution to this problem, because our whole application is
> >> based
> >> on these reports, and if the reports fail to generate PDFs for larger
> >> sets
> >> of data, then I can say our work was quite useless...:(
> >>
> >> I appreciate any advice that could point us in the right direction !
> >>
> >> Thanks,
> >>
> >> Andrei.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> I also tried running the report from the RS interface
> >> (http://localhost/Reports). It generates the html view for the faulty
> >> report, but when it comes to export to PDF format, the same error message
> >> pops up.
> >>
> >> Note : if I try to export the report to xml or csv, the operation
> >> completes
> >> successfuly.
> >>
> >> What could be the problem ? Please help !
> >>
> >>
> >>
> >>
> >>
> >>
>
>|||I see that you are on 2000 which I assume is IIS 5? I am on 2003 which is
IIS 6 so how you do things is totally different. Sorry,
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Al Sherman" <AlSherman@.discussions.microsoft.com> wrote in message
news:80482824-1EFA-4C14-9823-91648365607E@.microsoft.com...
> Thanks,
> Any idea which settings to try?
> Sometimes even the large sets complete OK, but usually not.
> "Bruce L-C [MVP]" wrote:
>> This has to do with some timeout settings on the web server. Rendering to
>> PDF takes much longer than HTML. 20 seconds with HTML could take minutes
>> with PDF (Depends on the number of rows, the complexity etc). I think it
>> might be the web server itself, not a RS configuration.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Al Sherman" <Al Sherman@.discussions.microsoft.com> wrote in message
>> news:44A9AA81-DE65-44F5-85A7-3A266DCCA248@.microsoft.com...
>> > We are having EXACTLY the same problem!
>> >
>> > Questions:
>> > 1) did you upgrade to SP2?
>> > 2) did it solve your problem (sure hope so)
>> >
>> > Thanks so much!
>> >
>> > Al
>> >
>> > "andrei" wrote:
>> >
>> >> Hi Group,
>> >>
>> >> I posted this problem two days ago, but it went unanswered, so here I
>> >> am,
>> >> giving it another try - it's really important for us !
>> >> Reformulation :
>> >>
>> >> We have a report that we can run in ReportManager. It takes about
>> >> 15-20
>> >> second to generate, but it displays the html on the screen.
>> >> It lets us navigate to the last page and back without any problem.
>> >>
>> >> The problem comes when we try to export this report to PDF format :
>> >> once
>> >> I
>> >> click the export link, it waits for 60 to 90 seconds, then it displays
>> >> the
>> >> error message :
>> >> *************************************************************
>> >> Server Application Unavailable
>> >> The web application you are attempting to access on this web server is
>> >> currently unavailable. Please hit the "Refresh" button in your web
>> >> browser
>> >> to retry your request.
>> >>
>> >> Administrator Note: An error message detailing the cause of this
>> >> specific
>> >> request failure can be found in the application event log of the web
>> >> server.
>> >> Please review this log entry to discover what caused this error to
>> >> occur.
>> >> ***************************************************************
>> >>
>> >> Other information :
>> >> - the same report, for smaller amounts of data, works fine when
>> >> exported
>> >> to
>> >> pdf.
>> >> - the same report, when exported to either XML or CSV, works fine -
>> >> the
>> >> files are created.
>> >> - we have a lot of other reports working fine when exported to pdf
>> >>
>> >> The only connection we were able to make is related to the amount of
>> >> data
>> >> selected to generate the report...
>> >>
>> >> So I'm guessing it could be related to timeout settings, so I tried
>> >> changing
>> >> in
>> >> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> >> Services\ReportServer\RSReportServer.config the following keys :
>> >> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
>> >> nothing changed
>> >> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to
>> >> -
>> >> nothing changed
>> >>
>> >> I also checked in C:\Program Files\Microsoft SQL
>> >> Server\MSSQL\Reporting
>> >> Services\ReportServer\web.config
>> >> the key <httpRuntime executionTimeout = "9000" /> - didn't change it,
>> >> the
>> >> value looks big enough...
>> >>
>> >> The configuration is as follows :
>> >> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
>> >>
>> >> We need a solution to this problem, because our whole application is
>> >> based
>> >> on these reports, and if the reports fail to generate PDFs for larger
>> >> sets
>> >> of data, then I can say our work was quite useless...:(
>> >>
>> >> I appreciate any advice that could point us in the right direction !
>> >>
>> >> Thanks,
>> >>
>> >> Andrei.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> I also tried running the report from the RS interface
>> >> (http://localhost/Reports). It generates the html view for the faulty
>> >> report, but when it comes to export to PDF format, the same error
>> >> message
>> >> pops up.
>> >>
>> >> Note : if I try to export the report to xml or csv, the operation
>> >> completes
>> >> successfuly.
>> >>
>> >> What could be the problem ? Please help !
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>>|||Hi Bruce:
Actually, we are running on a 2003 system, which is running IIS 6
I'm going to give Brad's suggestion a shot and upgrade to SP2.
I'll post a message as to whether or not this solves the problem
Thanks,
Al
"Bruce L-C [MVP]" wrote:
> I see that you are on 2000 which I assume is IIS 5? I am on 2003 which is
> IIS 6 so how you do things is totally different. Sorry,
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Al Sherman" <AlSherman@.discussions.microsoft.com> wrote in message
> news:80482824-1EFA-4C14-9823-91648365607E@.microsoft.com...
> > Thanks,
> >
> > Any idea which settings to try?
> >
> > Sometimes even the large sets complete OK, but usually not.
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> This has to do with some timeout settings on the web server. Rendering to
> >> PDF takes much longer than HTML. 20 seconds with HTML could take minutes
> >> with PDF (Depends on the number of rows, the complexity etc). I think it
> >> might be the web server itself, not a RS configuration.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Al Sherman" <Al Sherman@.discussions.microsoft.com> wrote in message
> >> news:44A9AA81-DE65-44F5-85A7-3A266DCCA248@.microsoft.com...
> >> > We are having EXACTLY the same problem!
> >> >
> >> > Questions:
> >> > 1) did you upgrade to SP2?
> >> > 2) did it solve your problem (sure hope so)
> >> >
> >> > Thanks so much!
> >> >
> >> > Al
> >> >
> >> > "andrei" wrote:
> >> >
> >> >> Hi Group,
> >> >>
> >> >> I posted this problem two days ago, but it went unanswered, so here I
> >> >> am,
> >> >> giving it another try - it's really important for us !
> >> >> Reformulation :
> >> >>
> >> >> We have a report that we can run in ReportManager. It takes about
> >> >> 15-20
> >> >> second to generate, but it displays the html on the screen.
> >> >> It lets us navigate to the last page and back without any problem.
> >> >>
> >> >> The problem comes when we try to export this report to PDF format :
> >> >> once
> >> >> I
> >> >> click the export link, it waits for 60 to 90 seconds, then it displays
> >> >> the
> >> >> error message :
> >> >> *************************************************************
> >> >> Server Application Unavailable
> >> >> The web application you are attempting to access on this web server is
> >> >> currently unavailable. Please hit the "Refresh" button in your web
> >> >> browser
> >> >> to retry your request.
> >> >>
> >> >> Administrator Note: An error message detailing the cause of this
> >> >> specific
> >> >> request failure can be found in the application event log of the web
> >> >> server.
> >> >> Please review this log entry to discover what caused this error to
> >> >> occur.
> >> >> ***************************************************************
> >> >>
> >> >> Other information :
> >> >> - the same report, for smaller amounts of data, works fine when
> >> >> exported
> >> >> to
> >> >> pdf.
> >> >> - the same report, when exported to either XML or CSV, works fine -
> >> >> the
> >> >> files are created.
> >> >> - we have a lot of other reports working fine when exported to pdf
> >> >>
> >> >> The only connection we were able to make is related to the amount of
> >> >> data
> >> >> selected to generate the report...
> >> >>
> >> >> So I'm guessing it could be related to timeout settings, so I tried
> >> >> changing
> >> >> in
> >> >> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> >> >> Services\ReportServer\RSReportServer.config the following keys :
> >> >> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
> >> >> nothing changed
> >> >> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to
> >> >> -
> >> >> nothing changed
> >> >>
> >> >> I also checked in C:\Program Files\Microsoft SQL
> >> >> Server\MSSQL\Reporting
> >> >> Services\ReportServer\web.config
> >> >> the key <httpRuntime executionTimeout = "9000" /> - didn't change it,
> >> >> the
> >> >> value looks big enough...
> >> >>
> >> >> The configuration is as follows :
> >> >> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
> >> >>
> >> >> We need a solution to this problem, because our whole application is
> >> >> based
> >> >> on these reports, and if the reports fail to generate PDFs for larger
> >> >> sets
> >> >> of data, then I can say our work was quite useless...:(
> >> >>
> >> >> I appreciate any advice that could point us in the right direction !
> >> >>
> >> >> Thanks,
> >> >>
> >> >> Andrei.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> I also tried running the report from the RS interface
> >> >> (http://localhost/Reports). It generates the html view for the faulty
> >> >> report, but when it comes to export to PDF format, the same error
> >> >> message
> >> >> pops up.
> >> >>
> >> >> Note : if I try to export the report to xml or csv, the operation
> >> >> completes
> >> >> successfuly.
> >> >>
> >> >> What could be the problem ? Please help !
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Hi Brad:
We've experienced the exact same problem.
I upgraded SQL Server to SP4 and Reporting Services to SP2 and the problem
persists.
How can I contact MS PSS?
Thanks a bunch!
Al
""Brad Syputa - MS"" wrote:
> We did a lot of work in SP2 of Reporting Services to improve rendering. I
> would suggest installing Service Pack 2 of Reporting Services and trying
> this again.
> If it continues to be a problem, then contact Microsoft PSS. If it is
> indeed a bug, which it sounds like it is, all fees will be reimbursed.
> --
> | From: "andrei" <andrei.toma@.era-environmental.com>
> | Subject: Export to PDF - crashing for larger sets of data
> | Date: Thu, 29 Sep 2005 09:26:31 -0400
> | Lines: 83
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
> | Message-ID: <OSdxGqPxFHA.1132@.TK2MSFTNGP10.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | NNTP-Posting-Host: modemcable233.195-200-24.mc.videotron.ca 24.200.195.233
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:53351
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | Hi Group,
> |
> | I posted this problem two days ago, but it went unanswered, so here I am,
> | giving it another try - it's really important for us !
> | Reformulation :
> |
> | We have a report that we can run in ReportManager. It takes about 15-20
> | second to generate, but it displays the html on the screen.
> | It lets us navigate to the last page and back without any problem.
> |
> | The problem comes when we try to export this report to PDF format : once I
> | click the export link, it waits for 60 to 90 seconds, then it displays the
> | error message :
> | *************************************************************
> | Server Application Unavailable
> | The web application you are attempting to access on this web server is
> | currently unavailable. Please hit the "Refresh" button in your web
> browser
> | to retry your request.
> |
> | Administrator Note: An error message detailing the cause of this specific
> | request failure can be found in the application event log of the web
> server.
> | Please review this log entry to discover what caused this error to occur.
> | ***************************************************************
> |
> | Other information :
> | - the same report, for smaller amounts of data, works fine when exported
> to
> | pdf.
> | - the same report, when exported to either XML or CSV, works fine - the
> | files are created.
> | - we have a lot of other reports working fine when exported to pdf
> |
> | The only connection we were able to make is related to the amount of data
> | selected to generate the report...
> |
> | So I'm guessing it could be related to timeout settings, so I tried
> changing
> | in
> | C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> | Services\ReportServer\RSReportServer.config the following keys :
> | <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
> | nothing changed
> | <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to 720
> -
> | nothing changed
> |
> | I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> | Services\ReportServer\web.config
> | the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
> | value looks big enough...
> |
> | The configuration is as follows :
> | win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
> |
> | We need a solution to this problem, because our whole application is based
> | on these reports, and if the reports fail to generate PDFs for larger sets
> | of data, then I can say our work was quite useless...:(
> |
> | I appreciate any advice that could point us in the right direction !
> |
> | Thanks,
> |
> | Andrei.
> |
> |
> |
> |
> |
> |
> |
> |
> |
> | I also tried running the report from the RS interface
> | (http://localhost/Reports). It generates the html view for the faulty
> | report, but when it comes to export to PDF format, the same error message
> | pops up.
> |
> | Note : if I try to export the report to xml or csv, the operation
> completes
> | successfuly.
> |
> | What could be the problem ? Please help !
> |
> |
> |
> |
> |
> |
>|||Hi Andrei:
We had a problem that sounded exactly the same.
Our report was using a Table Control with multiple "groups" to implement a
report with multiple output lines per result-set row.
I solved the problem by revising the report to use a List Control instead.
I'd appreciate knowing the answers to the following questions:
1) Was your report also using a Table Control?
2) Did it have multiple Groups?
Thanks,
Al
"andrei" wrote:
> Hi Group,
> I posted this problem two days ago, but it went unanswered, so here I am,
> giving it another try - it's really important for us !
> Reformulation :
> We have a report that we can run in ReportManager. It takes about 15-20
> second to generate, but it displays the html on the screen.
> It lets us navigate to the last page and back without any problem.
> The problem comes when we try to export this report to PDF format : once I
> click the export link, it waits for 60 to 90 seconds, then it displays the
> error message :
> *************************************************************
> Server Application Unavailable
> The web application you are attempting to access on this web server is
> currently unavailable. Please hit the "Refresh" button in your web browser
> to retry your request.
> Administrator Note: An error message detailing the cause of this specific
> request failure can be found in the application event log of the web server.
> Please review this log entry to discover what caused this error to occur.
> ***************************************************************
> Other information :
> - the same report, for smaller amounts of data, works fine when exported to
> pdf.
> - the same report, when exported to either XML or CSV, works fine - the
> files are created.
> - we have a lot of other reports working fine when exported to pdf
> The only connection we were able to make is related to the amount of data
> selected to generate the report...
> So I'm guessing it could be related to timeout settings, so I tried changing
> in
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\RSReportServer.config the following keys :
> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
> nothing changed
> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to 720 -
> nothing changed
> I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\web.config
> the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
> value looks big enough...
> The configuration is as follows :
> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
> We need a solution to this problem, because our whole application is based
> on these reports, and if the reports fail to generate PDFs for larger sets
> of data, then I can say our work was quite useless...:(
> I appreciate any advice that could point us in the right direction !
> Thanks,
> Andrei.
>
>
>
>
> I also tried running the report from the RS interface
> (http://localhost/Reports). It generates the html view for the faulty
> report, but when it comes to export to PDF format, the same error message
> pops up.
> Note : if I try to export the report to xml or csv, the operation completes
> successfuly.
> What could be the problem ? Please help !
>
>
>|||I had the exact same problem. For me, the problem was caused by ASP.Net
process recycling options. There is a setting in ASP.Net (under which RS
runs) that controls when a web application is assumed to be performing badly
and hogging too much memory. Once this threshold is reached, ASP.Net kills
the web app and starts a new one - existing requests are left dangling and
IIS returns the "Server Application Unavailable" message.
PDF export consumes large amounts of memory - the rendering is done in
memory. If the report is large, this process recycling limit can be reached.
It is expressed as a percentage of total physical memory. You can find the
setting in <windir>\Microsoft.Net\Framework\v1.14322\config.machine.config.
Look for the "processModel" element's "memoryLimit" attribute. By default it
is "60" - this indicates that the ASP.Net process (which includes RS) will be
recycled when it takes up 60% of the physical memory.
In order to avoid your problem, here are your choices:
1. up this setting
2. Install more memory
"andrei" wrote:
> Hi Group,
> I posted this problem two days ago, but it went unanswered, so here I am,
> giving it another try - it's really important for us !
> Reformulation :
> We have a report that we can run in ReportManager. It takes about 15-20
> second to generate, but it displays the html on the screen.
> It lets us navigate to the last page and back without any problem.
> The problem comes when we try to export this report to PDF format : once I
> click the export link, it waits for 60 to 90 seconds, then it displays the
> error message :
> *************************************************************
> Server Application Unavailable
> The web application you are attempting to access on this web server is
> currently unavailable. Please hit the "Refresh" button in your web browser
> to retry your request.
> Administrator Note: An error message detailing the cause of this specific
> request failure can be found in the application event log of the web server.
> Please review this log entry to discover what caused this error to occur.
> ***************************************************************
> Other information :
> - the same report, for smaller amounts of data, works fine when exported to
> pdf.
> - the same report, when exported to either XML or CSV, works fine - the
> files are created.
> - we have a lot of other reports working fine when exported to pdf
> The only connection we were able to make is related to the amount of data
> selected to generate the report...
> So I'm guessing it could be related to timeout settings, so I tried changing
> in
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\RSReportServer.config the following keys :
> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
> nothing changed
> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to 720 -
> nothing changed
> I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\web.config
> the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
> value looks big enough...
> The configuration is as follows :
> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
> We need a solution to this problem, because our whole application is based
> on these reports, and if the reports fail to generate PDFs for larger sets
> of data, then I can say our work was quite useless...:(
> I appreciate any advice that could point us in the right direction !
> Thanks,
> Andrei.
>
>
>
>
> I also tried running the report from the RS interface
> (http://localhost/Reports). It generates the html view for the faulty
> report, but when it comes to export to PDF format, the same error message
> pops up.
> Note : if I try to export the report to xml or csv, the operation completes
> successfuly.
> What could be the problem ? Please help !
>
>
>|||This is great information. Thanks for sharing. I have saved your response to
provide to others in the newsgroup at a later date.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Billy Boy" <billyboyo_laptio@.hotmail.com_no_spam> wrote in message
news:CB2112AB-801E-4008-9EF1-60B7FB1C74C5@.microsoft.com...
>I had the exact same problem. For me, the problem was caused by ASP.Net
> process recycling options. There is a setting in ASP.Net (under which RS
> runs) that controls when a web application is assumed to be performing
> badly
> and hogging too much memory. Once this threshold is reached, ASP.Net kills
> the web app and starts a new one - existing requests are left dangling and
> IIS returns the "Server Application Unavailable" message.
> PDF export consumes large amounts of memory - the rendering is done in
> memory. If the report is large, this process recycling limit can be
> reached.
> It is expressed as a percentage of total physical memory. You can find the
> setting in
> <windir>\Microsoft.Net\Framework\v1.14322\config.machine.config.
> Look for the "processModel" element's "memoryLimit" attribute. By default
> it
> is "60" - this indicates that the ASP.Net process (which includes RS) will
> be
> recycled when it takes up 60% of the physical memory.
> In order to avoid your problem, here are your choices:
> 1. up this setting
> 2. Install more memory
> "andrei" wrote:
>> Hi Group,
>> I posted this problem two days ago, but it went unanswered, so here I am,
>> giving it another try - it's really important for us !
>> Reformulation :
>> We have a report that we can run in ReportManager. It takes about 15-20
>> second to generate, but it displays the html on the screen.
>> It lets us navigate to the last page and back without any problem.
>> The problem comes when we try to export this report to PDF format : once
>> I
>> click the export link, it waits for 60 to 90 seconds, then it displays
>> the
>> error message :
>> *************************************************************
>> Server Application Unavailable
>> The web application you are attempting to access on this web server is
>> currently unavailable. Please hit the "Refresh" button in your web
>> browser
>> to retry your request.
>> Administrator Note: An error message detailing the cause of this specific
>> request failure can be found in the application event log of the web
>> server.
>> Please review this log entry to discover what caused this error to occur.
>> ***************************************************************
>> Other information :
>> - the same report, for smaller amounts of data, works fine when exported
>> to
>> pdf.
>> - the same report, when exported to either XML or CSV, works fine - the
>> files are created.
>> - we have a lot of other reports working fine when exported to pdf
>> The only connection we were able to make is related to the amount of data
>> selected to generate the report...
>> So I'm guessing it could be related to timeout settings, so I tried
>> changing
>> in
>> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\ReportServer\RSReportServer.config the following keys :
>> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
>> nothing changed
>> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to
>> -
>> nothing changed
>> I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\ReportServer\web.config
>> the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
>> value looks big enough...
>> The configuration is as follows :
>> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
>> We need a solution to this problem, because our whole application is
>> based
>> on these reports, and if the reports fail to generate PDFs for larger
>> sets
>> of data, then I can say our work was quite useless...:(
>> I appreciate any advice that could point us in the right direction !
>> Thanks,
>> Andrei.
>>
>>
>>
>>
>> I also tried running the report from the RS interface
>> (http://localhost/Reports). It generates the html view for the faulty
>> report, but when it comes to export to PDF format, the same error message
>> pops up.
>> Note : if I try to export the report to xml or csv, the operation
>> completes
>> successfuly.
>> What could be the problem ? Please help !
>>
>>
>>