Distributed Cache loading issue
Distributed Cache settings cannot be loaded because the server is not part of the Distributed Cache Cluster.
Summary
SPDocKit Snapshot Wizard or SPDocKit PowerShell module do not load Distributed Cache settings data and display a warning message during the load:
Please note! Distributed Cache settings cannot be loaded on a server that is not part of a Distributed Cache Cluster.
This happens because SPDocKit Snapshot Wizard or SPDocKit PowerShell module query only the server it is installed on for Distributed Cache data, so if the server on which SPDocKit Consultant is running is not a host for the Distributed Cache service, no data will be loaded.
Application version: 4.1.0 and newer
Solution
Take snapshot and run the load process from a server that is part of the Distributed Cache Cluster.
Workaround
Distributed Cache API requires that the registry of the current server contains data providers and connection string for the cluster, or take snapshot on a server that is part of the Distributed Cache Cluster.
There is an unofficial workaround for this restriction which includes editing the registry of the server on which you are taking a snapshot, to include the fields required by the API. This means running a PowerShell script on the server in order to update the provider and connection string fields.
The registry fields will be correctly updated using this PowerShell script:
Credit: To learn more about this workaround, please visit the Wouter Bleeker blog.
Status: Not resolved.
Last updated