Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Windows Server 2012: Server Manager can consume a large amount of private memory

Windows Server 2012: Server Manager can consume a large amount of private memory

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You are running Windows Server 2012 and Server Manager is running in one or more sessions
  • There is high load on the system and a process or processes are logging a large number of events to the event log on the system within the Server Manager retention period (default 24 hours)
In the above scenario, Server Manager can continue to consume memory on the system until all memory is exhausted and the server becomes unresponsive.

↑ Back to the top

Cause

The minimum event retention period in Server Manager is 24 hours. Server Manager combines data from various sources within memory. The behavior occurs because Server Manager does not observe Eventlog quotas nor does it release the events from memory when they are outside of the display filters for Server Manager (even with a manual refresh). Server Manager frees the event data from memory after the retention period set by the user. The default retention period is 24 hours.

Error conditions on the system further exacerbate the issue due to the higher rate of event generation and subsequently a higher rate of memory consumption.

↑ Back to the top

Resolution

Cumulative Update information

To resolve this issue, install the Windows 8 and Windows Server 2012 cumulative update 2811660. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2811660 Windows 8 and Windows Server 2012 cumulative update: March 2013

↑ Back to the top

Workaround

To workaround this issue, Microsoft recommends investigating the source of the increased event logging and resolving the conditions generating the events.  

Alternatively, closing Server Manager resolves the issue. 

↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info
Article ID : 2851710
Revision : 1
Created on : 1/7/2017
Published on : 1/21/2014
Exists online : False
Views : 199