subject:"Re\: Weird OAuth2 failure to refresh access token"

Re: Weird OAuth2 failure to refresh access token

2016-01-25 Thread Anthony Madrigal

Hi,

This seems like this issue is related an internal error with refreshing the 
access token. In general, if access tokens cannot be refreshed, you should 
try again after 30 seconds. If this does not work, you should try to do the 
OAuth2 flow again and get a hold of another access token.

In your App.config file, try setting:


If that still does not work, I suggest seeking the help of this forum 

.

Cheers,
Anthony
AdWords API Team

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/2a9ccac0-2018-4aef-b1b9-e528e4adb9b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Weird OAuth2 failure to refresh access token

2016-01-23 Thread PPC Developer

stack trace for the below error


   at 
Google.Api.Ads.Common.Lib.OAuth2ProviderForApplications.RefreshAccessTokenInOfflineMode()
   at 
Google.Api.Ads.Common.Lib.OAuth2ProviderForApplications.RefreshAccessToken()
   at 
Google.Api.Ads.Common.Lib.OAuth2ProviderBase.RefreshAccessTokenIfExpiring()
   at Google.Api.Ads.Common.Lib.OAuth2ProviderBase.GetAuthHeader()
   at Google.Api.Ads.AdWords.Lib.AdWordsSoapClient.InitForCall(String 
methodName, Object[] parameters)
   at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String 
methodName, Object[] parameters)
   at Google.Api.Ads.Common.Lib.AdsSoapClient.Invoke(String methodName, 
Object[] parameters)
   at Google.Api.Ads.AdWords.v201506.ManagedCustomerService.get(Selector 
serviceSelector)
   at AdwordsReports.Utilities.GetAllMCCAccounts() in 
c:\Users...mmon.cs:line 919



On Saturday, January 23, 2016 at 4:34:08 PM UTC, PPC Developer wrote:
>
> I'm running into the same problem with the server side. Our platform is 
> essentially a server that runs infinitely to download-process-update ad 
> groups/campigns,etc..the same code runs on multiple server instances on 
> multiple machines. After 1 day or so, some servers start getting the below 
> exception.
>
> Failed to refresh access token
> internal_failure
>
> restarting the server instance works, but that means server instances are 
> unable to run for more than 1-2 days and need recycling. Is there any 
> solution to this?
>
>
> On Wednesday, January 29, 2014 at 1:45:35 PM UTC, rohit wrote:
>>
>> Hi,
>>
>> Can someone from the AdWords team please help with resolving this issue. 
>> It has been happening every day for the past 10 days.
>>
>> ERROR 2014-01-21 03:30:33 21896 [Vulcan::Google]: 
>> msg:#
>> /home/offers/tracking/shared/bundle/jruby/1.9/gems/google-ads-common-0.9.3/lib/ads_common/auth/oauth2_handler.rb:94:in
>>  
>> `refresh_token!'
>> /home/offers/tracking/shared/bundle/jruby/1.9/gems/google-ads-common-0.9.3/lib/ads_common/auth/oauth2_handler.rb:83:in
>>  
>> `get_token'
>> /home/offers/tracking/shared/bundle/jruby/1.9/gems/google-ads-common-0.9.3/lib/ads_common/api.rb:113:in
>>  
>> `authorize'
>>
>> Token just prior to failure from this morning.
>>
>> :issued_at=>2014-01-29 07:41:50 -0600, :expires_in=>3600, :id_token=>nil
>>
>> Thanks, Rohit
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/c25d5781-c633-42b0-98e7-82fdc932ef3e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Weird OAuth2 failure to refresh access token

2016-01-23 Thread PPC Developer

I'm running into the same problem with the server side. Our platform is 
essentially a server that runs infinitely to download-process-update ad 
groups/campigns,etc..the same code runs on multiple server instances on 
multiple machines. After 1 day or so, some servers start getting the below 
exception.

Failed to refresh access token
internal_failure

restarting the server instance works, but that means server instances are 
unable to run for more than 1-2 days and need recycling. Is there any 
solution to this?


On Wednesday, January 29, 2014 at 1:45:35 PM UTC, rohit wrote:
>
> Hi,
>
> Can someone from the AdWords team please help with resolving this issue. 
> It has been happening every day for the past 10 days.
>
> ERROR 2014-01-21 03:30:33 21896 [Vulcan::Google]: 
> msg:#
> /home/offers/tracking/shared/bundle/jruby/1.9/gems/google-ads-common-0.9.3/lib/ads_common/auth/oauth2_handler.rb:94:in
>  
> `refresh_token!'
> /home/offers/tracking/shared/bundle/jruby/1.9/gems/google-ads-common-0.9.3/lib/ads_common/auth/oauth2_handler.rb:83:in
>  
> `get_token'
> /home/offers/tracking/shared/bundle/jruby/1.9/gems/google-ads-common-0.9.3/lib/ads_common/api.rb:113:in
>  
> `authorize'
>
> Token just prior to failure from this morning.
>
> :issued_at=>2014-01-29 07:41:50 -0600, :expires_in=>3600, :id_token=>nil
>
> Thanks, Rohit
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/0eb165fb-6626-4ab4-9057-c1437058ce71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Weird OAuth2 failure to refresh access token

