Distributed Cache (DC) is one of the new component that is added in SharePoint. It plays an important role in SharePoint server because this is a key component for performance and caching. This Distributed cache is not a SharePoint service but a standalone service called as AppFabric 1.1 for Windows server. This is known as one of the dangerous part of SharePoint in terms of social computing. Though it may not occur an issue while managing Distributed Cache in SharePoint because it is quite comfortable using PowerShell and this is also applied for the same when repairing.
When MinRole SharePoint 2016 server is set up with 9 SharePoint servers then one Distributed cache servers does not behave properly and it gives error “cacheHosInfo is null”. Even it is said that “Distributed cache host may have cause the cache reliability problems”. However there are multiple servers farm and so Distributed cache can run only 1 server in the farm. But actually when use-CacheCluster command is run on one of the SharePoint servers then the below mentioned error is received.
Use-CacheCluster : ErrorCode<ERRPS001>:SubStatus<ES0001>:Error in reading
Well the cause of this error states that the server is not able to read and get the values of the connection string. However the information is from AppFabric and when Distributed Cache service is not running on server then make sure it is because of the error as the server is not able to communicate to AppFabric. Well to check where the Distributed cache is running on which server, some process can be done.
In SharePoint, open PowerShell and then run the below mentioned command:
After running the above command, only one server is returned where DC is running and the problem is seen.
Well everything is in front as expected but when you want to access the Distributed cache from all servers in farm so you have to allow provision the DC instance on every server in farm. Here some of the ways to fix are mentioned.
Now nothing to be done except leaving it. If you want to run this command then you have to login on server where Distributed cache is running and then run it.
After that login on server where you have allowed the DC
Now open PowerShell and then run the below command:
Now install the Distributed cache instance on server in farm and then stop it, though it may look some odd type but it works. After that run the below mentioned command on server where you have to run the DC.
Following the above command successfully supplies Distributed Cache service instance on server and after that start the service and again run the below mentioned command:
Following the command will only stop the DC on server but will not remove it. Now when you run:
Now as you can see the DC is up on the server where you run it and down on server that you want it.
How to fix the error
Well when any type of error occurs in SharePoint then it becomes inaccessible and it needs to be repaired. However when all the above option does not work to fix the issue then use of third party tool like SharePoint File Repair Tool will help you to fix the error. This is one of the best software which completely works in repairing SharePoint database. It allows administrators or users to extract SharePoint databases such as documents, table, indexes, labels, media files and other objects from inaccessible MDF files.
Steps to Repair Errors in SharePoint Database
Step 1 – Download and Install SharePoint File Repair Tool on your system. Launch the software and you will see the interface and shown in the image below. You can select either ‘Complete Repair’ or ‘Document Recovery’.
Step 2 – With ‘Complete Repair’, the screen shows options to select and find SQL Server (.MDF) files. Use ‘Search File’ option if you don’t know actual path of the database. Now click on ‘Scan’ to start scanning.
Step 3 – Once the scan process complete, the tool will create a tree of all SharePoint database tables will be demonstrated in the left pane. The sample will be in the right pane. Now click on ‘Repair’ to inaugurate repairing for preferred database.
Step 4 – When you click on ‘Repair’, the below dialog box will get displayed. Specify the SQL Server name/Instance name and the desired destination path. Click ‘Browse‘ to select the destination path. Click ‘OK‘.
Step 5 – After completion of the process, a message will be displayed like ‘Recovered file saved at the desired location’. Now hit ‘OK’ button.
Step 6 – Another dialog box will ask you to attach repaired database to the web application. If you click ‘Yes’ button then below dialogue box will appear. Now enter application URL, name of the damaged database and SQL server instance name and then continue by pressing ‘OK’. When it’s done, repaired database will be available.