Our app has been in operation for many years now. In the last week we have started to see some new errors:
System.NotSupportedException: The stream does not support concurrent IO read or write operations.
We are getting this on our dataportal save, and have not seen it before. We are running a Win2008 Server, and use remoting to a winforms client.
Does anyone have suggestions on where we might look?
Thanks!
What is the source of the exception? The database, ADO.NET, remoting?
Looks like it is from Remoting. We have done the patch Tuesday .NET framework patches this week.
Here is the stack trace:
Server stack trace:
at System.Net.ConnectStream.InternalWrite(Boolean async, Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state)
at System.Net.ConnectStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Runtime.Remoting.Channels.ChunkedMemoryStream.WriteTo(Stream stream)
at System.Runtime.Remoting.Channels.StreamHelper.CopyStream(Stream source, Stream target)
at System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessAndSend(IMessage msg, ITransportHeaders headers, Stream inputStream)
at System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Csla.Server.IDataPortalServer.Update(Object obj, DataPortalContext context)
at Csla.DataPortalClient.RemotingProxy.Update(Object obj, DataPortalContext context)
at Csla.DataPortal.Update(Object obj)
at ActiveObjects.DataPortal.Update(Object obj)
at ActiveObjects.ActiveBusinessBase`1.Save()
at RxBusObj.frmAnalyzer.Save()
at Rx.frmAnalyzer.Save(Boolean Rebind)
In that case you probably need to contact Microsoft product support to see what they changed with Remoting...
Copyright (c) Marimer LLC