Re: SMSReporting GetRows Out of Memory failure
- From: "Jeff Gilbert [MSFT]" <jeff.gilbert@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 27 Dec 2006 18:23:41 -0800
Hi Joelle,
Have you tried the resolutions in the SMS Reporting FAQ
(http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/tfaq10.mspx)?
Hopefully one of these will help you resolve your reporting errors!
Jeff Gilbert, MCSE
Technical Writer | Windows & Enterprise Management Division
Microsoft Corporation
This posting is provided "AS IS" with no warranties and confers no rights.
"Steve Thompson" <stevethompson@xxxxxxxxxxxxx> wrote in message
news:uP9YntbKHHA.3552@xxxxxxxxxxxxxxxxxxxxxxx
"Joelle" <jmzack@xxxxxxxxxxxxxxxxxxx(nospam)> wrote in message
news:6AD205D8-99A2-4187-9250-1C5331A50862@xxxxxxxxxxxxxxxx
I have seen several posts about the following error when running SMS
reports:
Microsoft VBScript runtime error '800a0007'
Out of memory: 'GetRows'
/SMSReporting_CEN/Report.asp, line 550
I am getting this error when I run reports that return large amounts of
data. I do not get this error on reports with fewer rows returned and/or
with fewer columns per row.
I added the RowCount key at
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Reporting and set it to
0xffffffff
hexadecimal to return all rows so that we can get reports that include
all
data.
I already changed the Metabase.xml file to increase the AspBufferingLimit
value.
Still no luck.
I get this error with built-in reports as well as my own custom reports,
so
I don't think it has anything to do with my SQL code.
I haven't seen any information posted indicating that anyone else got a
reply and/or suggestions for resolving this problem. What should I do so
that I can get large reports to return all data to the screen in SMS
Reporting.
I do not know if this will help you... you may have hit an upper limit on
the amount of data you are bringing back.. I found I needed to modify the
global.asa file to prevent timeouts, I've adjusted the following
variables:
from:
Session("DBConnectionTimeout") = 30
Session("DBCommandTimeout") = 300
Session.Timeout = 10
to:
Session("DBConnectionTimeout") = 300
Session("DBCommandTimeout") = 3000
Session.Timeout = 100
ST
.
- References:
- Re: SMSReporting GetRows Out of Memory failure
- From: Steve Thompson
- Re: SMSReporting GetRows Out of Memory failure
- Prev by Date: SMS SDK Automation.dll and Collection Rules
- Next by Date: Re: HA for SMS Database
- Previous by thread: Re: SMSReporting GetRows Out of Memory failure
- Next by thread: SMS SDK Automation.dll and Collection Rules
- Index(es):
Relevant Pages
|
Loading