| Groups | Blog | Home |
sql server reporting services : SQL Server Reporting Services Issue
It sounds like you are tweaking the wrong value. In machine.config look for
the processModel element and the memoryLimit attribute. This attribute represents the percentage of memory that ASP.Net can use before it recycles the AppDomain. Increasing this value should allow the report to run. -- -Daniel This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "SriSamp" <ssampath@sct.co.in> wrote in message news:ux0U5Ey8EHA.208@TK2MSFTNGP12.phx.gbl... > One of my collegues reported the following behavior in SQL Server > Reporting > Services (am pasting the issue verbatim as reported): > > ===== > We are using SQL Server Reporting Services with Service Pack 1 to generate > some reports. There is a performance issue in generating reports. If we > try > to generate the reports for more than 1000 records we get an error > 'operation timedout' and reports are not generated. The above error occurs > if we try to generate the reports for PDF and TIFF formats. We are able to > successfully generate reports for XLS format. > ===== > > To get over this issue, I suggested that they increase the timeout in the > reporting services object, which solved the problem temporarily. However, > today, a different issue was reported (as a consequence of the earlier > setting): > > ===== > After increasing the 'timeout' of report service object, it worked for > 1000+ > records. Now after increasing the number of records to more than 2000 the > application is crashing. The IIS event log shows an error "aspnet_wp.exe > is > recycled because memory consumption exceeded 305 MB". The suggested fix > was > to changes the value in machine.config (increasing file limit from default > 4MB to 100 MB). However, the issue is still not solved, since it can recur > again. > ===== > > Any suggestions? > > -- > HTH, > SriSamp > Please reply to the whole group only! > http://www32.brinkster.com/srisamp > >
One of my collegues reported the following behavior in SQL Server Reporting
Services (am pasting the issue verbatim as reported): ===== We are using SQL Server Reporting Services with Service Pack 1 to generate some reports. There is a performance issue in generating reports. If we try to generate the reports for more than 1000 records we get an error 'operation timedout' and reports are not generated. The above error occurs if we try to generate the reports for PDF and TIFF formats. We are able to successfully generate reports for XLS format. ===== To get over this issue, I suggested that they increase the timeout in the reporting services object, which solved the problem temporarily. However, today, a different issue was reported (as a consequence of the earlier setting): ===== After increasing the 'timeout' of report service object, it worked for 1000+ records. Now after increasing the number of records to more than 2000 the application is crashing. The IIS event log shows an error "aspnet_wp.exe is recycled because memory consumption exceeded 305 MB". The suggested fix was to changes the value in machine.config (increasing file limit from default 4MB to 100 MB). However, the issue is still not solved, since it can recur again. ===== Any suggestions? -- HTH, SriSamp Please reply to the whole group only! http://www32.brinkster.com/srisamp
Thanks Daniel. Will forward this to my collegue.
On a related note, is 2000 records too much for RS to handle? Why is there so much memory consumption? Even if we increase this limit, chances are it can cap again in the future with more records being processed. Is there a long-term solution way out here? -- HTH, SriSamp Please reply to the whole group only! http://www32.brinkster.com/srisamp [quoted text, click to view] "Daniel Reib [MSFT]" <danreib@online.microsoft.com> wrote in message news:%23N8MnC18EHA.3260@TK2MSFTNGP10.phx.gbl... > It sounds like you are tweaking the wrong value. In machine.config look for > the processModel element and the memoryLimit attribute. This attribute > represents the percentage of memory that ASP.Net can use before it recycles > the AppDomain. Increasing this value should allow the report to run. > > -- > -Daniel > This posting is provided "AS IS" with no warranties, and confers no rights. > > > "SriSamp" <ssampath@sct.co.in> wrote in message > news:ux0U5Ey8EHA.208@TK2MSFTNGP12.phx.gbl... > > One of my collegues reported the following behavior in SQL Server > > Reporting > > Services (am pasting the issue verbatim as reported): > > > > ===== > > We are using SQL Server Reporting Services with Service Pack 1 to generate > > some reports. There is a performance issue in generating reports. If we > > try > > to generate the reports for more than 1000 records we get an error > > 'operation timedout' and reports are not generated. The above error occurs > > if we try to generate the reports for PDF and TIFF formats. We are able to > > successfully generate reports for XLS format. > > ===== > > > > To get over this issue, I suggested that they increase the timeout in the > > reporting services object, which solved the problem temporarily. However, > > today, a different issue was reported (as a consequence of the earlier > > setting): > > > > ===== > > After increasing the 'timeout' of report service object, it worked for > > 1000+ > > records. Now after increasing the number of records to more than 2000 the > > application is crashing. The IIS event log shows an error "aspnet_wp.exe > > is > > recycled because memory consumption exceeded 305 MB". The suggested fix > > was > > to changes the value in machine.config (increasing file limit from default > > 4MB to 100 MB). However, the issue is still not solved, since it can recur > > again. > > ===== > > > > Any suggestions? > > > > -- > > HTH, > > SriSamp > > Please reply to the whole group only! > > http://www32.brinkster.com/srisamp > > > > > >
TIFF and PDF are the two worst renderers with respect to memory consumption.
We continue to look at ways to improve this. The only workarounds are to choose other renderings or try and limit the amount of information in the report. -- -Daniel This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "SriSamp" <ssampath@sct.co.in> wrote in message news:OAMADo68EHA.4028@TK2MSFTNGP15.phx.gbl... > Thanks Daniel. Will forward this to my collegue. > > On a related note, is 2000 records too much for RS to handle? Why is there > so much memory consumption? Even if we increase this limit, chances are it > can cap again in the future with more records being processed. Is there a > long-term solution way out here? > -- > HTH, > SriSamp > Please reply to the whole group only! > http://www32.brinkster.com/srisamp > > "Daniel Reib [MSFT]" <danreib@online.microsoft.com> wrote in message > news:%23N8MnC18EHA.3260@TK2MSFTNGP10.phx.gbl... >> It sounds like you are tweaking the wrong value. In machine.config look > for >> the processModel element and the memoryLimit attribute. This attribute >> represents the percentage of memory that ASP.Net can use before it > recycles >> the AppDomain. Increasing this value should allow the report to run. >> >> -- >> -Daniel >> This posting is provided "AS IS" with no warranties, and confers no > rights. >> >> >> "SriSamp" <ssampath@sct.co.in> wrote in message >> news:ux0U5Ey8EHA.208@TK2MSFTNGP12.phx.gbl... >> > One of my collegues reported the following behavior in SQL Server >> > Reporting >> > Services (am pasting the issue verbatim as reported): >> > >> > ===== >> > We are using SQL Server Reporting Services with Service Pack 1 to > generate >> > some reports. There is a performance issue in generating reports. If we >> > try >> > to generate the reports for more than 1000 records we get an error >> > 'operation timedout' and reports are not generated. The above error > occurs >> > if we try to generate the reports for PDF and TIFF formats. We are able > to >> > successfully generate reports for XLS format. >> > ===== >> > >> > To get over this issue, I suggested that they increase the timeout in > the >> > reporting services object, which solved the problem temporarily. > However, >> > today, a different issue was reported (as a consequence of the earlier >> > setting): >> > >> > ===== >> > After increasing the 'timeout' of report service object, it worked for >> > 1000+ >> > records. Now after increasing the number of records to more than 2000 > the >> > application is crashing. The IIS event log shows an error >> > "aspnet_wp.exe >> > is >> > recycled because memory consumption exceeded 305 MB". The suggested fix >> > was >> > to changes the value in machine.config (increasing file limit from > default >> > 4MB to 100 MB). However, the issue is still not solved, since it can > recur >> > again. >> > ===== >> > >> > Any suggestions? >> > >> > -- >> > HTH, >> > SriSamp >> > Please reply to the whole group only! >> > http://www32.brinkster.com/srisamp >> > >> > >> >> > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |