Hi Danial,

So after some investigation, here is the exception that we see (we're using 
.NET API). Any ideas why this would be happening?

System.Net.WebException: The underlying connection was closed: An 
unexpected error occurred on a send. ---> System.IO.IOException: *Unable to 
read data from the transport connection: An existing connection was 
forcibly closed by the remote host. ---> 
System.Net.Sockets.SocketException: An existing connection was forcibly 
closed by the remote host*
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, 
Int32 size)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, 
Int32 size)
   at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, 
Int32 count)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, 
AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 
count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean 
receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult 
lazyResult)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext 
executionContext, ContextCallback callback, Object state, Boolean 
preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext 
executionContext, ContextCallback callback, Object state, Boolean 
preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext 
executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication
    ...
   at *ReportUtils.ReportUtilities.DownloadReportToStream*()

This is affecting our users. Will appreciate help!

Manas

On Thursday, December 19, 2013 3:44:56 PM UTC+5:30, Klimkin wrote:
>
> Hi MG,
>
>
> From our side, we haven't caught any alerts. Most likely it was limited to 
> your ISP / network as we had no other reports of the issue.
>
>
> -Danial, AdWords API Team.
>
>
> On Tuesday, December 17, 2013 9:50:02 AM UTC+4, AdWordsApiUser wrote:
>>
>> We've been noticing intermittent connectivity issues to API reports 
>> servers v201309 for the last 24 hours or so. We can't reach the server for 
>> a few minutes, and then it is back up. Seems to happen from all our 
>> locations at the same time (US + Asia), and every few hours. Anyone else 
>> seen this or any known issues going on right now?
>>
>> Thanks!
>> MG
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to