Cached objects have been evicted (SharePoint 2013)


Applies to: SharePoint Foundation 2013, SharePoint Server 2013

Topic Last Modified: 2016-12-16

Summary: Learn how to resolve the SharePoint Health Analyzer rule "Cached objects have been evicted."

Rule Name: Cached objects have been evicted

Summary: When the memory consumption of the cache service on a cache host exceeds the low watermark threshold, objects that have already expired are evicted. When memory consumption exceeds the high watermark threshold, objects are evicted from memory, whether they have expired or not, until memory consumption returns to the low watermark. Subsequently cached objects may be rerouted to other hosts to maintain an optimal distribution of memory.

Cause: There is not sufficient memory in the cache cluster.

Resolution: Add more RAM to the server
  • You can add more RAM to the server to increase the memory. To identify the failing server: in the SharePoint Central Administration website, in the Monitoring section, click Review problems and solutions, and then find the name of the server in the Failing Servers list. If there are multiple failing servers in a server farm, you must repeat this resolution on each failing server.

Resolution: Increase the memory allocation of the distributed cache
  1. Verify that you have the following memberships:

    • securityadmin fixed server role on the SQL Server instance.

    • db_owner fixed database role on all databases that are to be updated.

    • Administrators group on the server on which you are running the Windows PowerShell cmdlets.

    • Farm Administrators group.

    An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.

    If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about Windows PowerShell permissions, see Add-SPShellAdmin.
  2. Start the SharePoint 2013 Management Shell.

    • For Windows Server 2008 R2:

      • On the Start menu, click All Programs, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Management Shell.

    • For Windows Server 2012:

      1. On the Start screen, click SharePoint 2013 Management Shell.

        If SharePoint 2013 Management Shell is not on the Start screen:

      2. Right-click Computer, click All apps, and then click SharePoint 2013 Management Shell.

    For more information about how to interact with Windows Server 2012, see Common Management Tasks and Navigation in Windows Server 2012.

  3. Check the current distributed cache settings from usage. To do this, run the following command:


    For more information, see Get-SPDistributedCacheClientSetting

  4. Stop the Distributed Cache service on all cache hosts in the farm. To do this, run the following command on each cache host:

    Stop-SPDistributedCacheServiceInstance -Graceful

    For more information, see "Perform a graceful shutdown of the Distributed Cache service" in Manage the Distributed Cache service in SharePoint Server 2013.

  5. To increase the cache size of the Distributed Cache service, run the following command one time only on any cache host at the Windows PowerShell command prompt:

    Update-SPDistributedCacheSize -CacheSizeInMB CacheSize


    • CacheSize is the cache size's memory allocation assignment in megabytes (MB). The default value is 5 percent of total system RAM. This value should not be more than 40 percent of total system RAM with a maximum limit of 16 gigabytes (GB).

  6. Start the Distributed Cache service on all cache hosts. To start the Distributed Cache service, go to the Services on Server page in Central Administration, and start the Distributed Cache service on all cache hosts in the farm.