If you are running Appfabric cache service on a Windows 7 machine, one of the most common error you will encounter is
ERROR: Error accessing AppFabric Cache
ErrorCode<ERRCAdmin040>:SubStatus<ES0001>:Failed to connect to hosts in the cluster
FIX: Remote Registry service Fix – If you have Appfabric running on your Windows 7 machine, Remote Registry service is not set to run by default, so start the Remote Registry service, if not started. Appfabric by default uses this service even on local machine, or you have to modify your host file.
Also Restart-CacheCluster using AppFabric Caching Admin PowerShell prompt, after you have started the Remote Registery service.
ERROR : ErrorCode<ERRCA0017>:SubStatus<ES0006>:There is a temporary failure. Please retry later. (One or more specified Cache servers are unavailable, which could be caused by busy network or servers. Ensure that security permission has been granted for this client account on the cluster and that the AppFabric Caching Service is allowed through the firewall on all cache hosts.
Exception Details: System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host.
FIX: This error is generally seen when you try to use Cache client from an IIS web application.
A simple solution will be to grant access for cluster access using Grant-CacheAllowedClientAccount to everyone but this is not a proper solution as it may create other security issues .
The better way is to grant access for cache cluster to a user with admin role.
This command will add Advanced Security Properties to the shared Appfabric ClusterConfig file .
Then change your web application – application pool identity account to the same user who has been granted access for using Appfabric cache cluster .
After changing the configuration you must recycle the application pool .
It is easy to write code for a spec and walk on water, provided, both are frozen.