7, 2015 at 6:05:16 PM UTC-7, Ashley Xu wrote:
>
> Hi,
>
> Any updates or ETA?
>
> Thanks
> Ashley
>
> On Thursday, October 1, 2015 at 4:25:43 PM UTC-7, Ashley Xu wrote:
>>
>> Ok, thank you! Please keep me updated
>>
>> On Thursday, October 1, 2015
Hi,
Any updates or ETA?
Thanks
Ashley
On Thursday, October 1, 2015 at 4:25:43 PM UTC-7, Ashley Xu wrote:
>
> Ok, thank you! Please keep me updated
>
> On Thursday, October 1, 2015 at 9:58:09 AM UTC-7, Nadine Sundquist
> (AdWords API Team) wrote:
>>
>> Hi Ashley,
t.
>
> Regards,
> Nadine, AdWords API Team
>
> On Friday, September 18, 2015 at 4:20:38 PM UTC-4, Ashley Xu wrote:
>>
>> Hi Thanet,
>>
>> Any update? The issue is still happening. We are in the progress of
>> uploading the v201506. But still it'll be good to k
rking on trying to find
> the root cause.
>
> Regards,
> Nadine, AdWords API Team
>
> On Thursday, October 1, 2015 at 12:31:30 PM UTC-4, Ashley Xu wrote:
>>
>> We have upgraded to the recommended SDK. Still it does not help. We have
>> reported to you about this iss
gt;
> I'm investigating this issue and will let you know once I have any update.
> Have you also tried v201506 and add your client customer ID in your header?
>
> Cheers,
> Thanet, AdWords API Team
>
> On Friday, September 11, 2015 at 7:48:54 AM UTC+9, Ashley Xu wrote:
&g
and explain
> more?
>
> Best,
> Thanet, AdWords API Team
>
> On Thursday, September 10, 2015 at 10:36:41 AM UTC+9, Ashley Xu wrote:
>>
>> Hi Thanet,
>>
>> Did you get my private reply? Please help investigate on your earliest
>>
, September 8, 2015 at 5:15:05 PM UTC-7, Ashley Xu wrote:
>
> I've included the soap request/response and the class/method from adwords
> api client we use in private mode.
>
> On Tuesday, September 8, 2015 at 10:44:01 AM UTC-7, Thanet Knack
> Praneenararat (AdWords API Tea
>>> In other words, CustomerService is designed to give you customer
>>> information, e.g., currency code, date time zone, *not* the
>>> *clientCustomerId* itself (though the ID is also returned with other
>>> information).
>>> If you don't know the clientCusto
Hi,
We are calling CustomerService to get the customer Id, we don't have that
on our side. Also according to your documentation about Customer Service-'It
has a get method that *takes no arguments* and returns a Customer record
containing fields such as customerI' It suggests that when calling
Hi,
I got the soap request and response. Please help investigate. We've been
seeing many these errors for the past two weeks continuously.
AdsClientLibs.SoapXmlLogs Error: 1 :
-BEGIN API CALL-
Request
---
POST
We currently don't have that log. Is there a way to get it? We are using
AdwordsApiClient_18.6.0. Do we have API to get this?
Thanks
Siming Xu
On Tuesday, August 11, 2015 at 9:00:30 AM UTC-7, Anthony Madrigal wrote:
Hi Ashley,
Could you please send me your SOAP request and response through
Hi,
We have seen many errors when calling the customer service via adwords
client sdk. The error code is [RequestError.UNKNOWN @ ]. Please find the
stack trace below. The error code does not give us much information as to
what caused the error. Could you please take a look?
Message: An API
Hi,
Did we have any update on this? We are still seeing the issue but it just
happened less frequently.
Thanks
Ashley
On Monday, June 1, 2015 at 5:41:56 PM UTC-7, Ashley Xu wrote:
Hi,
We have seen a lot of 502 bad gateway errors recently. Please find below
the stack trace and the number
We are trying to get those information. Before that could you please tell
us under what scenarios will this error be thrown?
On Tuesday, June 2, 2015 at 12:36:42 AM UTC-7, Thanet Knack Praneenararat
(AdWords API Team) wrote:
Hi Nick,
Did this happen to your existing account created a long
Could someone please help to investigate?
On Monday, June 1, 2015 at 5:41:56 PM UTC-7, Ashley Xu wrote:
Hi,
We have seen a lot of 502 bad gateway errors recently. Please find below
the stack trace and the number of failures per day. Could you please help
take a look?
Thanks
Ashley
Hi,
We have seen a lot of 502 bad gateway errors recently. Please find below
the stack trace and the number of failures per day. Could you please help
take a look?
Thanks
Ashley
Sync error: WebExceptionProtocolError --- System.Net.WebException: The
request failed with HTTP status 502: Bad
clientCustomerId
https://developers.google.com/adwords/api/docs/guides/soap#clientCustomerId
header. Make sure that the OAuth credentials were generated while logged in
as a user with access to the account.
Cheers,
Josh, AdWords API Team
On Tuesday, January 6, 2015 7:52:47 PM UTC-5, Ashley Xu wrote
Hello,
we are seeing many bad gateway 502 error on 1/7. Do you have any outage?
Thanks
Siming Xu
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
Hi,
We have seen OperationAccessDenied.ACTION_NOT_PERMITTED error when calling
Adwords API to get campaigns(We are using AdWordsApiClient_18.3.0). Please
find the stack trace below. Could anyone please let me know what does it
mean when we run into this exception. It seems one user keeps
7:18:27 PM UTC-4, Ashley Xu wrote:
Also the failures seem to have outburst on certain days. Yesterday
we were only seeing 30 errors whereas today we are seeing around 200
errors. Same for last week.
On Tuesday, July 8, 2014 4:07:39 PM UTC-7, Bikram Bhuyan wrote:
Hi All,
I am also facing
Hi,
We are currently using AdWordsApiClient for oauth and calling AdWords API.
However just recently, we start seeing frequent failures of Unable to
connect to the remote server.
Sync error: WebExceptionOther --- System.Net.WebException: Unable to
connect to the remote server ---
Hi Jeremy,
Could you please share what did you do to resolve the issue? I am facing
the same problem.
Thanks
Ashley
On Wednesday, February 19, 2014 9:13:50 AM UTC-8, Jeremy K wrote:
This is resolved now by addressing the transparent proxy issues. Thanks
for your help Danial
On Friday,
know if the issue is persistent - and the frequency of the
intermittent failure. Thanks!
Ray
On Tuesday, July 8, 2014 1:04:24 PM UTC-4, Ashley Xu wrote:
Hi,
We are currently using AdWordsApiClient for oauth and calling AdWords
API.
However just recently, we start seeing frequent
?
Thanks,
Ray
On Tuesday, July 8, 2014 3:47:57 PM UTC-4, Ray Tsang (AdWords API Team)
wrote:
Thanks - we'll look into this.
Cheers,
Ray
On Tuesday, July 8, 2014 3:03:35 PM UTC-4, Ashley Xu wrote:
Hi Ray,
Yes, it's persistent. It starts happening around 2 or 3 weeks ago
Another endpoint we are accessing is
https://accounts.google.com/o/oauth2/token to get the access token.
Thanks
Ashley
On Tuesday, July 8, 2014 10:04:24 AM UTC-7, Ashley Xu wrote:
Hi,
We are currently using AdWordsApiClient for oauth and calling AdWords API.
However just recently, we
On Tuesday, July 8, 2014 3:49:23 PM UTC-7, Ray Tsang (AdWords API Team)
wrote:
Ashley,
Btw, what is your MCC CID?
Lastly, please verify that there are no long internal firewalls that may
be blocking the requests on your side.
Thanks!
Ray
On Tuesday, July 8, 2014 6:36:26 PM UTC-4, Ashley Xu
convert the API version
to v201402. I was looking at the forum for some help. So thought I will
add my comment here as well.
Thanks,
Bikram.
On Tuesday, July 8, 2014 4:01:18 PM UTC-7, Ashley Xu wrote:
It's not for one user but randomly failed for different customers.
If you think the MCC CID
27 matches
Mail list logo
