Hello Steve,

 I've heard back from the engineer who was investigating this, and
they've identified what they believe to be the root cause and have
submitted code for a patch. I'm afraid that I don't know the exact
time that the patched code will be deployed to production, but I
wanted to give you a heads-up that it's in the pipeline.

Cheers,
-Jeff Posnick, AdWords API Team


On Apr 13, 12:29 pm, AdWords API Advisor
<adwordsapiadvi...@google.com> wrote:
> Hello Steve,
>
>  Apologies for the delay in getting back to you. The core engineering
> team has been tracking an internal issue that appears to be triggering
> these responses from the KeywordToolService, but there is no
> resolution at this time. I'll update this thread when I get any
> additional details.
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>
> On Apr 6, 10:38 pm, steveh <st...@eosyn.com> wrote:
>
> > I have a routine that runs against the KeywordToolService multiple
> > times per day (one request every 15 minutes at the moment). On average
> > it succeeds 1-3 times per day and fails all of the rest with this
> > message:
>
> > "There was a problem contacting the site keyword server."
>
> > The header says that it cost 0 units, which implies that it's a Google
> > issue.
>
> > If it failed 100% of the time, I would assume it was a problem on my
> > side, but it works just frequently enough that I don't think that's
> > the case.
>
> > When I run this same routine against the sandbox, it succeeds 100% of
> > the time. Is there anything that I should be looking for or is this
> > something I need to report somewhere?
>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to