I noticed the formatting was messed up so I have reposted below.
Hi Everyone
Im running SQLSefrver Reporting Services 2000 SP 1 on Windows Server 2003 and getting the error below.
Can anyone point me in the right direction as to what this could mean and how I could fix the problem.
This is the error that is being logged in the reportserver error log:
w3wp!runningjobs!364!8/02/2007-18:37:17:: w WARN: Previous request for Memory stats updatestill executing, skipping...
w3wp!runningjobs!364!8/02/2007-18:38:17:: w WARN: Previous request for Memory stats updatestill executing, skipping...
w3wp!runningjobs!364!8/02/2007-18:39:17:: w WARN: Previous request for Memory stats updatestill executing, skipping...
w3wp!runningjobs!364!8/02/2007-18:40:17:: w WARN: Previous request for Memory stats updatestill executing, skipping...
w3wp!library!3114!02/08/2007-18:40:18:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ; Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. --> System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.Diagnostics.ResourceUtilities.get_PrivateMBytes() at Microsoft.ReportingServices.Diagnostics.ResourceUtilities.get_TooMuchMemory() at Microsoft.ReportingServices.WebServer.Global.Application_AuthenticateRequest(Object sender, EventArgs e)
-- End of inner exception stack trace --
w3wp!library!18ec!02/08/2007-18:41:03:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ; Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. --> System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.Diagnostics.ResourceUtilities.get_PrivateMBytes() at Microsoft.ReportingServices.Diagnostics.ResourceUtilities.get_TooMuchMemory() at Microsoft.ReportingServices.WebServer.Global.Application_AuthenticateRequest(Object sender, EventArgs e)
-- End of inner exception stack trace --
|||
OK, placing the report and reportserver virtual directories into their own app. pools seems to have "fixed" the problem. Dont know why but at the moment Im happy its just fixed!!
