Fix SharePoint Distributed Cache "cacheHostInfo is null" Error After Server Rename

Resolve the SharePoint "cacheHostInfo is null" error after a WFE server rename by safely rebuilding the Distributed Cache instance using PowerShell.

Dealing with SharePoint server configuration issues can be frustrating, especially when a routine server rename unexpectedly breaks your caching services. If you're encountering the "cacheHostInfo is null" error, don't worry—there is a direct, command-line fix to get your farm running smoothly again.

Problem Description: SharePoint WFE Rename Cache Failures

After changing the hostname of a SharePoint Web Front End (WFE) server, the Distributed Cache service often retains the old server name. This configuration mismatch causes the cache cluster to fail, resulting in the "cacheHostInfo is null" error message, broken authentication tokens, and degraded overall farm performance.

Quick Answer for Distributed Cache Name Mismatches

Do not manually edit the AppFabric ClusterConfig.xml file. Instead, use SharePoint PowerShell with Farm Administrator privileges to remove the stale cache instance and recreate it using the Add-SPDistributedCacheServiceInstance cmdlet.

Likely Causes Behind The cacheHostInfo Null Error

• Server Renaming: Changing the WFE server's hostname without first gracefully stopping and unprovisioning SharePoint services.
• AppFabric Desynchronization: The underlying Windows Server AppFabric caching service retaining memory of the old hostname.
• DNS Resolution Issues: Outdated Domain Name System (DNS) records still pointing traffic to the old server name instead of the new one.

Recommended Solution: Rebuild SharePoint Cache via PowerShell

1. Log in to the affected SharePoint WFE server using an account with Farm Administrator privileges.
2. Open the SharePoint Management Shell as an Administrator.
3. Crucial Warning: Do not attempt to manually modify the AppFabric ClusterConfig.xml file, as this can corrupt the entire farm cluster configuration.
4. Run the following command to delete the outdated, obsolete cache instance:
   Remove-SPDistributedCacheServiceInstance
5. Provision a fresh instance mapped to the newly updated server name by executing:
   Add-SPDistributedCacheServiceInstance
6. Verify the cache cluster health by running Get-SPCacheHost. Ensure the new hostname appears correctly and the service status displays as "UP".
7. Finally, verify that the local server hostname is updated, confirm DNS resolution is routing properly, and check that the AppFabric Caching Service is actively running in the Windows Services (services.msc) panel.

Alternative Solutions for AppFabric Synchronization Issues

1. Restart AppFabric Service: Sometimes, simply restarting the "AppFabric Caching Service" via the Windows Services console can resolve minor state desynchronizations.
2. Flush DNS Cache: Open standard Command Prompt as an administrator and run ipconfig /flushdns on the server to ensure it is resolving the new hostname locally.
3. Clear Configuration Cache: Stop the SharePoint Timer Service, delete the XML files inside the configuration cache folder (leaving the cache.ini file), reset the cache.ini value to 1, and restart the Timer Service.

Working with WPS Office: A Reliable Document Alternative

While WPS Office cannot fix SharePoint server-side AppFabric or caching errors, it serves as an excellent fallback when your SharePoint document libraries are temporarily inaccessible. If server issues prevent you from opening or editing files collaboratively online, WPS Office is a robust, free alternative to Microsoft Office. It allows you to effortlessly create, open, edit, and save Word, Excel, and PowerPoint-compatible documents locally on your desktop until your SharePoint farm is fully restored.

Prevention Tips for SharePoint Server Renames

• Always gracefully stop the Distributed Cache service on a specific node before making hostname or IP address changes.
• Ideally, remove the server from the SharePoint farm entirely before renaming it, then run the configuration wizard to rejoin it to the farm under the new name.
• Keep DNS records updated immediately after a server name change to prevent intra-farm communication and lookup failures.

FAQs About SharePoint Distributed Cache Administration

Can I just edit ClusterConfig.xml to fix the hostname?

No. Manually editing the AppFabric ClusterConfig.xml is strictly unsupported by Microsoft and can cause catastrophic, irreversible failure of the Distributed Cache cluster. Always use the provided PowerShell cmdlets to manage cache hosts.

How do I check if my Distributed Cache is running correctly?

Open the SharePoint Management Shell and run the Get-SPCacheHost command. It will output a list of all cache hosts in your cluster along with their current operational status, port numbers, and hostnames.

Does renaming the server require a server reboot?

Yes. Renaming a Windows Server requires a reboot to take effect on the OS level. However, SharePoint services often require manual reconfiguration (like the PowerShell steps above) to recognize the OS-level changes post-reboot.