Home/ Questions/Q 7543583
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T08:27:57+00:00

We have a 3 machine cache cluster running with SQL configuration provider. The service

  • 0

We have a 3 machine cache cluster running with SQL configuration provider. The service is running under a domain account on the cache hosts (We are not using Security). The SQL server is also running under the a domain user account. We had issues with caching service running under Network Service and could not connect to SQL at all. But this configuration allowed the cluster to be up and running smoothly.

There are 2 types of cache clients. One of the cache clients is a native c++ exe running under the same domain account that the cache service runs on. These cache clients are on different machines. All such clients can successfully connect to the cache host.

The second type of a cache client is a .NET web application that runs under Network Service. This client is unable to write/fetch anything into the cache host. It is able successfully initialize the cache factory but fails with :

`Creating Region for general use in default cache

Error in Cache Call : ErrorCode<ERRCA0017>:SubStatus<ES0001>:There is a temporary     failure. Please retry later. : http://go.microsoft.com/fwlink/?LinkId=164049
at Microsoft.ApplicationServer.Caching.DataCache.ThrowException(ResponseBody respBody)
at Microsoft.ApplicationServer.Caching.DataCache.CreateRegion(String region)
at CacheAPISample.Program.CreateRegion(String myRegion)
at CacheAPISample.Program.RunSampleTest()
at CacheAPISample.Program.Main(String[] args)`

From the error description there is no indication of what kind of error would this be. I have made sure the domain\clientmachinename$ is a allowed cache client. Security and Protection are turned off. Firewall rules are enabled (Given client type 1 can successfully call, firewall is ruled out as an issue).

So far I have tried:

  1. Running sample tests with a domain user from client type 2. And also making sure the domain user is a allowed cache client.

  2. Host mapping the cache server.

What should I do to get down to the actual root cause of the error? The logs at the cache hosts are clean. There are no errors.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Just as a followup, I believe this was partly resolved by ensuring that the client system could resolve the AppFabric server by machine name (using etc/hosts hack) not by FQDN. This appears to be a known issue out there. Unfortunately the error message is the same for this and other real failures.

    • 0