Hello Brett,
There is a known issue with ECN turned on by default. Please try the following on your server: netsh interface tcp set global ecncapability=disabled as described here: http://social.technet.microsoft.com/wiki/contents/articles/20204.how-to-enable-and-disable-explicit-congestion-notification-in-windows.aspx Please let us know if this resolves your issue. -Danial, AdWords API Team. On Wednesday, April 9, 2014 10:38:41 PM UTC+4, Brett Rogers wrote: > > Danial, > > Yes, we are using Windows (and C#, for what it's worth). > > I'm pretty confident that it's not a network issue given the fact that > this machine runs quite a few different network-involved processes, > including hosting a database, and none of those processes have been seen > network-related issues. > > > On Wednesday, April 9, 2014 5:46:50 AM UTC-7, Danial Klimkin wrote: >> >> Hello Brett, >> >> >> Generally, you should receive a meaningful error from the API for the >> cases when you are rate limited. >> >> Bad Request often means the request was not send in full (unless it was a >> really malformed request). Most likely this is a network issue. >> >> Are you running on a windows platform? >> >> >> -Danial, AdWords API Team. >> >> >> On Tuesday, April 8, 2014 10:29:59 PM UTC+4, Brett Rogers wrote: >>> >>> Scenario: >>> >>> We have a daily task that downloads AdWords AdHoc reports for our MCC >>> account's accounts, campaigns, ad groups, and ads to synchronize them with >>> 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 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 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 complete everything and API requests will also work, >>> i.e., the same auth credentials work elsewhere, just not from that computer. >>> >>> Ideas? Are we running into some kind of IP or computer-based quota? >>> >>> FYI - we're using the latest API version - v201402, but the problem was >>> also occurring with v201309 before we recently upgraded. >>> >> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/d/optout.
