Check the Distributed Cache service status in SharePoint Central Administration first. A stopped or disabled service causes farm-wide performance degradation and error events. This diagnostic flow separates a simple service state issue from other causes, then applies the required fix to enable the service.
📊 Distributed Cache service is available in SharePoint Server 2013, 2016, 2019, and Subscription Edition. Source: Microsoft.
How SharePoint distributed cache issues actually manifest
What the symptoms mean before you touch anything
A cache disruption often reveals itself as stale newsfeeds, slow authentication challenges, or odd browser behaviors. The event "Distributed cache service is not enabled in this deployment" occurs when the Distributed Cache service is stopped.
Stale feed data occurs because Feed Cache (tags, activities) cannot refresh without an active service instance. In memory cache failures within application pools are distinct; the farm-level Distributed Cache Service must be healthy before individual app pools perform correctly. Start by confirming the service instance is not already Disabled or Provisioning on your target server before assuming a more complex issue.
How to check service status in Central Administration
Navigate to SharePoint Central Administration first. Do not rely solely on PowerShell, where services sometimes appear stuck in a provisioning state even when the backend is healthy.
- Check the service instance: In the Service Applications section, click Manage services on server. Verify that the Distributed Cache service is listed with a status of Started.
- If the service is Disabled: This is the most common cause of the error event. Proceed to the fix steps below.
- If the service is Stopping or Provisioning: Wait for the state to complete, then recheck.
Likely causes: disabled service or insufficient permissions
Most often, the error stems from the Distributed Cache service being disabled on the server. Less commonly, the account running the fix lacks the required permissions.
Fix: Enable the Distributed Cache service
The Distributed Cache service is disabled on this server, which triggers the event. Follow these steps to enable it:
- Ensure your account has the securityadmin fixed server role on the SQL Server instance, db_owner role on the relevant databases, is a member of the Administrators group on the server, and is a member of the Farm Administrators group.
- Start the SharePoint Management Shell on the server where the service is to be enabled.
- Verify status by clicking Manage services on server in SharePoint Central Administration and ensuring the Distributed Cache service is listed with a status of Started.
How to remove and re-add broken instances safely
If diagnosis confirms a service instance is corrupted, the underlying state persists until you remove and re-provision it. Administrative access often requires the securityadmin role on SQL Server and db_owner role on the configuration database, as well as membership in the Administrators group and Farm Administrators group.
- Start the SharePoint Management Shell as a Farm Administrator.
- Run
Remove-SPDistributedCacheServiceInstanceon the affected server. This removes the service instance from the farm. - Wait for the removal to propagate. You can monitor progress by checking Manage services on server in Central Administration.
- Once removed, run
Add-SPDistributedCacheServiceInstanceon the same server to register the service again. - Verify status in Central Administration by clicking Manage services on server and ensuring the Distributed Cache service lists Started.
A common first-timer mistake is running Add-SPDistributedCacheServiceInstance without first confirming the instance was removed. If the service is still listed as online, adding another instance will create a conflict. Always check the status before attempting to add.
Diagnostic checklist for SharePoint distributed cache errors
Use this decision table to map specific error symptoms to the precise command sequences required for resolution. Do not skip the verification steps.
| Symptom | Diagnostic Check | Action Sequence |
|---|---|---|
| Error: "Distributed cache service is not enabled in this deployment" | Check service status in Central Administration | Click Manage services on server; if Disabled, run Add-SPDistributedCacheServiceInstance |
| Service shows "Disabled" in CA | Verify permissions | Confirm securityadmin role on SQL, db_owner on databases, Administrators group membership, and Farm Administrators group membership |
| Service stuck in "Provisioning" | Check for leftover instance data | Run Remove-SPDistributedCacheServiceInstance, then Add-SPDistributedCacheServiceInstance |
When to escalate beyond basic troubleshooting
If the service remains unstable after verifying permissions and enabling the service instance, the issue may involve deeper database inconsistencies or SQL mirroring problems. Review the ULS logs on the server for detailed entries. If the problem persists, engaging Microsoft Support with the relevant ULS entries will expedite resolution.
Prevention
Always ensure your account holds the required permissions (securityadmin, db_owner, Administrators group, and Farm Administrators group) before running Distributed Cache cmdlets. After applying cumulative updates, verify the Distributed Cache service status in Central Administration to confirm it remains Started.
Frequently asked questions
What is distributed cache?
The Distributed Cache Service is a server component that stores data across multiple farm servers to improve performance. It handles session state, authentication tokens, and Feed Cache data. It is available in SharePoint Server 2013, 2016, 2019, and Subscription Edition.
Centralized cache vs distributed cache?
Centralized cache typically refers to a single-server storage mechanism, while Distributed Cache spreads data across multiple nodes for high availability. In SharePoint, the Distributed Cache ensures that if one server fails, the cache data remains accessible from other nodes in the cluster.
In memory cache vs distributed cache?
In-memory cache resides on a single server's RAM and is lost if that server restarts. Distributed Cache replicates data across the farm, providing redundancy. Application pools use in-memory cache for local speed, but SharePoint relies on Distributed Cache for farm-wide data consistency.
How to delete site cache
To clear the site-specific cache, users can append ?clearcache=1 to the site URL or use the browser's developer tools to clear local storage. For administrators, resetting the Distributed Cache service instance will clear site-level cached data across the farm.
SharePoint clear config cache command?
There is no single PowerShell command to clear the config cache automatically. You must manually stop the relevant services, delete the XML files in the Config folder, and reset the CacheVersion value in the cache.ini file before restarting the services.