Others

How to Fix SharePoint Distributed Cache Service Noncompliant Status

Steven Parker Oct 13, 2026 868 views

Question details

The user needs to resolve a noncompliant status for the Distributed Cache service after adding it to an application server.

Fix SharePoint Distributed Cache Service Noncompliant Status

Product: SharePoint Server Subscription Edition
Device & OS: not provided
Scenario: Adding the Distributed Cache service to an application server configured with the Search role.
Observed behavior: The Distributed Cache service status displays as "Complaint is No".

Before you start

Verify that you have SharePoint Farm Administrator privileges to review server topologies and that you have gathered the details of your current MinRole configuration.

Solution 1Recommended

Verify MinRole Compliance and Consult Microsoft Support

Check your server role configuration against SharePoint's MinRole requirements and seek specialized guidance from Microsoft.

In SharePoint Server Subscription Edition, server roles are strictly managed by the MinRole topology feature. When a service like the Distributed Cache is placed on a server with an incompatible role (such as the Search role), SharePoint flags the service instance as noncompliant.

Because this involves complex on-premises Server configurations rather than SharePoint Online, resolving it requires reviewing your farm topology and potentially reallocating services.

Check MinRole compatibility

Navigate to SharePoint Central Administration > System Settings > Convert server role in this farm. Verify if running the Distributed Cache service on your specific Search role server violates the configured MinRole topology.

Review the service status

Go to Central Administration > System Settings > Manage services in this farm. Note the exact status, server associations, and any accompanying error logs for the Distributed Cache service.

Consult the Microsoft Q&A Community

Visit the dedicated SharePoint Server Microsoft Q&A community. Post your question along with your specific farm topology and the "Complaint is No" service status details.

Open a Microsoft support case

If community support cannot resolve the topology conflict, log into your Microsoft 365 Admin Center or Microsoft Support portal to open a formal support case with the collected logs.

Verify MinRole Compliance and Consult Microsoft Support

Important: Do not attempt to force start the service via PowerShell without ensuring it aligns with your MinRole architecture, as this can lead to further farm instability.

Free Microsoft Office alternative

Simplify Your Document Management with WPS Office

While configuring on-premises Microsoft SharePoint Server can be complex and requires heavy IT oversight, WPS Office provides a free, lightweight, and easy-to-use alternative for everyday document creation and sharing. Enjoy full Microsoft Office format compatibility without the heavy server management.

1. Download and install: Visit the official WPS Office website to download the free, lightweight installer for your device.
2. Open your documents: Launch WPS Office and seamlessly open your existing Microsoft Office files with full layout retention.
3. Collaborate in the cloud: Use WPS Cloud to share documents via links and collaborate with your team effortlessly.

Fully compatible with Microsoft Word, Excel, and PowerPoint file formatsLightweight application that requires minimal system resourcesBuilt-in cloud collaboration and file sharing featuresFamiliar user interface for a seamless migration

microsoft office alternative - wps office

Frequently Asked Questions

What does 'Complaint is No' mean in SharePoint Server?

It indicates that a specific service instance on a server is not compliant with the server's designated MinRole topology. SharePoint automatically checks if the services running on a server match what is expected for its assigned role.

Can I run Distributed Cache on a Search role server?

Typically, running Distributed Cache on a dedicated Search server can cause performance issues and may violate strict MinRole definitions depending on your farm topology. It is generally recommended to use a dedicated Distributed Cache role or a Custom role if combining services.

Where should I get help for SharePoint Server configuration issues?

For on-premises SharePoint Server issues, it is best to post your farm topology details in the dedicated SharePoint Server Microsoft Q&A community or open a support ticket directly with Microsoft.

Office Quick Solutions