RTM exception – connection was terminated, possibly due to server or network problems or serialized

This is another one of those random errors I received while testing my app running with AppFabric Cache RTM version My app is a simple C# .NET 3.5 application running under .NET 4 Integrated Pipeline on Windows 2008 R2.

This particular error shown below hasn’t happened as often as the one described here I’m surprised to see these random errors with
only 1 web server and 1 person hitting it.

Error Msg:
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.

Source: Microsoft.ApplicationServer.Caching.Client

Stack Trace: at Microsoft.ApplicationServer.Caching.DataCache.ThrowException(ResponseBody respBody) at Microsoft.ApplicationServer.Caching.DataCache.InternalPut(String key, Object value, DataCacheItemVersion oldVersion, TimeSpan timeout, DataCacheTag[]
tags, String region) at Microsoft.ApplicationServer.Caching.DataCache.Put(String key, Object value, TimeSpan timeout) at Microsoft.ApplicationServer.Caching.DataCacheSessionStoreProvider.SetAndReleaseItemExclusive(HttpContext context, String id, SessionStateStoreData
item, Object lockId, Boolean newItem) at System.Web.SessionState.SessionStateModule.OnReleaseState(Object source, EventArgs eventArgs) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep
step, Boolean& completedSynchronously)

Target: Void ThrowException(Microsoft.ApplicationServer.Caching.ResponseBody)


Please refer to my answer to the thread:http://social.msdn.microsoft.com/Forums/en-US/velocity/thread/3e4a3b81-717e-4573-acef-37cc43beee66http://social.msdn.microsoft.com/Forums/en-US/velocity/thread/47a5222a-d746-43e2-b313-47b0d1da404a/

this error stopped after I put the application  pool from .net 4 to .net 2 

Are you using the same build version for appfabric cache   client and server? Please check in case you were using old client bits.ThanksShankar