AF: AppFabric Invalid Version Error
On a clustered environment when you try to start the AppFabric caching service you may encounter the error AppFabric Invalid Version Error.
You will see the following exception logged in the AppFabric event logs
AppFabric Caching service crashed with exception {Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode<ERRService0001>:SubStatus<ES0001>:Service initialization failed. No user action required. ---> Microsoft.Fabric.Common.OperationCompletedException: Operation completed with an exception ---> Microsoft.Fabric.Federation.InvalidVersionException: Node with version: Microsoft.ApplicationServer.Caching.ServerVersionInfo received an abort because of invalid version
You can use the Get-CacheHost command to view the version of the Caching Service on each cache host
The following is the output of the Get-CacheHost command executed on a clustered environment.
| HostName : CachePort | Service Name | Service Status | Version Info |
| CACHESERVER1:22233 | AppFabricCachingService | UP | 3 [3,3][1,3] |
| CACHESERVER2:22233 | AppFabricCachingService | UP | 3 [3,3][1,3] |
| CACHESERVER3:22233 | AppFabricCachingService | DOWN | 3 [1,3][1,1] |
| CACHESERVER4:22233 | AppFabricCachingService | DOWN | 3 [1,3][1,1] |
The Version Info column in this example contains the value 3 [3,3][1,3]. This corresponds to the following version details:
| 3 | The version of the Caching Service running on that cache host. |
| [3,3] | The range of caching service versions that can run on that particular host within the cache cluster during the online upgrade. |
| [1,3] | The range of cache client versions that can use the cache cluster. |
The hosts are running the updated Caching Service with a version of 3. But if we look at the allowed server and client versions there is a mismatch on the server instance CACHESERVER3 and CACHESERVER4.
Use Update-CacheHostAllowedVersions to update the allowed server and client server versions
Below is the command to update the server and client version range.
Update-CacheHostAllowedVersions -BeginServerVersion 3
Update-CacheHostAllowedVersions -EndClientVersion 3
After updating the versions, the caching service started without any issues. The following is the output of the Get-CacheHost command .
| HostName : CachePort | Service Name | Service Status | Version Info |
| CACHESERVER1:22233 | AppFabricCachingService | UP | 3 [3,3][1,3] |
| CACHESERVER2:22233 | AppFabricCachingService | UP | 3 [3,3][1,3] |
| CACHESERVER3:22233 | AppFabricCachingService | UP | 3 [3,3][1,3] |
| CACHESERVER4:22233 | AppFabricCachingService | UP | 3 [3,3][1,3] |
Reference Articles https://msdn.microsoft.com/en-us/library/hh343304(v=azure.10).aspx
Created by
Sakthivel Ramasamy