September 11, 2017 at 1:28 pm
Hi,
Our reports suddenly stops working on August 30 and the quickest resolution that can be done is reboot the database server. While looking at the logs for reporting services. I have found this section where it says "Error while performing memory shrink: System.OutOfMemoryException". I am pretty new in SQL server administration and I hope someone could help me understand why this happened. Below are the data I have in my logs. I don't have this same error on other days so I would assume this is the culprit.
<Header>
<Product>Microsoft SQL Server Reporting Services Version 2011.0110.5058.00 ((SQL11_PCU_Main).140514-1820 )</Product>
<Locale>English (Canada)</Locale>
<TimeZone>Central Daylight Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\Logfiles\ReportServerService__08_30_2017_00_09_33.log</Path>
<SystemName>MyServer</SystemName>
<OSName>Microsoft Windows NT 6.2.9200</OSName>
<OSVersion>6.2.9200</OSVersion>
<ProcessID>1860</ProcessID>
<Virtualization>Hypervisor</Virtualization>
</Header>
<ProcessorArchitecture>AMD64</ProcessorArchitecture>
<ApplicationArchitecture>AMD64</ApplicationArchitecture>
library!WindowsService_64!bb0!08/30/2017-00:09:33:: i INFO: Call to CleanBatch()
library!WindowsService_64!bb0!08/30/2017-00:09:33:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_64!bb0!08/30/2017-00:09:33:: i INFO: Call to CleanBatch() ends
library!WindowsService_64!3c4!08/30/2017-00:19:33:: i INFO: Call to CleanBatch()
library!WindowsService_64!3c4!08/30/2017-00:19:33:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_64!3c4!08/30/2017-00:19:33:: i INFO: Call to CleanBatch() ends
library!WindowsService_64!bb0!08/30/2017-00:29:33:: i INFO: Call to CleanBatch()
library!WindowsService_64!bb0!08/30/2017-00:29:33:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_64!bb0!08/30/2017-00:29:33:: i INFO: Call to CleanBatch() ends
library!WindowsService_64!bb0!08/30/2017-00:39:33:: i INFO: Call to CleanBatch()
library!WindowsService_64!bb0!08/30/2017-00:39:33:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_64!bb0!08/30/2017-00:39:33:: i INFO: Call to CleanBatch() ends
library!WindowsService_64!770!08/30/2017-00:49:33:: i INFO: Call to CleanBatch()
library!WindowsService_64!770!08/30/2017-00:49:33:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_64!770!08/30/2017-00:49:33:: i INFO: Call to CleanBatch() ends
library!WindowsService_64!788!08/30/2017-00:59:33:: i INFO: Call to CleanBatch()
library!WindowsService_64!788!08/30/2017-00:59:33:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_64!788!08/30/2017-00:59:33:: i INFO: Call to CleanBatch() ends
library!WindowsService_64!770!08/30/2017-01:09:33:: i INFO: Call to CleanBatch()
library!WindowsService_64!770!08/30/2017-01:09:33:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_64!770!08/30/2017-01:09:33:: i INFO: Call to CleanBatch() ends
library!WindowsService_64!bc0!08/30/2017-01:19:32:: i INFO: Call to CleanBatch()
library!WindowsService_64!bc0!08/30/2017-01:19:32:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_64!bc0!08/30/2017-01:19:32:: i INFO: Call to CleanBatch() ends
library!WindowsService_64!770!08/30/2017-01:29:32:: i INFO: Call to CleanBatch()
library!WindowsService_64!770!08/30/2017-01:29:32:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_64!770!08/30/2017-01:29:32:: i INFO: Call to CleanBatch() ends
library!WindowsService_64!7c0!08/30/2017-01:39:32:: i INFO: Call to CleanBatch()
library!WindowsService_64!7c0!08/30/2017-01:39:32:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_64!7c0!08/30/2017-01:39:32:: i INFO: Call to CleanBatch() ends
library!WindowsService_64!770!08/30/2017-01:49:32:: i INFO: Call to CleanBatch()
library!WindowsService_64!770!08/30/2017-01:49:32:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_64!770!08/30/2017-01:49:32:: i INFO: Call to CleanBatch() ends
library!WindowsService_64!bb0!08/30/2017-01:59:32:: i INFO: Call to CleanBatch()
library!WindowsService_64!bb0!08/30/2017-01:59:32:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_64!bb0!08/30/2017-01:59:32:: i INFO: Call to CleanBatch() ends
dbcleanup!WindowsService_64!7c0!08/30/2017-01:59:58:: i INFO: Expiring old execution log entries
library!WindowsService_64!7c0!08/30/2017-02:09:32:: i INFO: Call to CleanBatch()
library!WindowsService_64!7c0!08/30/2017-02:09:32:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_64!7c0!08/30/2017-02:09:32:: i INFO: Call to CleanBatch() ends
library!WindowsService_64!bb0!08/30/2017-02:19:32:: i INFO: Call to CleanBatch()
library!WindowsService_64!bb0!08/30/2017-02:19:32:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_64!bb0!08/30/2017-02:19:32:: i INFO: Call to CleanBatch() ends
appdomainmanager!DefaultDomain!768!08/30/2017-02:20:26:: e ERROR: Error while performing memory shrink: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
appdomainmanager!DefaultDomain!768!08/30/2017-02:22:37:: e ERROR: Error while performing memory shrink: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
library!WindowsService_64!3c4!08/30/2017-02:29:32:: i INFO: Call to CleanBatch()
library!WindowsService_64!3c4!08/30/2017-02:29:32:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions.
library!WindowsService_64!3c4!08/30/2017-02:29:32:: i INFO: Call to CleanBatch() ends
appdomainmanager!DefaultDomain!768!08/30/2017-02:30:14:: e ERROR: Error while performing memory shrink: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
appdomainmanager!DefaultDomain!768!08/30/2017-02:30:16:: e ERROR: Error while performing memory shrink: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown
September 11, 2017 at 2:39 pm
Don't have any direct experience with that kind of error, but is it possible that SSRS is seeking more memory than is readily available? In other words, is it possible that you're RAM constrained ?
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
September 11, 2017 at 2:43 pm
Sue
September 12, 2017 at 7:42 am
Thank you so much for your responses
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply