Hello Tim,
Thank you for the feedback. It is great to hear the issue is resolved. -Danial, AdWords API Team. > On Monday, August 13, 2012 6:13:26 PM UTC+1, tozor wrote: > > > > We are caching the AdwordsUser instance in our code (which contains the > > token). However we were doing this in the reporting part of our > > application based on the account email, which is not the same as the email > > we use for authentication which is for our MCC. So we would only > > authenticate once per account, but actually multiple times for the same MCC > > user. We changed our code to directly cache the auth token for our MCC > > user. > > > > Let me just give one more shout out to the good folks at Google that pay > > attention to this forum. Our application has to work on both Google and > > The Search Engine Who Shall Not Be Named. I can tell you that posting to > > that other forum is really just a typing exercise for the developer. It is > > really a pleasure to know that if you take the time to formulate an > > intelligent query, that you will get one or more intelligent replies. > > > > Tim > > > > On Monday, 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 Adwords java client library, we see > >>> where our code needs to be changed. We were caching the tokens but not > >>> optimally for this report download code path. Thanks again for the quick > >>> reply. As a developer responsible for a very large application with a very > >>> 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: > >>>> > >>>> Caused by: com.google.api.adwords.lib.AuthTokenException: Auth token > >>>> could not be retrieved because of error: CaptchaRequired > >>>> at > >>>> com.google.api.adwords.lib.AuthToken.getAuthToken(AuthToken.java:133) > >>>> at > >>>> com.google.api.adwords.lib.utils.v201109.ReportUtils.reloadAuthToken(ReportUtils.java:278) > >>>> at > >>>> com.google.api.adwords.lib.utils.v201109.ReportUtils.downloadReport(ReportUtils.java:189) > >>>> > >>>> The downloadReport() method takes an AdwordsUser instance. We are > >>>> caching this in our code so that we only authenticate once. However from > >>>> looking at the stack trace, it looks like the Adwords client library is > >>>> actually reloading the auth token. Since I don't have the source to the > >>>> Adwords client library, I am confused if your advice will actually help me. > >>>> > >>>> Tim > >>>> > >>>> > >>>> On Monday, August 13, 2012 8:54:24 AM UTC-5, AdWords API Advisor wrote: > >>>>> > >>>>> Hello Tim, > >>>>> > >>>>> > >>>>> You are being limited by the authorization mechanism, not AdWords API. > >>>>> The > >>>>> ClientLogin protocol refuses to authorize too often with the email and > >>>>> password for security reason. We recommend 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 Follows: > >>>>> ------------------------ > >>>>> From: tozor <[email protected]> > >>>>> Subject: Re: Reports not being returned in requested format > >>>>> Date: Mon, 13 Aug 2012 06:24:36 -0700 (PDT) > >>>>> > >>>>> > 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 > >>>>> could > >>>>> > not be retrieved because of error: CaptchaRequired > >>>>> > > >>>>> > We have added retries and delays and this helps some, but I am > >>>>> wondering > >>>>> > >>>>> > why we are getting this at all. This started happening mid day last > >>>>> > Thursday (8/9). We have a very large application that manages > >>>>> several > >>>>> > hundred Adwords accounts. So we pull reports of all types for all > >>>>> of > >>>>> these > >>>>> > accounts frequently (very frequently in the morning). Is there a > >>>>> rate > >>>>> of > >>>>> > report download requests that we must stay under? This is causing > >>>>> serious > >>>>> > pain for our application so please let us know if this is an issue > >>>>> on > >>>>> your > >>>>> > end or if this is intended behavior, how we are supposed to code our > >>>>> > application so that we are guaranteed to get the report we request. > >>>>> > > >>>>> > Thanks. > >>>>> > > >>>>> > Tim > >>>>> > > >>>>> > On Monday, August 13, 2012 3:56:01 AM UTC-5, Danial Klimkin wrote: > >>>>> > > > >>>>> > > Hi mm, > >>>>> > > > >>>>> > > > >>>>> > > Do you use any of our client libraries? Are there any network > >>>>> issues > >>>>> you > >>>>> > > see this morning as well? > >>>>> > > > >>>>> > > > >>>>> > > -Danial, AdWords API Team. > >>>>> > > > >>>>> > > > >>>>> > > On Friday, August 10, 2012 6:27:18 PM UTC+4, mm wrote: > >>>>> > >> > >>>>> > >> Hey guys - > >>>>> > >> I am seeing this problem with multiple (but not all) accounts > >>>>> this > >>>>> > >> morning. I am requesting reports in gzipped csv format, but am > >>>>> getting just > >>>>> > >> csv. This is happening for KeywordPerformance and > >>>>> CriteriaPerformance > >>>>> > >>>>> > >> reports. Known issue? Fix forthcoming? > >>>>> > >> > >>>>> > >> Thanks - > >>>>> > >> mm > >>>>> > >> > >>>>> > > > >>>>> > > >>>>> > -- > >>>>> > =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ > >>>>> > Also find us on our blog and discussion group: > >>>>> > http://adwordsapi.blogspot.com > >>>>> > http://groups.google.com/group/adwords-api > >>>>> > =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ > >>>>> > > >>>>> > You received this message because you are subscribed to the Google > >>>>> > Groups "AdWords API Forum" group. > >>>>> > To post to this group, send email to [email protected] > >>>>> > To unsubscribe from this group, send email to > >>>>> > [email protected] > >>>>> > For more options, visit this group at > >>>>> > http://groups.google.com/group/adwords-api?hl=en > >>>>> > >>>>> > > -- > =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ > Also find us on our blog and discussion group: > http://adwordsapi.blogspot.com > http://groups.google.com/group/adwords-api > =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ > > You received this message because you are subscribed to the Google > Groups "AdWords API Forum" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/adwords-api?hl=en -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
