SharePoint 2013 Configuration – Failed to connect to host in the cluster

I’ve been spending a little bit of time around SharePoint 2013 and have been probing the various installation methods and came across this problem twice sp far while trying to configure SharePoint 2013 Farms.

Connect-SPConfigurationDatabase : ErrorCode<ERRCAdmin040>:SubStatus<ES0001>:Failed to connect to hosts in the cluster

There are some posts out there that suggest that you can circumvent this problem by Creating or Connecting to your configuration database with the –SkipRegisterAsDistributedCacheHost parameter, however this will result in the Distributed Cache Service Instance being absent from your farm, and I have at this stage been able to get it to reappear.  As it is pretty early in the game for SharePoint 2013 I am not yet sure the impact that not having a Distributed Cache Service will have on your farm, however it will likely be negative.

What seems to be causing this particular problem is an alias being used for the SQL Server, when your SQL Server is on another server.  Re-running the command or trying to establish your farm with the server name instead of the alias seems to avoid the problem.

Hopefully this post will help a few folks avoid a frustrating problem.

Note : This is not a solution, it is just a work around that might avoid frustrating and let you test out SharePoint 2013.


One Response to SharePoint 2013 Configuration – Failed to connect to host in the cluster

  1. Pingback: Microsoft Premier Field Engineer - SharePoint Dev

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: