Report Error when 2 pages for multiple records

We have a web app, built in .Net, with reporting services as our reporting
tool. The problem we are having is when we have a report that goes to
numerous people and the report is 2 pages long. When we make it 1 page,
legal size, it works fine (avg records are 500-900). When this report is
generated it is created in a pdf format. I can run it on report services
manager and in the viewer it takes approx 10 secs or less to run and render,
but when we create the pdf it spikes the processor up to 90% and if it's a 2
page report it generates an error.PDF's take significantly longer than HTML but it surprises me that a 2 page
report you see much of a difference. Do you have any service packs
installed. If not, my advice is to install SP2.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
news:BBA2388F-E062-4368-987A-62CD9298BD14@.microsoft.com...
> We have a web app, built in .Net, with reporting services as our reporting
> tool. The problem we are having is when we have a report that goes to
> numerous people and the report is 2 pages long. When we make it 1 page,
> legal size, it works fine (avg records are 500-900). When this report is
> generated it is created in a pdf format. I can run it on report services
> manager and in the viewer it takes approx 10 secs or less to run and
> render,
> but when we create the pdf it spikes the processor up to 90% and if it's a
> 2
> page report it generates an error.|||I have all of the service packs installed. This is a 2 page report that
generates approx 950 pages. I have similar reports, but set to legal single
page, that generate over 1000 pages in pdf. The error message I get is:
"Server Error in '/' Application.
The underlying connection was closed: An unexpected error occurred on a
receive.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Net.WebException: The underlying connection was
closed: An unexpected error occurred on a receive.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[WebException: The underlying connection was closed: An unexpected error
occurred on a receive.]
System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebReques
t request) +58
System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRe
quest request) +5
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) +183
LAMS.SQLReportServer.ReportingService.Render(String Report, String
Format, String HistoryID, String DeviceInfo, ParameterValue[] Parameters,
DataSourceCredentials[] Credentials, String ShowHideToggle, String& Encoding,
String& MimeType, ParameterValue[]& ParametersUsed, Warning[]& Warnings,
String[]& StreamIds) +141
LAMS.ReportViewer.RenderPDFReport() +618
LAMS.ReportViewer.Page_Load(Object sender, EventArgs e) +88
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +750"
"Bruce L-C [MVP]" wrote:
> PDF's take significantly longer than HTML but it surprises me that a 2 page
> report you see much of a difference. Do you have any service packs
> installed. If not, my advice is to install SP2.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
> news:BBA2388F-E062-4368-987A-62CD9298BD14@.microsoft.com...
> > We have a web app, built in .Net, with reporting services as our reporting
> > tool. The problem we are having is when we have a report that goes to
> > numerous people and the report is 2 pages long. When we make it 1 page,
> > legal size, it works fine (avg records are 500-900). When this report is
> > generated it is created in a pdf format. I can run it on report services
> > manager and in the viewer it takes approx 10 secs or less to run and
> > render,
> > but when we create the pdf it spikes the processor up to 90% and if it's a
> > 2
> > page report it generates an error.
>
>|||OK, we had a failure to communicate. You said a 2 page report and I thought
it was 2 pages long. You mean 2 pages per record.
RS renders everything in RAM. Formats make a big difference in CPU
utilizations. CSV, HTML are very fast. PDF and Excel are much slower and
much much more intensive in resources required. My personal feeling is that
when you are talking about that many pages it is an inappropriate use of RS.
It is just not designed to be outputting 1000 pages of PDF. Users cannot
look at that many pages anyway. You should consider drill through technique.
Show the users what they need to see. I do know that sometimes users need to
pull data into another program but that is not what PDF format is used for.
Excel is another matter (although Excel can't handle 100,000 rows either).
For Excel you could use CSV to get around this. For PDF there is no work
around. More RAM helps but you really are overloading the server when you
are doing this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
news:790D7C48-1AB7-4F2A-A1C3-A1CF679B9B52@.microsoft.com...
>I have all of the service packs installed. This is a 2 page report that
> generates approx 950 pages. I have similar reports, but set to legal
> single
> page, that generate over 1000 pages in pdf. The error message I get is:
> "Server Error in '/' Application.
> The underlying connection was closed: An unexpected error occurred on a
> receive.
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about
> the error and where it originated in the code.
> Exception Details: System.Net.WebException: The underlying connection was
> closed: An unexpected error occurred on a receive.
> Source Error:
> An unhandled exception was generated during the execution of the current
> web
> request. Information regarding the origin and location of the exception
> can
> be identified using the exception stack trace below.
> Stack Trace:
> [WebException: The underlying connection was closed: An unexpected error
> occurred on a receive.]
> System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebReques
> t request) +58
> System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRe
> quest request) +5
> System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters) +183
> LAMS.SQLReportServer.ReportingService.Render(String Report, String
> Format, String HistoryID, String DeviceInfo, ParameterValue[] Parameters,
> DataSourceCredentials[] Credentials, String ShowHideToggle, String&
> Encoding,
> String& MimeType, ParameterValue[]& ParametersUsed, Warning[]& Warnings,
> String[]& StreamIds) +141
> LAMS.ReportViewer.RenderPDFReport() +618
> LAMS.ReportViewer.Page_Load(Object sender, EventArgs e) +88
> System.Web.UI.Control.OnLoad(EventArgs e) +67
> System.Web.UI.Control.LoadRecursive() +35
> System.Web.UI.Page.ProcessRequestMain() +750"
> "Bruce L-C [MVP]" wrote:
>> PDF's take significantly longer than HTML but it surprises me that a 2
>> page
>> report you see much of a difference. Do you have any service packs
>> installed. If not, my advice is to install SP2.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
>> news:BBA2388F-E062-4368-987A-62CD9298BD14@.microsoft.com...
>> > We have a web app, built in .Net, with reporting services as our
>> > reporting
>> > tool. The problem we are having is when we have a report that goes to
>> > numerous people and the report is 2 pages long. When we make it 1
>> > page,
>> > legal size, it works fine (avg records are 500-900). When this report
>> > is
>> > generated it is created in a pdf format. I can run it on report
>> > services
>> > manager and in the viewer it takes approx 10 secs or less to run and
>> > render,
>> > but when we create the pdf it spikes the processor up to 90% and if
>> > it's a
>> > 2
>> > page report it generates an error.
>>|||Thanks for the input. The only problem is this is our leasing application
and we have to print mass batch of renewals once a year. I am thinking of
setting it on a schedule but that would remove a data range filter that is in
place and is changable by the user. Any suggestions?
"Bruce L-C [MVP]" wrote:
> OK, we had a failure to communicate. You said a 2 page report and I thought
> it was 2 pages long. You mean 2 pages per record.
> RS renders everything in RAM. Formats make a big difference in CPU
> utilizations. CSV, HTML are very fast. PDF and Excel are much slower and
> much much more intensive in resources required. My personal feeling is that
> when you are talking about that many pages it is an inappropriate use of RS.
> It is just not designed to be outputting 1000 pages of PDF. Users cannot
> look at that many pages anyway. You should consider drill through technique.
> Show the users what they need to see. I do know that sometimes users need to
> pull data into another program but that is not what PDF format is used for.
> Excel is another matter (although Excel can't handle 100,000 rows either).
> For Excel you could use CSV to get around this. For PDF there is no work
> around. More RAM helps but you really are overloading the server when you
> are doing this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
> news:790D7C48-1AB7-4F2A-A1C3-A1CF679B9B52@.microsoft.com...
> >I have all of the service packs installed. This is a 2 page report that
> > generates approx 950 pages. I have similar reports, but set to legal
> > single
> > page, that generate over 1000 pages in pdf. The error message I get is:
> >
> > "Server Error in '/' Application.
> > The underlying connection was closed: An unexpected error occurred on a
> > receive.
> > Description: An unhandled exception occurred during the execution of the
> > current web request. Please review the stack trace for more information
> > about
> > the error and where it originated in the code.
> > Exception Details: System.Net.WebException: The underlying connection was
> > closed: An unexpected error occurred on a receive.
> > Source Error:
> > An unhandled exception was generated during the execution of the current
> > web
> > request. Information regarding the origin and location of the exception
> > can
> > be identified using the exception stack trace below.
> >
> > Stack Trace:
> > [WebException: The underlying connection was closed: An unexpected error
> > occurred on a receive.]
> > System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebReques
> > t request) +58
> > System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRe
> > quest request) +5
> > System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > methodName, Object[] parameters) +183
> > LAMS.SQLReportServer.ReportingService.Render(String Report, String
> > Format, String HistoryID, String DeviceInfo, ParameterValue[] Parameters,
> > DataSourceCredentials[] Credentials, String ShowHideToggle, String&
> > Encoding,
> > String& MimeType, ParameterValue[]& ParametersUsed, Warning[]& Warnings,
> > String[]& StreamIds) +141
> > LAMS.ReportViewer.RenderPDFReport() +618
> > LAMS.ReportViewer.Page_Load(Object sender, EventArgs e) +88
> > System.Web.UI.Control.OnLoad(EventArgs e) +67
> > System.Web.UI.Control.LoadRecursive() +35
> > System.Web.UI.Page.ProcessRequestMain() +750"
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> PDF's take significantly longer than HTML but it surprises me that a 2
> >> page
> >> report you see much of a difference. Do you have any service packs
> >> installed. If not, my advice is to install SP2.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
> >> news:BBA2388F-E062-4368-987A-62CD9298BD14@.microsoft.com...
> >> > We have a web app, built in .Net, with reporting services as our
> >> > reporting
> >> > tool. The problem we are having is when we have a report that goes to
> >> > numerous people and the report is 2 pages long. When we make it 1
> >> > page,
> >> > legal size, it works fine (avg records are 500-900). When this report
> >> > is
> >> > generated it is created in a pdf format. I can run it on report
> >> > services
> >> > manager and in the viewer it takes approx 10 secs or less to run and
> >> > render,
> >> > but when we create the pdf it spikes the processor up to 90% and if
> >> > it's a
> >> > 2
> >> > page report it generates an error.
> >>
> >>
> >>
>
>|||If you can have parameters that allows you to do a subset then schedule the
report multiple times just varying the parameter and print say 100 pages at
a time.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
news:6B4C566B-C41C-49FD-BF58-2FCD7B9656E3@.microsoft.com...
> Thanks for the input. The only problem is this is our leasing application
> and we have to print mass batch of renewals once a year. I am thinking of
> setting it on a schedule but that would remove a data range filter that is
> in
> place and is changable by the user. Any suggestions?
> "Bruce L-C [MVP]" wrote:
>> OK, we had a failure to communicate. You said a 2 page report and I
>> thought
>> it was 2 pages long. You mean 2 pages per record.
>> RS renders everything in RAM. Formats make a big difference in CPU
>> utilizations. CSV, HTML are very fast. PDF and Excel are much slower and
>> much much more intensive in resources required. My personal feeling is
>> that
>> when you are talking about that many pages it is an inappropriate use of
>> RS.
>> It is just not designed to be outputting 1000 pages of PDF. Users cannot
>> look at that many pages anyway. You should consider drill through
>> technique.
>> Show the users what they need to see. I do know that sometimes users need
>> to
>> pull data into another program but that is not what PDF format is used
>> for.
>> Excel is another matter (although Excel can't handle 100,000 rows
>> either).
>> For Excel you could use CSV to get around this. For PDF there is no work
>> around. More RAM helps but you really are overloading the server when you
>> are doing this.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
>> news:790D7C48-1AB7-4F2A-A1C3-A1CF679B9B52@.microsoft.com...
>> >I have all of the service packs installed. This is a 2 page report that
>> > generates approx 950 pages. I have similar reports, but set to legal
>> > single
>> > page, that generate over 1000 pages in pdf. The error message I get
>> > is:
>> >
>> > "Server Error in '/' Application.
>> > The underlying connection was closed: An unexpected error occurred on a
>> > receive.
>> > Description: An unhandled exception occurred during the execution of
>> > the
>> > current web request. Please review the stack trace for more information
>> > about
>> > the error and where it originated in the code.
>> > Exception Details: System.Net.WebException: The underlying connection
>> > was
>> > closed: An unexpected error occurred on a receive.
>> > Source Error:
>> > An unhandled exception was generated during the execution of the
>> > current
>> > web
>> > request. Information regarding the origin and location of the exception
>> > can
>> > be identified using the exception stack trace below.
>> >
>> > Stack Trace:
>> > [WebException: The underlying connection was closed: An unexpected
>> > error
>> > occurred on a receive.]
>> > System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebReques
>> > t request) +58
>> > System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRe
>> > quest request) +5
>> > System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
>> > methodName, Object[] parameters) +183
>> > LAMS.SQLReportServer.ReportingService.Render(String Report, String
>> > Format, String HistoryID, String DeviceInfo, ParameterValue[]
>> > Parameters,
>> > DataSourceCredentials[] Credentials, String ShowHideToggle, String&
>> > Encoding,
>> > String& MimeType, ParameterValue[]& ParametersUsed, Warning[]&
>> > Warnings,
>> > String[]& StreamIds) +141
>> > LAMS.ReportViewer.RenderPDFReport() +618
>> > LAMS.ReportViewer.Page_Load(Object sender, EventArgs e) +88
>> > System.Web.UI.Control.OnLoad(EventArgs e) +67
>> > System.Web.UI.Control.LoadRecursive() +35
>> > System.Web.UI.Page.ProcessRequestMain() +750"
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> PDF's take significantly longer than HTML but it surprises me that a 2
>> >> page
>> >> report you see much of a difference. Do you have any service packs
>> >> installed. If not, my advice is to install SP2.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
>> >> news:BBA2388F-E062-4368-987A-62CD9298BD14@.microsoft.com...
>> >> > We have a web app, built in .Net, with reporting services as our
>> >> > reporting
>> >> > tool. The problem we are having is when we have a report that goes
>> >> > to
>> >> > numerous people and the report is 2 pages long. When we make it 1
>> >> > page,
>> >> > legal size, it works fine (avg records are 500-900). When this
>> >> > report
>> >> > is
>> >> > generated it is created in a pdf format. I can run it on report
>> >> > services
>> >> > manager and in the viewer it takes approx 10 secs or less to run and
>> >> > render,
>> >> > but when we create the pdf it spikes the processor up to 90% and if
>> >> > it's a
>> >> > 2
>> >> > page report it generates an error.
>> >>
>> >>
>> >>
>>|||Thanks a bunch for the info Bruce.
"Bruce L-C [MVP]" wrote:
> If you can have parameters that allows you to do a subset then schedule the
> report multiple times just varying the parameter and print say 100 pages at
> a time.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
> news:6B4C566B-C41C-49FD-BF58-2FCD7B9656E3@.microsoft.com...
> > Thanks for the input. The only problem is this is our leasing application
> > and we have to print mass batch of renewals once a year. I am thinking of
> > setting it on a schedule but that would remove a data range filter that is
> > in
> > place and is changable by the user. Any suggestions?
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> OK, we had a failure to communicate. You said a 2 page report and I
> >> thought
> >> it was 2 pages long. You mean 2 pages per record.
> >>
> >> RS renders everything in RAM. Formats make a big difference in CPU
> >> utilizations. CSV, HTML are very fast. PDF and Excel are much slower and
> >> much much more intensive in resources required. My personal feeling is
> >> that
> >> when you are talking about that many pages it is an inappropriate use of
> >> RS.
> >> It is just not designed to be outputting 1000 pages of PDF. Users cannot
> >> look at that many pages anyway. You should consider drill through
> >> technique.
> >> Show the users what they need to see. I do know that sometimes users need
> >> to
> >> pull data into another program but that is not what PDF format is used
> >> for.
> >> Excel is another matter (although Excel can't handle 100,000 rows
> >> either).
> >> For Excel you could use CSV to get around this. For PDF there is no work
> >> around. More RAM helps but you really are overloading the server when you
> >> are doing this.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
> >> news:790D7C48-1AB7-4F2A-A1C3-A1CF679B9B52@.microsoft.com...
> >> >I have all of the service packs installed. This is a 2 page report that
> >> > generates approx 950 pages. I have similar reports, but set to legal
> >> > single
> >> > page, that generate over 1000 pages in pdf. The error message I get
> >> > is:
> >> >
> >> > "Server Error in '/' Application.
> >> > The underlying connection was closed: An unexpected error occurred on a
> >> > receive.
> >> > Description: An unhandled exception occurred during the execution of
> >> > the
> >> > current web request. Please review the stack trace for more information
> >> > about
> >> > the error and where it originated in the code.
> >> > Exception Details: System.Net.WebException: The underlying connection
> >> > was
> >> > closed: An unexpected error occurred on a receive.
> >> > Source Error:
> >> > An unhandled exception was generated during the execution of the
> >> > current
> >> > web
> >> > request. Information regarding the origin and location of the exception
> >> > can
> >> > be identified using the exception stack trace below.
> >> >
> >> > Stack Trace:
> >> > [WebException: The underlying connection was closed: An unexpected
> >> > error
> >> > occurred on a receive.]
> >> > System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebReques
> >> > t request) +58
> >> > System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRe
> >> > quest request) +5
> >> > System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> >> > methodName, Object[] parameters) +183
> >> > LAMS.SQLReportServer.ReportingService.Render(String Report, String
> >> > Format, String HistoryID, String DeviceInfo, ParameterValue[]
> >> > Parameters,
> >> > DataSourceCredentials[] Credentials, String ShowHideToggle, String&
> >> > Encoding,
> >> > String& MimeType, ParameterValue[]& ParametersUsed, Warning[]&
> >> > Warnings,
> >> > String[]& StreamIds) +141
> >> > LAMS.ReportViewer.RenderPDFReport() +618
> >> > LAMS.ReportViewer.Page_Load(Object sender, EventArgs e) +88
> >> > System.Web.UI.Control.OnLoad(EventArgs e) +67
> >> > System.Web.UI.Control.LoadRecursive() +35
> >> > System.Web.UI.Page.ProcessRequestMain() +750"
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> PDF's take significantly longer than HTML but it surprises me that a 2
> >> >> page
> >> >> report you see much of a difference. Do you have any service packs
> >> >> installed. If not, my advice is to install SP2.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "bssolutions" <bssolutions@.discussions.microsoft.com> wrote in message
> >> >> news:BBA2388F-E062-4368-987A-62CD9298BD14@.microsoft.com...
> >> >> > We have a web app, built in .Net, with reporting services as our
> >> >> > reporting
> >> >> > tool. The problem we are having is when we have a report that goes
> >> >> > to
> >> >> > numerous people and the report is 2 pages long. When we make it 1
> >> >> > page,
> >> >> > legal size, it works fine (avg records are 500-900). When this
> >> >> > report
> >> >> > is
> >> >> > generated it is created in a pdf format. I can run it on report
> >> >> > services
> >> >> > manager and in the viewer it takes approx 10 secs or less to run and
> >> >> > render,
> >> >> > but when we create the pdf it spikes the processor up to 90% and if
> >> >> > it's a
> >> >> > 2
> >> >> > page report it generates an error.
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>sql