Received an unexpected EOF or 0 byte s from the transport stream.

Sep 11, 2014 at 12:45 PM
I am opening stream for so intensive keyword (example for debugging "a" keyword) after a while I am getting that error. What is the cause of this error and How can I solve this error?

Thank you...

Error:

Unhandled Exception: System.IO.IOException: Received an unexpected EOF or 0 byte
s from the transport stream.
at System.Net.ConnectStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.Http.DelegatingStream.Read(Byte[] buffer, Int32 offset, Int32 c
ount)
at System.Net.Http.HttpClientHandler.WebExceptionWrapperStream.Read(Byte[] bu
ffer, Int32 offset, Int32 count)
at System.Net.Http.DelegatingStream.Read(Byte[] buffer, Int32 offset, Int32 c
ount)
at System.IO.Compression.DeflateStream.Read(Byte[] array, Int32 offset, Int32
count)
at System.IO.Compression.GZipStream.Read(Byte[] array, Int32 offset, Int32 co
unt)
at System.IO.Stream.ReadByte()
at LinqToTwitter.TwitterExecute.<QueryTwitterStreamAsync>d__15.MoveNext() in
d:\Programming\SMB\SMB\linqtotwitter-00c9d369449805e8bde1698146432770ac45f431\Li
nqToTwitterPcl\LinqToTwitter\TwitterExecute.cs:line 202
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNot
ification(Task task)
at LinqToTwitter.TwitterContext.<ExecuteAsync>d__da1.MoveNext() in d:\Progra
mming\SMB\SMB\linqtotwitter-00c9d369449805e8bde1698146432770ac45f431\LinqToTwitt
erPcl\LinqToTwitter\TwitterContext.cs:line 415
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNot
ification(Task task)
at LinqToTwitter.TwitterQueryProvider.<ExecuteAsync>d__6
1.MoveNext() in d:\P
rogramming\SMB\SMB\linqtotwitter-00c9d369449805e8bde1698146432770ac45f431\LinqTo
TwitterPcl\LinqToTwitter\TwitterQueryProvider.cs:line 140
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNot
ification(Task task)
at LinqToTwitter.TwitterExtensions.<ToListAsync>d__4`1.MoveNext() in d:\Progr
amming\SMB\SMB\linqtotwitter-00c9d369449805e8bde1698146432770ac45f431\LinqToTwit
terPcl\LinqToTwitter\TwitterExtensions.cs:line 33
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNot
ification(Task task)
at LinqToTwitter.TwitterExtensions.<StartAsync>d__0.MoveNext() in d:\Programm
ing\SMB\SMB\linqtotwitter-00c9d369449805e8bde1698146432770ac45f431\LinqToTwitter
Pcl\LinqToTwitter\TwitterExtensions.cs:line 26
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNot
ification(Task task)
at SMB.TwitterKeywordTracking.TwitterKeywordTrackManager.<startTracking>d__7.
MoveNext() in d:\Programming\SMB\SMB\SMB.TwitterKeywordTrackManager\TwitterKeywo
rdTrackManager.cs:line 91
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__1(Ob
ject state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionCo
ntext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, C
ontextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWor
kItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
Coordinator
Sep 11, 2014 at 11:41 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.