Troubleshooting

Unable to Start Cache due to Disabled Network Card

You may not be able to start the cache or clients may be unable to connect with server even on local machine. These problems arise when network card is disabled or cable is not connected.

Workaround

  • To resolve this problem, make sure that the network card is enabled and the network cable is connected.

  • Restarting NCache Service will rebind it to local host rather than IP address of that machine. Restart NCache Service using Windows PowerShell. Make sure you have enough privileges to restart the service. If the user is not the part of the Administrator's group, make sure to run Windows PowerShell as administrator, otherwise you might get an error message that "Cannot open ncachesvc service on computer".

Execute the following command to restart NCache Service:

Restart-Service -Name NCacheSvc

Nodes Not Joining with Cluster on Cache Start

Sometimes it may be the case when you start a clustered cache, but nodes do not join with each other. It means that cluster is not formed and cache runs on each node as a standalone cache. You can use Get-Caches cmdlet to confirm if the cluster is formed properly or not. Use the following command to make sure that the cluster is formed.

Get-Caches -Detail

Workaround

  • Please see that the cache configuration on each node contains the correct initial hosts list. Every node participating in the clustered cache must be listed there. If the server list is not correct then update the server list and restart NCache Service using Windows PowerShell. Make sure you have enough privileges to restart the service. If the user is not the part of the Administrator's group, make sure to run Windows PowerShell as administrator, otherwise you might get an error message that "Cannot open ncachesvc service on computer".

Execute the following command to restart NCache Service:

Restart-Service -Name NCacheSvc

  • See that every node can be accessed from every other node participating in the clustered cache. For this you can use the ping utility. If nodes are not accessible then there is some network problem and must be resolved before starting the cache.

  • Make sure that Windows Firewall is disabled on all nodes. This can be done using the telnet utility. Use the following command using Command Prompt to use the telnet utility.

telnet <ip-address> <port>

Following is an example of a telnet command.

telnet 20.200.20.30 8250

Cache is not registered on the server

When you perform any managerial operation on the cache and error message displayed says that the cache is not registered on the cache there must be some problem in the cache configurations.

Workaround

You can use Get-Caches cmdlet to see which caches are registered on the server. If the cache name is not in the list, verify that the cache is registered on the correct server with the correct name properly through the configuration file.

Get-Caches -Detail

NCache service could not be contacted on server

On running any PowerShell cmdlet the user may be prompted with this error message.

Workaround

  • Make sure that NCache service is running. If it is not running start NCache Service using Windows PowerShell. Make sure you have enough privileges to start the service. If the user is not the part of the Administrator's group, make sure to run Windows PowerShell as administrator, otherwise you might get an error message that "Cannot open ncachesvc service on computer".

Execute the following command to start NCache Service:

Start-Service -Name NCacheSvc
  • Make sure that the server nodes are properly mentioned under the <servers> tag in the client.ncconf. Specifying the server node outside the tag may cause this error to occur.

Failed to start service 'NCache (NCacheSvc)'

You can receive the message " Failed to start service 'NCache (NCacheSvc)'" on starting NCache Service.

Workaround

Make sure that the cache is properly registered on the server. The tags in config.ncconf must be properly opened and closed in order to register the cache(s) on the server. Start the NCache Service once the configurations have been updated.

See Also

Set Up PowerShell Environment
Export-Cache​Data
Export-Cache​Keys
Stop-Cache
TroubleShooting