Thanks Anash, I will try this!
On Friday, December 9, 2016 at 12:26:25 PM UTC-8, Anash P. Oommen (AdWords
API Team) wrote:
>
> Hi Caihua,
>
> Could you try increasing the timeout in the .NET client library using the
> Timeout setting in App.config? See
> https://github.com/googleads/googleads-d
Hi Caihua,
Could you try increasing the timeout in the .NET client library using the
Timeout setting in App.config?
See
https://github.com/googleads/googleads-dotnet-lib/wiki/Understanding-App.config#general-library-behavior
for details.
The error you get could be due to a server somewhere u
Hi Anthony,
Do you have any update? We saw new failures today in which the IO
connection get terminated after 5 mins while we are downloading report
file. Please let us know if this is expected or not. Thank you!
Caihua.
On Wednesday, December 7, 2016 at 10:19:32 PM UTC-8, Caihua Du wrote:
>
>
Hi Anthony,
No, we didn't make changes to the deployment environment. This issue is not
100% repro, and if the download time is more than 5 min, the connection
seems get force closed. Is this expected?
Thank you!
Caihua.
On Wednesday, December 7, 2016 at 2:42:36 PM UTC-8, Anthony Madrigal wrot
Hi Caihua,
This may be a network related issue on your side. Have you made any changes
to the hosts where your app is deployed such as upgrading the .NET runtime
recently or changing some values in your App.config/Web.config file?
Regards,
Anthony
AdWords API Team
--
--
=~=~=~=~=~=~=~=~=~=~=
if there is any other
values controlled from the server side to override the value I set in the
request?
System.Net.Sockets.SocketException: An existing connection was forcibly
closed by the remote host
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32
size
arted the following
>> error part of the way through the process:
>>
>> - The remote server returned an error: (400) Bad Request.
>>
>> Once this error occurs on the main daily task computer, we see the
>> following:
>>
>> - AdHoc Reports requests
dHoc Reports requests initiated from that computer fail after a handful
> of requests
> - AdWords API requests initiated from that computer fail with this error:
> -- An existing connection was forcibly closed by the remote host
>
> BUT, if we then launch this same daily task from anoth
>>>> our local database. We have multiple accounts in our MCC and each account
>>>>> has large quantities of ad groups, so we download quite a bit of data.
>>>>> This
>>>>> process worked great until a few weeks ago, when we started the foll
go, when we started the following
>>>> error part of the way through the process:
>>>>
>>>> - The remote server returned an error: (400) Bad Request.
>>>>
>>>> Once this error occurs on the main daily task computer, we see the
>>>
uest.
>>>
>>> Once this error occurs on the main daily task computer, we see the
>>> following:
>>>
>>> - AdHoc Reports requests initiated from that computer fail after a
>>> handful of requests
>>> - AdWords API requests initiated from
rs on the main daily task computer, we see the
>> following:
>>
>> - AdHoc Reports requests initiated from that computer fail after a
>> handful of requests
>> - AdWords API requests initiated from that computer fail with this error:
>> -- An existing connection was
te server returned an error: (400) Bad Request.
>
> Once this error occurs on the main daily task computer, we see the
> following:
>
> - AdHoc Reports requests initiated from that computer fail after a handful
> of requests
> - AdWords API requests initiated from that computer fai
uests initiated from that computer fail after a handful
of requests
- AdWords API requests initiated from that computer fail with this error:
-- An existing connection was forcibly closed by the remote host
BUT, if we then launch this same daily task from another computer, it will
successfully com
14 matches
Mail list logo
