Read carefully when you catch this error “ErrorCode<ERRCA0017>:SubStatus<ES0006>:There is a temporary failure.”, because in our case it was a misconfigured AD Kerberos Service Principal Name for the service account which runs the Distributed Caching Service.
In that case you get the above mentioned error with at some point in the stacktrace the message “The target principal name is incorrect.”, you are in the same situation as we were.
Unexpected error occurred in method ‘GetObject’ , usage ‘Distributed Logon Token Cache‘ – Exception ‘Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode<ERRCA0017>:SubStatus<ES0006>:There is a temporary failure. Please retry later. (One or more specified cache servers are unavailable, which could be caused by busy network or servers. For on-premises cache clusters, also verify the following conditions. Ensure that security permission has been granted for this client account, and check that the AppFabric Caching Service is allowed through the firewall on all cache hosts. Also the MaxBufferSize on the server must be greater than or equal to the serialized object size sent from the client.) —> System.ServiceModel.Security.SecurityNegotiationException: A call to SSPI failed, see inner exception. —> System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. —> System.ComponentModel.Win32Exception: The target principal name is incorrect.
You might try the path of verifying all settings and timeouts.
PS C:\Users\srvcspinstall> Get-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCache
ChannelInitializationTimeout : 60000
ConnectionBufferSize : 131072
MaxBufferPoolSize : 268435456
MaxBufferSize : 8388608
MaxOutputDelay : 2
ReceiveTimeout : 60000
ChannelOpenTimeOut : 2000
RequestTimeout : 2000
MaxConnectionsToServer : 6
PS C:\Users\srvcspinstall> Get-CacheAllowedClientAccounts