Re: Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

2016-04-25 Thread 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
Hi Tiana, This was due to an internal issue with the report servers, so there wasn't any action you could take in this situation aside from notifying us of the problem. Thanks, Josh, AdWords API Team On Monday, April 25, 2016 at 4:29:41 PM UTC-4, Tiana S. wrote: > > Hi Umesh, > > Have been run

Re: Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

2016-04-25 Thread Tiana S.
Hi Umesh, Have been running some reports, but no longer seeing the error. Will keep an eye out for new occurrences! Thank you very much for the quick response on this issue and the quick resolution. Very curious as to what was the cause of this. As Mark mentioned, I would also love to see a po

Re: Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

2016-04-25 Thread Joe G
Seeing this error as well with v201509. Some requests go through but the majority give CLIENT_NOT_AUTHORIZED. On Monday, April 25, 2016 at 3:22:42 PM UTC-4, Tiana S. wrote: > > Hi Anthony, > > Thanks for the heads up! > Having the same issue here, on API v201509 > > On Monday, 25 April 2016 21

Re: Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

2016-04-25 Thread Mark Rogoyski
Reports seem to be working normally now. Thank you for quickly troubleshooting the issue and resolving it. Will a postmortem be posted to explain the outage? On Monday, April 25, 2016 at 1:10:56 PM UTC-7, Umesh Dengale wrote: > > Hello, > > The engineering team has identified the issue and fix i

Re: Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

2016-04-25 Thread 'Umesh Dengale' via AdWords API Forum
Hello, The engineering team has identified the issue and fix is deployed. Please try to run the reports and let us know if you experience the same issue. Thanks, Umesh, AdWords API Team. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googl

Re: Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

2016-04-25 Thread Tiana S.
Hi Anthony, Thanks for the heads up! Having the same issue here, on API v201509 On Monday, 25 April 2016 21:13:50 UTC+2, Anthony Madrigal wrote: > > Hi guys, > > We are currently investigating this issue. There should be an update very > soon. Thanks for your patience. > > Regards, > Anthony >

Re: Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

2016-04-25 Thread olivier
We're getting the same error here, too. No changes on our side, just regular calls. On Monday, April 25, 2016 at 2:43:33 PM UTC-4, Mark Rogoyski wrote: > > We are seeing the same thing. > > On Monday, April 25, 2016 at 11:42:07 AM UTC-7, AdWordsApiUser wrote: >> >> We're getting LoasAuthenticatio

Re: Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

2016-04-25 Thread 'Anthony Madrigal' via AdWords API Forum
Hi guys, We are currently investigating this issue. There should be an update very soon. Thanks for your patience. Regards, Anthony AdWords API Team -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://p

Re: Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

2016-04-25 Thread Mark Rogoyski
We are on API v201601 and getting the same error responses. On Monday, April 25, 2016 at 12:10:52 PM UTC-7, Matt Linscott wrote: > > Same error here. We are getting it on the CAMPAIGN_PERFORMANCE_REPORT, > CAMPAIGN_PLATFORM_TARGET_REPORT and AD_PERFORMANCE_REPORT reports. We are > using the v201

Re: Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

2016-04-25 Thread Matt Linscott
Same error here. We are getting it on the CAMPAIGN_PERFORMANCE_REPORT, CAMPAIGN_PLATFORM_TARGET_REPORT and AD_PERFORMANCE_REPORT reports. We are using the v201603 API. Here's an example from the report log, with our auth info *'d out. [Apr 25 2016 11:59:55.00 - ERROR] POST /api/adwords/rep

Re: Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

2016-04-25 Thread Mark Rogoyski
We are experiencing the same thing. Services like ManagedCustomerService, CampaignService, ConstantDataService, etc. all seem to work, but ReportDefinitionService seems to fail with the LoasAuthenticationError.CLIENT_NOT_AUTHORIZED error on every request. On Monday, April 25, 2016 at 12:03:36 P

Re: Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

2016-04-25 Thread HK
We have the same issue and it will quickly become critical. We are seeing it with reports only. Our other APIs for getting campaigns, budgets, etc. are working fine, just not downloading reports. Hans -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+:

Re: Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

2016-04-25 Thread Gigel Chiazna
yep, me too; only for some reports, not for all operations On Monday, April 25, 2016 at 9:42:07 PM UTC+3, AdWordsApiUser wrote: > > We're getting LoasAuthenticationError.CLIENT_NOT_AUTHORIZED for most > request for the past 15 minutes or so. We are not a new user, we have > standard access. Is t

Re: Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

2016-04-25 Thread Mark Rogoyski
We are seeing the same thing. On Monday, April 25, 2016 at 11:42:07 AM UTC-7, AdWordsApiUser wrote: > > We're getting LoasAuthenticationError.CLIENT_NOT_AUTHORIZED for most > request for the past 15 minutes or so. We are not a new user, we have > standard access. Is this being looked at? Do we n

Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

2016-04-25 Thread AdWordsApiUser
We're getting LoasAuthenticationError.CLIENT_NOT_AUTHORIZED for most request for the past 15 minutes or so. We are not a new user, we have standard access. Is this being looked at? Do we need to do anything? -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Go