An unexpected error occurred in Report Processing. (rsInternalError)

Category: sql server reportingservices

Question

Manio Manish on Wed, 30 Apr 2014 11:54:56


Hi ,

An unexpected error occurred in Report Processing. (rsInternalError) Get Online Help
The type initializer for 'Microsoft.ReportingServices.Library.RSLocalCacheManager' threw an exception.
The type initializer for 'Microsoft.ReportingServices.Diagnostics.MemoryAuditCollection' threw an exception.
Exception of type 'System.OutOfMemoryException' was thrown.

I get the above error message when i click to see the cube status on SSRS home page under admin reports .

probably all the  TFS 2012  reports  shows the same error message.

Please advice...

No space issue is seen  for the Tfs report server DB or temp db.

Below is  what i find in the  reporting service Logs..

processing!ReportServer_0-78!179c!04/30/2014-09:41:07:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing. ---> System.TypeInitializationException: The type initializer for 'Microsoft.ReportingServices.Library.RSLocalCacheManager' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Microsoft.ReportingServices.Diagnostics.MemoryAuditCollection' threw an exception. ---> System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at Microsoft.ReportingServices.Diagnostics.MemoryAuditCollection..cctor()
   --- End of inner exception stack trace ---
   at Microsoft.ReportingServices.Diagnostics.MemoryAuditCollection.Register(MemoryAuditProxy map)
   at Microsoft.ReportingServices.Library.RSLocalCacheManager..ctor()
   at Microsoft.ReportingServices.Library.RSLocalCacheManager..cctor()
   --- End of inner exception stack trace ---
   at Microsoft.ReportingServices.Library.SegmentCache.TryGetCache(Guid segmentId, Byte[]& buffer)
   at Microsoft.ReportingServices.Library.CacheStorageLayer.Read(SegmentChunkDbInterface storage, ReadWriteParameters parameters, ReadWriteStatistics& statistics)
   at Microsoft.ReportingServices.Library.SegmentedChunkStorage.Read(Int64 position, Byte[] buffer, Int32 offset, Int32 length)
   at Microsoft.ReportingServices.Library.StorageStream.Read(Byte[] buffer, Int32 offset, Int32 count)
   at Microsoft.ReportingServices.Library.BufferedReadWriteStream.FillBuffer(Int32& bytesRead)
   at Microsoft.ReportingServices.Library.BufferedReadWriteStream.ReadByte()
   at System.IO.BinaryReader.ReadByte()

An unexpected error occurred in Report Processing. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing. ---> System.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors
   at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetProperties(String Item, Property[] Properties, ItemNamespaceEnum itemNamespace, Property[]& Values)
   at Microsoft.ReportingServices.WebServer.ReportingService2010.GetProperties(String ItemPath, Property[] Properties, Property[]& Values)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

Thanks,

Manish


Replies

tracycai on Thu, 01 May 2014 06:07:58


Hi,

1. Are you using the NLB? If possible, please turn off the NLB temporally to see whether the is gone.

2. Try to enlarge the execution timeout value in the web.config.

a. Backup the web.config first. Then, open the web.config from the report server folder, located at c:\Program Files\Microsoft SQL Server\MSRS11.<instance name>\Reporting Services\ReportServer\ by default.

b. Find out the following line in the file.

<httpRuntime executionTimeout="9000" />

c. Modify the attribute value from 9000 to 36000. Save the web.config file and restart the reporting service.

3. Restart the reporting service and then you need reproduce this issue, and collect the new reporting service logs.

Thanks.