2014-01-29 Thread rohit

Hi,

Can someone from the AdWords team please help with resolving this issue. It 
has been happening every day for the past 10 days.

ERROR 2014-01-21 03:30:33 21896 [Vulcan::Google]: 
msg:#
/home/offers/tracking/shared/bundle/jruby/1.9/gems/google-ads-common-0.9.3/lib/ads_common/auth/oauth2_handler.rb:94:in
 
`refresh_token!'
/home/offers/tracking/shared/bundle/jruby/1.9/gems/google-ads-common-0.9.3/lib/ads_common/auth/oauth2_handler.rb:83:in
 
`get_token'
/home/offers/tracking/shared/bundle/jruby/1.9/gems/google-ads-common-0.9.3/lib/ads_common/api.rb:113:in
 
`authorize'

Token just prior to failure from this morning.

:issued_at=>2014-01-29 07:41:50 -0600, :expires_in=>3600, :id_token=>nil

Thanks, Rohit

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.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 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/groups/opt_out.

Re: Weird OAuth2 failure to refresh access token

2014-01-21 Thread rohit

Hi,

We are seeing this same error for the past few days using the Ruby client. 
We make two scheduled attempts to download data at 3:30 AM and 5:30 AM, 
they both fail with the same error. Manual re-try at 7AM usually succeeds.

ERROR 2014-01-21 03:30:33 21896 [Vulcan::Google]: 
msg:#
/home/offers/tracking/shared/bundle/jruby/1.9/gems/google-ads-common-0.9.3/lib/ads_common/auth/oauth2_handler.rb:94:in
 
`refresh_token!'
/home/offers/tracking/shared/bundle/jruby/1.9/gems/google-ads-common-0.9.3/lib/ads_common/auth/oauth2_handler.rb:83:in
 
`get_token'
/home/offers/tracking/shared/bundle/jruby/1.9/gems/google-ads-common-0.9.3/lib/ads_common/api.rb:113:in
 
`authorize'

ERROR 2014-01-21 05:30:32 3817 [Vulcan::Google]: 
msg:#
/home/offers/tracking/shared/bundle/jruby/1.9/gems/google-ads-common-0.9.3/lib/ads_common/auth/oauth2_handler.rb:94:in
 
`refresh_token!'
/home/offers/tracking/shared/bundle/jruby/1.9/gems/google-ads-common-0.9.3/lib/ads_common/auth/oauth2_handler.rb:83:in
 
`get_token'
/home/offers/tracking/shared/bundle/jruby/1.9/gems/google-ads-common-0.9.3/lib/ads_common/api.rb:113:in
 
