, August 13, 2012 11:45:09 AM UTC-5, Oliver wrote:
>
> Hi Tim, do you mind sharing which object is the one that actually needs
> caching instead?
>
> Oliver
>
> On Monday, August 13, 2012 5:00:02 PM UTC+1, tozor wrote:
>>
>> After looking at the source of the Ad
large number of users, this quick reply is very much appreciated!
Tim
On Monday, August 13, 2012 9:24:01 AM UTC-5, tozor wrote:
>
> Thanks for the quick reply. We are using the Adwords java client library,
> the call that is failing is:
>
ommend either switching to OAuth2.0 or
> storing and re-using AuthTokens. See this article for more details:
>
>
>
> http://adwordsapi.blogspot.com/2010/07/discover-v2009-working-with-authtokens.html
>
>
>
> -Danial, AdWords API Team.
>
>
> Original Message Fo
After some more research, the problem is that we are frequently getting the
following error returned:
com.google.api.adwords.lib.utils.v201109.ReportException: Could not obtain
AuthToken
which in turn is being caused by
Caused by: com.google.api.adwords.lib.AuthTokenException: Auth token cou
We also started seeing this error about 5 or 6 days ago. We manage
hundreds of accounts in our application and have seen this on a small
subset of the accounts. Also for us, if you go into one of these accounts
in the Adwords UI and click on the reports link, you get an ugly red
warning messa
We are seeing API login failures across numerous accounts (accounts that we
access everyday and have done so for long periods of time). Basically we
are getting CLIENT_EMAIL_INVALID. This started happening about 7AM CST this
morning.
Is this a known problem? Anyone else seeing this all of a
The problem cleared up for me a couple of hours after I posted. This
type of issue causes a bunch of operational headaches for my
application since I can't get any keyword performance data for the
account when it is in this pending forever mode. It happens very
infrequently, however it would be nic
same for my application. We manage many dozens of Adwords accounts, and
it only seems to be happening on a couple of them.
Thanks in advance.
Tim
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.goo
g.
>
> Best,
> - Eric
>
> On Jul 28, 10:52 pm, tozor wrote:
>
>
>
> > Thanks much Eric. One comment I would make is that the Account
> > Structure report is not a complete replacement for the zero impression
> > keyword report because of the fact that first
ile this job may be
> currently succeeding in this configuration, since it is over the
> limits it might start failing at any time. I would refer you back to
> my original advice to either segment your data or use the Account
> Structure report to get this information instead.
>
> Be
> requestId?
>
> Thanks,
> - Eric
>
> On Jul 27, 2:28 pm, tozor wrote:
>
>
>
> > I made a request with all 106 campaigns and it worked. Here is the
> > request id:
>
> > ad94b71784836c3a7cfdc6ff2315435b
>
> > Once again thanks very much fo
tains 106 campaigns, if you count the
> deleted ones, but your second request only includes 75 campaigns. I
> believe these extra campaigns are causing the report to be over the
> size limit.
>
> Best,
> - Eric
>
> On Jul 26, 2:01 pm, tozor wrote:
>
>
>
> >
ds of the requests used to schedule these
> reports (the one that fails and the one that succeeds). Perhaps that
> will shed some light on the issue.
>
> Best,
> - Eric
>
> On Jul 23, 5:53 pm, tozor wrote:
>
>
>
> > I appreciate the reply, but doesn't it
ed. Alternatively, you can remove the
> zero impression option, and use the Account Structure Report to fetch
> information about all of the keywords in the account.
>
> Best,
> - Eric
>
> On Jul 23, 8:33 am, tozor wrote:
>
>
>
> > This remains an issue f
.
Tim
On Jul 13, 7:20 pm, tozor wrote:
> When I notice the problem it is for azeroimpressionreport for the
> current day.
>
> Tim
>
> On Jul 13, 5:55 pm, AdWords API Advisor
> wrote:
>
>
>
> > Hi Tim,
>
> > Are you noticing this for one day in p
s API Team
>
> On Jul 12, 9:27 am, tozor wrote:
>
>
>
> > I get the following unexpected error when trying to run a zero
> > impression keyword report:
>
> > AxisFault
> > faultCode: {http://schemas.xmlsoap.org/soap/envelope/}
> > Server.userExc
I get the following unexpected error when trying to run a zero
impression keyword report:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}
Server.userException
faultSubcode:
faultString: Including Zero Impression Keywords will make your report
too large to run. To include this d
I am seeing similar behavior on some of the accounts I am running
reports against. Most reports run fine but the occasional report
stays in the pending state for a very long period of time,
occasionally transitioning to the "in progress" state and then back to
"pending".
Tim
On Jun 8, 9:39 a
issue and working to resolve
> it as soon as possible. Unfortunately I don't have any further
> information at this time.
>
> Best,
> - Eric Koleda, AdWords API Team
>
> On Apr 28, 11:01 am, tozor wrote:
>
>
>
> > We have an application that manages around
We have an application that manages around 50 separate Adwords
accounts via the API. We pull reports for each account multiple times
a day and most reports take one or two minutes for small accounts and
around 10 to 15 minutes for the very large accounts. Today however I
am seeing reports for man
on what
attribute(s) you are updating.
Thanks again.
Tim
On Aug 21, 11:39 am, AdWords API Advisor
wrote:
> Hi Tozor,
>
> Thank you for taking the time to get me a RequestId, as it helps me
> immensely when trying to track down an issue. Including this
> information in the faul
interested to
know.
Hopefully you can shed some light on why I am getting this concurrency
error.
Thanks.
Tim
On Aug 20, 11:52 am, tozor wrote:
> How do I get at the request ID? Is there some sort of logging I am
> supposed to enable? Assuming that your answer is yes, can I make a
>
I can get more information about
> these errors you are running up against. Can you please send me the
> Request ID of an updateCriteria request that generated the error?
>
> Thanks,
> - Eric Koleda, AdWords API Team
>
> On Aug 19, 9:29 am, tozor wrote:
>
> > I seem to be ab
I seem to be able to trigger the following error in Adwords
consistently when I update multiple destination URLs via the V13
updateCriteria method:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}
Server.userException
faultSubcode:
faultString: The Attempted modification failed
eeing this error across multiple accounts. It only
> > started after Saturday's maintanence.
>
> > -NS
>
> > On Aug 10, 12:15 pm, tozor wrote:
>
> > > After the Adwords maintenance on Saturday, I started noticing an error
> > > on any API operation to a cou
After the Adwords maintenance on Saturday, I started noticing an error
on any API operation to a couple of accounts that our application
manages:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}
Server.userException
faultSubcode:
faultString: The specified account is inactive.
Feel free to ask about some of this sort of thing in the general
> AdWords help center as well, as I usually just rely on empirical
> testing when it comes to AdWords functionality not directly related to
> the API.
>
> http://www.google.com/support/forum/p/AdWords
>
>
I am having a situation in my application where I have keywords in my
application database which at one time existed in Adwords, but now no
longer exist. By no longer exist I mean that when I call getCriteria
() null is returned. Also the keyword is no longer returned in a
zero impression keywo
I saw this last night and again this morning. Different accounts each
time.
Tim Ozor
On Jun 8, 12:32 am, Achal Rastogi wrote:
> Hi,
>
> Just checking to see if anyone is experiencing ssl connection failures
> as well.
>
> Here is the stack trace our logs are dumping out -
>
> 2009-06-07 22
Thanks much that worked great.
Tim
On Feb 25, 1:13 pm, Peer wrote:
> Hi,
>
> image.data is write only. On existing image ads you should use the
> image.imageUrl and then download the data using that Url.
>
> Cheers,
> Peer Jakobsen
> eSearchVision
--~--~-~--~~~--
diting the destination URL of an ad
> via the web interface results in a new ad with a different id.
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>
> On Feb 23, 10:44 am, tozor wrote:
>
> > I'm curious why AdService.updateAds() is so limited in terms of the
> &
I'm curious why AdService.updateAds() is so limited in terms of the
attributes that can be updated. One aspect of my application involves
updating URL parameters in the destination URL. This works fine for
placements and keywords but I have no way to do this for an Ad. I'm
curious if anyone el
I wanted to report an occurrence this morning, and more importantly
the fact that my workaround strategy was successful. Basically here
is what I am doing:
1) Download the file from the URL which is returned from
getGzipReportDownloadUrl()
2) Check the file size. If it is 30 bytes or less, then
I have also been experiencing this error. I had two occurrences in
the reports I ran this morning. Initially I simply implemented a 5
second delay between the time the report status switched to completed
and the time I accessed the URL. I will implement the retry discussed
here.
Tim
On Jan
really like is to be notified the
> next time this happens so that they could try to catch things live.
>
> So, please don't hesitate to post again about this behavior soon after
> you see it. I'll bring it to the engineers' immediate attention when
> you do.
>
&g
I saw it several times on Friday during the day, but have not seen it
since then.
Tim Ozor
On Oct 2, 10:07 am, AdWords API Advisor <[EMAIL PROTECTED]>
wrote:
> Hello,
>
> The bug is in with the engineering team, but there's no update on it
> yet. How frequently are folks experiencing this b
Thanks a bunch. I was looking at CampaignService and Campaign.
Tim
On Sep 30, 3:03 am, "Jan Piotrowski (AdWords API Guru)"
<[EMAIL PROTECTED]> wrote:
> Hi tozor,
>
> setCampaignNegativeCriteria is still there, but not where you looked
> for it. It doe
>From my read of the documentation it does not look like there is
support for managing the list of negative keywords and site exclusions
which are available at the campaign level. If this is correct, any
chance this support will get into v13??
Thanks in advance.
Tim Ozor
--~--~-~--
I am also seeing these errors today with some frequency.
Tim Ozor
On Sep 26, 10:43 am, AdWords API Advisor
<[EMAIL PROTECTED]> wrote:
> Thanks for providing those logs and report job ids. I'll open a bug
> with the reports team with that info.
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>
bsite--Keywords will have a value in [Broad, Phrase, Exact] and
> Websites will be something else*.
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>
> *Seehttp://groups.google.com/group/adwords-api/browse_thread/thread/cb1a4...
>
> On Sep 23, 12:13 pm, tozor <[EMAIL PRO
I re-ran the same report since my last post and it now does have the
KeywordMinCPC column. So it seems like the behavior changed within
the last hour. Hopefully Jeff can clear this up for us.
Tim
On Sep 23, 11:39 am, "Peer Jakobsen (AdWords API Guru)"
<[EMAIL PROTECTED]> wrote:
> We saw th
I made a related post on this matter, but I wish they would keep the
value of KeywordMinCpc in the output at least thru the end of
supporting the v12 release. I am sure that other folks (including
myself) are going to have their existing code affected by removing
this attribute from the XML outpu
I am wondering how I can distinguish between a placement (website as
the API calls it) and a keyword in a Keyword report. The way I did
this previously was to use KeywordMinCpc. Placements had an empty
value for this attribute. Now the min cpc attribute does not seem to
be showing up in reports
t; that, it's probably worthwhile to think about whether there's anything
> that can be done to change the scope of the report you're running. For
> instance, if this is a cross-client report from an MCC, can you split
> up the clients that it requests into a set of sma
our report team isolate the issue on your end.
Tim
On Aug 28, 11:11 am, tozor <[EMAIL PROTECTED]> wrote:
> I appreciate the reply but am frustrated because I don't see from your
> answer how I am going to get this resolved. I currently have a report
> which is again st
ng smaller batches of concurrent zero-impression keyword
> reports. While there is not a hard limit on the number you can run,
> they do require much more processing than other reports to complete.
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>
> On Aug 26, 5:25 pm, tozor &l
I have a stuck one I'll let go for awhile. The report id is
431736501. It has been running for 2.5 hours. Hopefully your report
team can find out what is going on with this one.
Thanks.
Tim
On Aug 23, 8:14 am, tozor <[EMAIL PROTECTED]> wrote:
> One more example that
report id to them.
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>
> On Aug 21, 3:45 pm, tozor <[EMAIL PROTECTED]> wrote:
>
> > Jeff,
>
> > Just letting you know that the problem does still exist, although I
> > went for a couple of days without seeing it.
48 matches
Mail list logo
