Microsoft KB Archive/840709

= The Reporting Services Windows service may stop responding when you distribute many reports through subscriptions =

Article ID: 840709

Article Last Modified on 4/3/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Reporting Services

-



SYMPTOMS
When you distribute many reports through subscriptions that use the e-mail delivery extension or the file share delivery extension, you may receive a System.OutOfMemory exception. Additionally, the Microsoft SQL Server 2000 Reporting Services Windows service may stop responding. Error messages that are similar to the following may appear in the Reporting Services error log:

ReportingServicesService!processing!7b0!12/18/2003-08:32:17:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing., ; Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing. ---> System.OutOfMemoryException: Exception of type System.OutOfMemoryException was thrown. --- End of inner exception stack trace --- ReportingServicesService!library!b78!12/18/2003-08:32:17:: e ERROR: Connection close failed. Exception thrown: System.OutOfMemoryException: Exception of type System.OutOfMemoryException was thrown. ReportingServicesService!library!c34!12/18/2003-08:32:18:: e ERROR: Transaction rollback failed. Exception thrown: System.OutOfMemoryException: Exception of type System.OutOfMemoryException was thrown. ReportingServicesService!library!698!12/18/2003-08:32:18:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., Internal error; Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. ---> System.OutOfMemoryException: Exception of type System.OutOfMemoryException was thrown. --- End of inner exception stack trace ---

The problem occurs when both of the following conditions are true:
 * The subscriptions are scheduled to be processed frequently (every 3 minutes, for example).
 * The reports contain lots of data.

This problem may occur even if there is sufficient free memory available on the computer that is running the Reporting Services Windows service.



WORKAROUND
To work around this problem, you can set the MemoryLimit setting in the RSReportServer.config configuration file to a value that is less than 120.

Note By default, the RSReportServer.config file is located in the \ReportServer folder. The default value for the MemoryLimit setting is 60.

