Cache Service immediately stops with an error

Question

Immediately after doing Start-CacheCluster, my cache service has already stopped. My application log shows the following pairs of errors:

ERROR1:

Application: DistributedCacheService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.Fabric.Common.ReleaseAssertException
Stack:
   at Microsoft.Fabric.Common.IOCompletionPortWorkQueue.Invoke(System.Threading.WaitCallback, System.Object)
   at Microsoft.Fabric.Common.IOCompletionPortWorkQueue.WorkerThreadStart()
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()

ERROR2:

Faulting application name: DistributedCacheService.exe, version: 1.0.2912.0, time stamp: 0x4bea6d7b

Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdfe0

Exception code: 0xe0434352

Fault offset: 0x000000000000aa7d

Faulting process id: 0x2aa4

Faulting application start time: 0x01cb0808ce054c15

Faulting application path: C:\Windows\System32\AppFabric\DistributedCacheService.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: 13c5102f-73fc-11df-90f5-463500000031

I think everything is configured correctly. Any ideas?

Answer 1

Not sure what happened, but after a stop and then a restart, everything is working fine now.

Answer 2

Can you please give us the exception details in the Windows Event Log. Go to

Applications and Services Logs -> Microsoft -> Windows -> Application Server-System Services -> Admin.

---

Amit. (Velocity Dev, MSFT)

Answer 3

AppFabric Caching service crashed with exception {Microsoft.Fabric.Common.ReleaseAssertException: Async callback System.AsyncCallback failed with exception Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode<ERRCA0009>:SubStatus<ES0001>:Cache referred to does not exist. Contact administrator or use the Cache administration tool to create a Cache.

   at Microsoft.ApplicationServer.Caching.RegionRange..ctor(ReliableServicePartition partition, VelocityDataStore store, ReplicaRole role, Int64 epoch)

   at Microsoft.ApplicationServer.Caching.VelocityDataStore.OnChangeRole(ReliableServicePartition dataRange, ReplicaRole newRole, Int64 epoch)

   at Microsoft.Fabric.Data.PARA.PartitionAgent.ProcessAddPrimary(ParaPartition paraPartition, ConfigurationBody configBody)

   at Microsoft.Fabric.Data.PARA.PartitionAgent.ProcessPartitionMessage(String name, GenerationNumber generationNumber, IPartitionBody body, NodeInfo origin)

   at Microsoft.Fabric.Data.PARA.PartitionAgent.ProcessMessage(String name, GenerationNumber generationNumber, Object body, NodeInfo origin)

   at Microsoft.Fabric.Data.ReliableServiceManager.Microsoft.Fabric.Common.IQueueHandler<Microsoft.Fabric.Federation.IReplyContext>.ProcessItem(IReplyContext context)

   at Microsoft.Fabric.Common.QueueHandler`1.CompleteProcessItem(IAsyncResult result)

   at Microsoft.Fabric.Common.OperationContext.InvokeCallback(AsyncCallback callback, IAsyncResult result)

   at Microsoft.Fabric.Common.ReleaseAssert.Fail(String format, Object[] args)

   at Microsoft.Fabric.Common.OperationContext.InvokeCallback(AsyncCallback callback, IAsyncResult result)

   at Microsoft.Fabric.Common.OperationContext.InvokeCallback(AsyncCallback callback)

   at Microsoft.Fabric.Common.OperationContext.EndOperation()

   at Microsoft.Fabric.Common.ReaderQueue`1.ActivateContext(Object state)

   at Microsoft.Fabric.Common.ReaderQueue`1.Enqueue(T item, Boolean useCurrentThread)

   at Microsoft.Fabric.Federation.FederationSite.DispatchContext(IReplyContext context, Boolean allowMultipleRecipients, MessageFilterTable`1 filterTable, Object filterTableLock)

   at Microsoft.Fabric.Federation.FederationSite.DispatchRoutedMessage(RoutedReceiverContext context)

   at Microsoft.Fabric.Common.IOCompletionPortWorkQueue.Invoke(WaitCallback callback, Object state)

   at Microsoft.Fabric.Common.IOCompletionPortWorkQueue.WorkerThreadStart()

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading.ThreadHelper.ThreadStart()}. Check debug log for more information

Answer 4

Yes this is a known issue and would be fixed in the future releases. If you face this kind of problem again, you can do export-cacheclusterconfig and then import-cacheclusterconfig from the admin tool. Hope this helps.

---

Amit. (Velocity Dev, MSFT)

Answer 5

Just came across this.  It happened right after a database outage.  It seems that something may have caused the config database to become corrupted.  I had previously saved an export of the cache cluster config.  Re-importing that config fixed the problem.  Thanks for the suggestion!