The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error

davido posted on Friday, February 06, 2009

CslaLight I occassionaly get this error but I do not know the cause. Does anyone else experience this?

{System.ServiceModel.CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.
   at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.ClientBase`1.ChannelBase`1.EndInvoke(String methodName, Object[] args, IAsyncResult result)
   at Csla.WcfPortal.WcfPortalClient.WcfPortalClientChannel.EndFetch(IAsyncResult result)
   at Csla.WcfPortal.WcfPortalClient.Csla.WcfPortal.IWcfPortal.EndFetch(IAsyncResult result)
   at Csla.WcfPortal.WcfPortalClient.OnEndFetch(IAsyncResult result)
   at System.ServiceModel.ClientBase`1.OnAsyncCallCompleted(IAsyncResult result)}

RockfordLhotka replied on Friday, February 06, 2009

Are you exceeding the max size of data transfer?

davido_xml replied on Tuesday, February 10, 2009

No. I am in control of the database and query criteria so I know what's expected. Doing a browser F5 will perform the exact same set of WCF communications and will 90% of the time work. It is just the occassional exception.

RockfordLhotka replied on Tuesday, February 10, 2009

And this is against IIS, not the dev web server (Cassini)? I know there are some issues with Cassini that can cause sporadic WCF failure (though usually under load).

davido replied on Tuesday, February 10, 2009

I have been using Cassini. I will swap over to IIS and keep an eye on it.