We recently became aware of a change in behavior in the .NET framework that affects Azure Managed Cache.

Affected customers may start seeing this error:

Exception message: ErrorCode:SubStatus:The connection was terminated, possibly due to server or network problems or serialized Object size is greater than MaxBufferSize on server. Result of the request is unknown.Additional Information : The client was trying to communicate with the server: net.tcp://YourCacheNameHere.cache.windows.net:25233.

In order to fix this issue, changes are required in the client application. The options for fixing this issue depend on the version of the framework you are using.

1. For clients using .NET 4.0 and above, the best solution is to update the Microsoft.WindowsAzure.Caching NuGet package to version 2.9.0.2 or later.
2. For clients using .NET 3.5 and below, you can set the following registry keys on the client machine to disable the change in behavior.

Add the following in Registry through Regedit:

Registry location: 
HKEY_LOCAL_MACHINESoftwareMicrosoft.NETFramework
DWORD name: SchSendAuxRecord
Value data: 0

And

Registry location: 
HKEY_LOCAL_MACHINESoftwareWow6432NodeMicrosoft.NETFramework
DWORD name: SchSendAuxRecord
Value data: 0

Reminder: Azure Managed Cache and In-Role Cache will be deprecated on 11/30/2016

As part of the announcement last year, we would also like to remind customers that Managed Cache will be shut down and support for In-Role Cache will end on 11/30/2016. We encourage all existing customers to migrate to Azure Redis Cache. For more information on migrating, please visit the Migrate from Managed Cache Service to Azure Redis Cache documentation webpage.