If you’re using Windows Server AppFabric caching and have recently updated to version 1.8 of the Windows Azure SDK, you might be running into some difficulty in connecting to the caching instance.
I started receiving this error when trying to access the cache:
ErrorCode<ERRCA0019>:SubStatus<ES0001>:Check the client version. It should be within the allowed version range on the server. If necessary, upgrade the client to the allowed version.
After a ton of investigation, the fix was really easy: remove all caching SDK assembly references (Microsoft.ApplicationServices.*) and replace it with the Windows Azure Shared Caching NuGet package:
That should clear that error right up.
Resources and References
While these all didn’t pertain to my end solution, these are the various sources that helped shed some light on the issue:
- StackOverflow: Client Version Error after installing Azure 1.8
- MSDN: Migrate from AppFabric Caching to Windows Azure Caching
- MSDN: Migrate from Windows Azure Caching 1.7 (Preview) to Caching (Released) 1.8
- Scott Hanselman’s Computer Zen: Installing, Configuring and Using Windows Server AppFabric and the “Velocity” Memory Cache in 10 minutes
- Visual Studio Developer Center: AppFabric Cache: getting ErrorCode<ERRCA0016>:SubStatus<ES0001> continuously
- Visual Studio Developer Center: Troubleshooting AppFabric Scaling Issues (Intermittent ErrorCode<ERRCA0017>:SubStatus<ES0006> Errors)
- MSDN: How to: Configure a Cache Client Programmatically (Windows Azure Shared Caching)