AppFabric helps IT professionals to build scalable web applications on IIS. It consists of hosting and caching features. In this post, I will mention some possible solutions to AppFabric Caching Service crashes.
AppFabric Caching architecture (Source)
If the caching has issues, check the Event Viewer logs in the containers below:
In the Event Viewer logs, it is likely that you will see one or more of these error messages:
Event ID 111: AppFabricCachingService.Crash Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode:SubStatus:Service initialization failed. No user action required. Event ID 6: 30ecac98000000000000000000000000 Microsoft.Fabric.Common.OperationCompletedException: Operation completed with an exception —> System.TimeoutException: The operation has timed out.
Some findings and fixes are below. Each of them can be implemented individually.
Make sure the AppFabric Caching service uses a managed account (Instructions).
Best practice for the Caching service account:
A single account should be used for all Service Applications, named Service Application Pool account. This allows the administrator to use a single IIS Application Pool for all Service Applications. In addition, this account should run the following Windows Services: SharePoint Search Host Controller, SharePoint Server Search, and Distributed Cache (AppFabric Caching Service).
NT Authority\System on the SQL AppFabric Database should have Data Reader / Data Writer permissions.
Also, in PowerShell, execute
Grant-CacheAllowedClientAccount command for
NT Authority\System account.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.