Hi Alex,
Welcome to the form!
We had replied to this question on the private thread that you had created
earlier today. However, for the benefit of everyone else on this forum, let
me share it here as well. We can continue the discussion on this thread to
avoid duplicates. I ran a test report
Hi:
This is my first post here, and I'll try to adhere to the guidelines but
please forgive if I miss something.
We have developed a year ago PHP code that connects to the AdWords API and
downloads daily some kinds of reports (campaign, adgroup, keyword and ad)
for the accounts of our customer
Hah, funny you should mention that Zweitze - that's exactly what I found
last night.
The AdWords .NET library dev responded in private, offering to help me with
my issue. He suggested I enable .NET tracing to log the raw HTTP requests.
Once I did that, I found an XML response in the trace file
I understand that you use .NET.
When you get a WebException with HTTP 400, do download the response: take
WebException.Response, cast it to HttpWebResponse, then call it's
GetResponseStream() method.
You will find some XML with more info on the problem with the request.
My guess: your code fail
Hello Brett,
I'll ask my colleague to suggest here. We is the author of the DotNet
library and may have more insights about windows environment.
-Danial, AdWords API Team.
On Tuesday, April 15, 2014 8:10:10 AM UTC+4, Brett Rogers wrote:
>
> Danial,
>
> I disabled ECN on my server but still s
Danial,
I disabled ECN on my server but still seeing the same results. I also tried
setting up a brand new machine (VM) and running the task there, but seeing
the same results.
For now I've tried playing around with retries and delays, but that hasn't
seemed to help much either.
Very frustr
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-congest
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
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?
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 d
10 matches
Mail list logo
