Object reference exception - WeOnlyDo Discussion board

Object reference exception (wodFtpDLX / wodFtpDLX.NET)

by Emre Ozer, Wednesday, March 17, 2010, 09:26 (5366 days ago)

We're constantly getting an unhandled object reference not set to an instance of an object exception from time to time. Here are the details:

Assembly Info:
{WeOnlyDo.Client.FTP, Version=1.3.0.119, Culture=neutral, PublicKeyToken=e066bfc6dc58a05b}


StackTrace:

at . . ( , Exception )
at . . (IAsyncResult )
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
at System.Net.FixedSizeReader.ReadCallback(IAsyncResult transportResult)
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Net.ContextAwareResult.CompleteCallback(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.ContextAwareResult.Complete(IntPtr userToken)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)


Exception logged in our application before breaking:
Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request.

Dees anybody have an idea?

Thanks,

Emre


Complete thread: