Report viewer send print job with a large memory

i am using reporting service 2005 and report viewer from vs.net 2005.

when i send a print job from report view to HP Laserjet 1320, there print job is actually abt 20MB for 20 pages.

it happends that the printer will hav problem printing the print job or just hang there..

is there any way to resolve it?

There was an issue with 2005 that the print control did not get updated correctly if you had the 2000 print control. Is it possible that you have the 2000 print control on the client? If so, you can clear the control from the client by going to Tools->Internet Options->Settings->View Objects in IE, then delete the RSPrintControl. The next time you go to use the print control a new one should be downloaded.

Report Timeout problem ;Out of memory exception

I am having a problem with report rendering.
The MSSRS Report runs for around 15 minutes and then the report page times
out giving the error as
"Out of memory exception. Server application unavailable".
When i check the query execution time in query analyser, query returns
results in 10 minutes.
There are about 3 groups in the RDL design.
Please provide any suggestions to overcome this problem.
Thanks in advance.
Thanks and Cheers,
TruptiSounds like your report is just too big. RS renders reports in memory, thus
the 'Out of memory exception'. Try redesigning the report or adding more
memory to your machine/server.
Also, if you get the report to successfully run you can try to pin point
what's taking so long. Look in the ReportServer database; the ExecutionLog
table. It shows what report ran, when, the amount of time for data
retrieval, processing time, and rendering time. It also shows what render
format, render status (fail or success), query row count and byte size of
the rendered file.
--
Adrian M.
MCP
"Trupti" <gettrupti@.hotmail.com> wrote in message
news:e0Tt9bcNFHA.1392@.TK2MSFTNGP10.phx.gbl...
>I am having a problem with report rendering.
> The MSSRS Report runs for around 15 minutes and then the report page
> times out giving the error as
> "Out of memory exception. Server application unavailable".
> When i check the query execution time in query analyser, query returns
> results in 10 minutes.
> There are about 3 groups in the RDL design.
> Please provide any suggestions to overcome this problem.
> Thanks in advance.
> Thanks and Cheers,
> Trupti
>
>

Report Server Queue not fully utilizing resources

We've set up a report farm with two servers, both 64 bit with 4 CPUs each. One has 16Gig and the other 8Gig of memory. We're using Windows NLB and the load test software confirms that the NLB is working. When we run a number of concurrent reports, both servers get utilized, but they only work on a few at a time. The report server queue doesn't seem to be fully utilizing the hardware. From a prior post I've learned that the report server queue automatically runs 4 reports per CPU. This is not occuring for our setup. Has anyone else experienced the same? Are there any configurations that need to be set to open the queue up? The reports are heavy (300,000 records grouped and summed). Does this affect the queuing process?

For interactive requests the queue is managed by ASP.Net. You might want to confirm that its settings are allowing multiple requests. What about the catalog database? Have you confirmed that you are not seeing an IO problem on that?

http://blogs.msdn.com/jgalla/archive/2007/03/21/reportservertempdb-io-saturation.aspx

|||

Thanks John.We tested our throughput with the catalog database and it’s not a problem.The MaxActiveReqForOneUser setting in the RSWebApplication Configuration File is currently set to 0, which allows unlimited requests for a single user.We are using only one user id for all report requests.It’s embedded in our web application.Our web application is using the webmethod WebReports.Render from the RS SOAP API to run reports.Is there some limitation on the SOAP API methods that may cause the queue to backup?Is there any limitation on the number of simultaneously processing reports for one user? (Not sure if there’s a limitation difference between Active Requests, which could be queued, and Processing reports)

Below is a sample of our WebReports.Render method.

WebReports.Render(/MyPiersReports/XXXXX/Criteria_Reports/Reg_02_RegionCommodity, XML, null, "", ,this._paramValues, null, null, "Unicode (UTF-8)", "text/xml", this._historyParams,null,null)

|||There are no limitations in the SOAP API which would serialize all requests from a single user.