`authorize'

Any idea what is causing this issue?

Thanks, Rohit

On Monday, January 6, 2014 6:09:32 AM UTC-6, Akil Burgess wrote:
>
> Hi All,
>
> We've noticed a weird authentication error that was occurring on one of 
> our application servers over the weekend. All of our 
> *MutateJobService.mutate* API calls were failing with the error below 
> across multiple accounts. The weird thing is all other API calls were 
> unaffected and the MutateJobService.mutate API calls succeeded across our 
> other application servers (which are all using the same OAuth2 
> credentials). After restarting the failing application instance the errors 
> disappeared.
>
> Is there a reason why the refresh would only fail for one API call and not 
> for others? Similarly, why would the refresh only fail on one application 
> instance and not others?
>
> Thanks!
> Akil Burgess
>
>
> An unhandled exception occurred.
> [Google.Api.Ads.Common.Lib.AdsOAuthException]: Failed to refresh access 
> token.
>  http://www.w3.org/TR/html4/loose.dtd">Google
>  
> Accounts content="text/html; charset=utf-8"> content="IE=edge" /> content="width=device-width, initial-scale=1, minimum-scale=1, 
> maximum-scale=1, user-scalable=0" /> type='text/css' href='
> https://ssl.gstatic.com/accounts/o/1893590695-error_page_css_ltr.css'>
> 
>   
> >
 id="googlelogo"> alt="Google">403. 
> That's an error.
You 
> are not authorized to perform this request.  That's all we 
> know.
>
> Stack Trace: 
>at 
> Google.Api.Ads.Common.Lib.OAuth2ProviderForApplications.RefreshAccessTokenInOfflineMode()
>at Google.Api.Ads.Common.Lib.OAuth2ProviderBase.GetAuthHeader()
>at Google.Api.Ads.AdWords.Lib.AdWordsSoapClient.InitForCall(String 
> methodName, Object[] parameters)
>at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String 
> methodName, Object[] parameters)
>at Google.Api.Ads.AdWords.v201306.MutateJobService.mutate(Operation[] 
> operations, BulkMutateJobPolicy policy)
>...
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.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 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/groups/opt_out.

Re: Weird OAuth2 failure to refresh access token

2014-01-07 Thread Akil Burgess

Hi Anash,

Thanks for your response and the suggestion. We are already reusing 
OAuthProvider instances do reduce refresh frequency. We had experienced 
rate limit errors from the OAuth2 servers before (see http://goo.gl/wdDEKU) 
and the error page was different - is it possible to receive different 
error pages for rate limit errors?

I've opened Issue #7 (
https://github.com/googleads/googleads-adwords-dotnet-lib/issues/7) on the 
AdWords API .NET library to make the code path more robust.

Cheers,
Akil 

On Monday, January 6, 2014 11:00:53 PM UTC, Anash P. Oommen (AdWords API 
Team) wrote:
>
> Hi Akil,
>
> My initial guess is that the page is a rate limit error from the OAuth2 
> servers (too many instances trying to refresh access token simultaneously). 
> It's a matter of chance that a particular server failed, and the error 
> would go away if the code were retried after a minute or so.
>
> You could reuse the OAuthProvider instance between multiple AdWordsUser 
> instances to reduce its frequency, but could you also open an issue against 
> the AdWords API .NET library to make this code path more robust?
>
> Cheers,
> Anash P. Oommen,
> AdWords API Advisor.
>
> On Monday, January 6, 2014 7:09:32 AM UTC-5, Akil Burgess wrote:
>>
>> Hi All,
>>
>> We've noticed a weird authentication error that was occurring on one of 
>> our application servers over the weekend. All of our 
>> *MutateJobService.mutate* API calls were failing with the error below 
>> across multiple accounts. The weird thing is all other API calls were 
>> unaffected and the MutateJobService.mutate API calls succeeded across our 
>> other application servers (which are all using the same OAuth2 
>> credentials). After restarting the failing application instance the errors 
>> disappeared.
>>
>> Is there a reason why the refresh would only fail for one API call and 
>> not for others? Similarly, why would the refresh only fail on one 
>> application instance and not others?
>>
>> Thanks!
>> Akil Burgess
>>
>>
>> An unhandled exception occurred.
>> [Google.Api.Ads.Common.Lib.AdsOAuthException]: Failed to refresh access 
>> token.
>> > http://www.w3.org/TR/html4/loose.dtd">Google
>>  
>> Accounts> content="text/html; charset=utf-8">> content="IE=edge" />> content="width=device-width, initial-scale=1, minimum-scale=1, 
>> maximum-scale=1, user-scalable=0" />> type='text/css' href='
>> https://ssl.gstatic.com/accounts/o/1893590695-error_page_css_ltr.css'>
>> 
>> >  
>> >
> id="googlelogo">> alt="Google">403. 
>> That's an error.
You 
>> are not authorized to perform this request.  That's all we 
>> know.
>>
>> Stack Trace: 
>>at 
>> Google.Api.Ads.Common.Lib.OAuth2ProviderForApplications.RefreshAccessTokenInOfflineMode()
>>at Google.Api.Ads.Common.Lib.OAuth2ProviderBase.GetAuthHeader()
>>at Google.Api.Ads.AdWords.Lib.AdWordsSoapClient.InitForCall(String 
>> methodName, Object[] parameters)
>>at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String 
>> methodName, Object[] parameters)
>>at Google.Api.Ads.AdWords.v201306.MutateJobService.mutate(Operation[] 
>> operations, BulkMutateJobPolicy policy)
>>...
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.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 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/groups/opt_out.

Re: Weird OAuth2 failure to refresh access token

2014-01-06 Thread Anash P. Oommen (AdWords API Team)

Hi Akil,

My initial guess is that the page is a rate limit error from the OAuth2 
servers (too many instances trying to refresh access token simultaneously). 
It's a matter of chance that a particular server failed, and the error 
would go away if the code were retried after a minute or so.

You could reuse the OAuthProvider instance between multiple AdWordsUser 
instances to reduce its frequency, but could you also open an issue against 
the AdWords API .NET library to make this code path more robust?

Cheers,
Anash P. Oommen,
AdWords API Advisor.

On Monday, January 6, 2014 7:09:32 AM UTC-5, Akil Burgess wrote:
>
> Hi All,
>
> We've noticed a weird authentication error that was occurring on one of 
> our application servers over the weekend. All of our 
> *MutateJobService.mutate* API calls were failing with the error below 
> across multiple accounts. The weird thing is all other API calls were 
> unaffected and the MutateJobService.mutate API calls succeeded across our 
> other application servers (which are all using the same OAuth2 
> credentials). After restarting the failing application instance the errors 
> disappeared.
>
> Is there a reason why the refresh would only fail for one API call and not 
> for others? Similarly, why would the refresh only fail on one application 
> instance and not others?
>
> Thanks!
> Akil Burgess
>
>
> An unhandled exception occurred.
> [Google.Api.Ads.Common.Lib.AdsOAuthException]: Failed to refresh access 
> token.
>  http://www.w3.org/TR/html4/loose.dtd">Google
>  
> Accounts content="text/html; charset=utf-8"> content="IE=edge" /> content="width=device-width, initial-scale=1, minimum-scale=1, 
> maximum-scale=1, user-scalable=0" /> type='text/css' href='
> https://ssl.gstatic.com/accounts/o/1893590695-error_page_css_ltr.css'>
> 
>   
> >
 id="googlelogo"> alt="Google">403. 
> That's an error.
You 
> are not authorized to perform this request.  That's all we 
> know.
>
> Stack Trace: 
>at 
> Google.Api.Ads.Common.Lib.OAuth2ProviderForApplications.RefreshAccessTokenInOfflineMode()
>at Google.Api.Ads.Common.Lib.OAuth2ProviderBase.GetAuthHeader()
>at Google.Api.Ads.AdWords.Lib.AdWordsSoapClient.InitForCall(String 
> methodName, Object[] parameters)
>at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String 
> methodName, Object[] parameters)
>at Google.Api.Ads.AdWords.v201306.MutateJobService.mutate(Operation[] 
> operations, BulkMutateJobPolicy policy)
>...
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.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 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/groups/opt_out.

Re: Weird OAuth2 failure to refresh access token

Re: Weird OAuth2 failure to refresh access token

Re: Weird OAuth2 failure to refresh access token

Re: Weird OAuth2 failure to refresh access token

Re: Weird OAuth2 failure to refresh access token

Re: Weird OAuth2 failure to refresh access token

Re: Weird OAuth2 failure to refresh access token

7 matches

Site Navigation

Mail list logo

Footer information