Application Server: The Caching Service should be started
Applies To: Windows Server 2008 R2, Windows Server 2012
This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the Application Server Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer.
Windows Server 2012
Windows Server 2008 R2
Application Server role
The AppFabric Caching Service has not been started.
This server cannot be used by a cache cluster if the Caching Service is not running.
The Caching Service of the AppFabric role service of the Application Server role enables you to implement an in-memory cache platform to store frequently used application data. Each server that runs the Caching Service is referred to as a cache server, and all cache servers that run the Caching Service can be configured as nodes of a cache cluster that is available as a single unified memory cache. Instances of the Caching Service on the cache servers of the cache cluster work together to store and distribute data in the cache.
If the Caching Service on a cache server is not started, that server cannot be a working member of the cache cluster.
Start the Caching Service.
To start the Caching Service
Start-CacheHostto start the Caching Service on the cache host. For more information, see Start-CacheHost (http://go.microsoft.com/fwlink/?LinkId=199820).
To start the Caching Cluster
- If no cache hosts are up in the cache cluster, execute
Start-CacheHost. For more information, see Start-CacheCluster (http://go.microsoft.com/fwlink/?LinkId=199822).
To start the Caching Cluster for the First Time
- After installation for the first time, you will need to start the cache cluster. Configure at least one node in the cluster, and then execute a cmdlet to start the cluster. In the developer scenario (using a single-node cluster), to start a new cluster execute
Use-CacheCluster(to set the context of your Windows PowerShell session to a particular cache cluster) and then execute
Start-CacheCluster. In a multiple-node cluster, to start all cache host services in the cluster (lead hosts first), execute
Start-CacheCluster. For additional cache hosts (and any other cluster-level configuration changes) to be acknowledged by the cache cluster, you need to restart all cache host services with
Restart-CacheCluster. To start a specific cache host service, execute