Daily Archives: April 19, 2013

Cache cluster is down, restart the cache cluster and Retry Error–SharePoint 2013

The windows event viewer might have many critical error from Distributed Cache Service. This service will try every 5 min and will throw critical error on the event viewer. The error message may be “Cache cluster is down, restart the cache cluster and Retry “ The root cause of this error may be various reasons. The distributed cache service is very fragile and needs more memory from the server side. Before we Start the Distributed Cache Service please read the article http://technet.microsoft.com/library/jj219572(office.15).aspx The article tells you that we need to enable some firewall ports in the server, especially the application server where the service is running, If multiple servers are running need to start the first server which should have incoming ports to be enabled.

I followed the below procedure, it solved for me, not sure it is the best solution

Remove the Distributed Cache Service using the Powershell command

Stop-SPDistributedCacheServiceInstance -Graceful


Enable the firewall ports in the server for incoming ports for 22233,22234,22235,22236

From the Services in the windows need to Start the Remote Registry service, This service is needed to be running for the Distributed Cache Service. If planning for multiple servers make sure in all servers the service is running

Restart the AppFabric Caching Service from the windows service.

Add the Distributed Cache Service using the PowerShell command


Through Central Administration->System Settings->Manage Services on server now can see the service. Start the Distributed Cache Service.

Install-SPRSService is not Recognized Error–SharePoint 2013 SQL 2012 Reporting Services

Sometime even after you install the SQL Reporting Services in SharePoint Mode to the Application Server you might get the below error

Install-SPRSService : The term ‘Install-SPRSService’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

The reason might be the wrong version of SQL 2012 Reporting Services for SharePoint is installed. For SharePoint 2013 SQL 2012 SP1 is the requirement. In some cases if you have downloaded the SQL 2012 SP1 installer during November 2012 or before there is an issue with Microsoft Site that the SP1 will not be installed. So please download the latest SQL 2012 SP1 installer ISO and install the Reporting Service in SharePoint Mode.


Installing the SP1 with the latest ISO will solve the issue.

Central Admin Warning – InfoPath Forms Services forms cannot be filled out in a Web browser because no State Service connection is configured

After i complete my SharePoint 2013 setup the above mentioned warning appeared in the central administration. The solution is to run the below PS command to fix it

$serviceApp = New-SPStateServiceApplication -Name “State Service”
New-SPStateServiceDatabase -Name “StateService DB” -ServiceApplication $serviceApp
New-SPStateServiceApplicationProxy -Name “State Service” -ServiceApplication $serviceApp –DefaultProxyGroup

Move Search Components To Different Server in SharePoint 2013

SharePoint 2013 Search components are very scalable. Now you can move the components from the search to different servers which it is running. In SharePoint farm environment usually the Application Server will host all the Services including the Search Application services. The Search Application consists of several Search components like

  • Admin
  • Crawler
  • Content Processing
  • Analytics processing
  • Query Processing
  • Index

The movement of the components to another server is not possible from the Central Administration. The Search Topology does not provide any option to move. So these can be done using the PS commands.

Farm before movement


Farm After Movement


Below is the PS script for the activity.

$ssa = Get-SPEnterpriseSearchServiceApplication
$active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active
$clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone –SearchTopology $active

$Srv2 = Get-SPEnterpriseSearchServiceInstance -Identity “Server Name Here
New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $clone -SearchServiceInstance $Srv2
New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $clone -SearchServiceInstance $Srv2
New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $clone -SearchServiceInstance $Srv2
New-SPEnterpriseSearchCrawlComponent -SearchTopology $clone -SearchServiceInstance $Srv2

Start-SPEnterpriseSearchServiceInstance -Identity $Srv2
Set-SPEnterpriseSearchTopology -Identity $clone
Clone again to remove original

$ssa = Get-SPEnterpriseSearchServiceApplication
$active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active
$clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone –SearchTopology $active

Get-SPEnterpriseSearchComponent -SearchTopology $clone  — to get the component id for the subsequent commands

Remove-SPEnterpriseSearchComponent -Identity  COMPID -SearchTopology $clone -confirm:$false
Remove-SPEnterpriseSearchComponent -Identity COMPID -SearchTopology $clone -confirm:$false
Remove-SPEnterpriseSearchComponent -Identity COMPID -SearchTopology $clone -confirm:$false
Remove-SPEnterpriseSearchComponent -Identity COMPID -SearchTopology $clone -confirm:$false

Set-SPEnterpriseSearchTopology -Identity $clone


Replace the Server Name Here with the server you want to move

COMPID i the old component id of the search component to be removed. You can get all component running on the server by using the command

Get-SPEnterpriseSearchComponent -SearchTopology $clone

I followed the post from this blog http://stevemannspath.blogspot.ch/2013/03/sharepoint-2013-search-moving-query.html