Re: Api exception when calling Google.Api.Ads.AdWords.v201502.CustomerService.get()
BTW, do you know if it'll retry for this error? We have added RetryCount in our config file as is instructed in the client library wiki. If it still throws the exception then does it mean all the retry failed or there may not be any retry for that request. Thanks Ashley On Wednesday, October 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 at 9:58:09 AM UTC-7, Nadine Sundquist >> (AdWords API Team) wrote: >>> >>> Hi Ashley, >>> >>> Thanks for the update about you upgrading to a newer version. This one >>> seems to be a tricky one to resolve. We're still working 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 issue a month ago, provided you with the >>>> full soap request\response and tried out what you recommended, but to no >>>> avail. Please treat this as a high priority. And let us know what is the >>>> root cause and what we can try next asap. >>>> >>>> Thanks >>>> Ashley >>>> On Friday, September 18, 2015 at 5:05:31 PM UTC-7, Nadine Sundquist >>>> (AdWords API Team) wrote: >>>>> >>>>> Hi Ashley, >>>>> >>>>> I just checked on the thread that Thanet started about this issue. >>>>> They haven't been able to figure it out, yet. >>>>> >>>>> 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 know the root cause. >>>>>> >>>>>> Thanks >>>>>> Ashley >>>>>> >>>>>> On Thursday, September 10, 2015 at 11:39:42 PM UTC-7, Thanet Knack >>>>>> Praneenararat (AdWords API Team) wrote: >>>>>>> >>>>>>> Hi Ashley, >>>>>>> >>>>>>> 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: >>>>>>>> >>>>>>>> I've replied to your email with the information. Could you please >>>>>>>> take a look? >>>>>>>> >>>>>>>> Thanks >>>>>>>> Ashley >>>>>>>> >>>>>>>> On Wednesday, September 9, 2015 at 8:14:30 PM UTC-7, Thanet Knack >>>>>>>> Praneenararat (AdWords API Team) wrote: >>>>>>>> >>>>>>>>> Hi Ashley, >>>>>>>>> >>>>>>>>> I've replied to your email yesterday. Could you please check your >>>>>>>>> inbox again? >>>>>>>>> >>>>>>>>> What I've said in the email is that it seems your log a bit too >>>>>>>>> old so we can't track back to see what happened. >>>>>>>>> >>>>>>>>> Could you please: >>>>>>>>> >>>>>>>>>1. Send a recent one ? >>>>>>>>>2. Try v201506? >>>>>>>>>3. Add your client customer ID? (I know that it's written that >>>>>>>>>the client customer ID is not needed but to investigate the >>>>>>>>> problem, this >>>>>>>>>may help us.) >>>>>>>>> >>>>>>>>> By the way, I still don't get yo
Re: Api exception when calling Google.Api.Ads.AdWords.v201502.CustomerService.get()
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, >> >> Thanks for the update about you upgrading to a newer version. This one >> seems to be a tricky one to resolve. We're still working 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 issue a month ago, provided you with the full >>> soap request\response and tried out what you recommended, but to no avail. >>> Please treat this as a high priority. And let us know what is the root >>> cause and what we can try next asap. >>> >>> Thanks >>> Ashley >>> On Friday, September 18, 2015 at 5:05:31 PM UTC-7, Nadine Sundquist >>> (AdWords API Team) wrote: >>>> >>>> Hi Ashley, >>>> >>>> I just checked on the thread that Thanet started about this issue. They >>>> haven't been able to figure it out, yet. >>>> >>>> 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 know the root cause. >>>>> >>>>> Thanks >>>>> Ashley >>>>> >>>>> On Thursday, September 10, 2015 at 11:39:42 PM UTC-7, Thanet Knack >>>>> Praneenararat (AdWords API Team) wrote: >>>>>> >>>>>> Hi Ashley, >>>>>> >>>>>> 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: >>>>>>> >>>>>>> I've replied to your email with the information. Could you please >>>>>>> take a look? >>>>>>> >>>>>>> Thanks >>>>>>> Ashley >>>>>>> >>>>>>> On Wednesday, September 9, 2015 at 8:14:30 PM UTC-7, Thanet Knack >>>>>>> Praneenararat (AdWords API Team) wrote: >>>>>>> >>>>>>>> Hi Ashley, >>>>>>>> >>>>>>>> I've replied to your email yesterday. Could you please check your >>>>>>>> inbox again? >>>>>>>> >>>>>>>> What I've said in the email is that it seems your log a bit too old >>>>>>>> so we can't track back to see what happened. >>>>>>>> >>>>>>>> Could you please: >>>>>>>> >>>>>>>>1. Send a recent one ? >>>>>>>>2. Try v201506? >>>>>>>>3. Add your client customer ID? (I know that it's written that >>>>>>>>the client customer ID is not needed but to investigate the >>>>>>>> problem, this >>>>>>>>may help us.) >>>>>>>> >>>>>>>> By the way, I still don't get your use case much about using this >>>>>>>> service to get client customer ID. >>>>>>>> If possible, could you please also give your code snippets 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 h
Re: Api exception when calling Google.Api.Ads.AdWords.v201502.CustomerService.get()
We have upgraded to the recommended SDK. Still it does not help. We have reported to you about this issue a month ago, provided you with the full soap request\response and tried out what you recommended, but to no avail. Please treat this as a high priority. And let us know what is the root cause and what we can try next asap. Thanks Ashley On Friday, September 18, 2015 at 5:05:31 PM UTC-7, Nadine Sundquist (AdWords API Team) wrote: > > Hi Ashley, > > I just checked on the thread that Thanet started about this issue. They > haven't been able to figure it out, yet. > > 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 know the root cause. >> >> Thanks >> Ashley >> >> On Thursday, September 10, 2015 at 11:39:42 PM UTC-7, Thanet Knack >> Praneenararat (AdWords API Team) wrote: >>> >>> Hi Ashley, >>> >>> 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: >>>> >>>> I've replied to your email with the information. Could you please >>>> take a look? >>>> >>>> Thanks >>>> Ashley >>>> >>>> On Wednesday, September 9, 2015 at 8:14:30 PM UTC-7, Thanet Knack >>>> Praneenararat (AdWords API Team) wrote: >>>> >>>>> Hi Ashley, >>>>> >>>>> I've replied to your email yesterday. Could you please check your >>>>> inbox again? >>>>> >>>>> What I've said in the email is that it seems your log a bit too old so >>>>> we can't track back to see what happened. >>>>> >>>>> Could you please: >>>>> >>>>>1. Send a recent one ? >>>>>2. Try v201506? >>>>>3. Add your client customer ID? (I know that it's written that the >>>>>client customer ID is not needed but to investigate the problem, this >>>>> may >>>>>help us.) >>>>> >>>>> By the way, I still don't get your use case much about using this >>>>> service to get client customer ID. >>>>> If possible, could you please also give your code snippets 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 convenience. Our availability has been impacted for a long time >>>>>> now. This is one example request id 00051e629b8f3bc80a4c992354005dfb. >>>>>> The >>>>>> full soap request/response is already attached. >>>>>> >>>>>> Thanks >>>>>> Ashley >>>>>> >>>>>> On Tuesday, 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 Team) wrote: >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Could you please provide more information how you use the service? >>>>>>>> Any SOAP logs or code snippets would help much. >>>>>>>> Please reply by clicking *Reply privately to author* on the top >>>>>>>> right button of my comment. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Thanet, AdWords API Team >>>>>>>> >>>>>>>> On Tuesday, September 8, 2015 at 9:17:59 PM UTC+9, >>>>>>>> jxx...@hotmail.com wrote: >>>>>>&g
Re: Api exception when calling Google.Api.Ads.AdWords.v201502.CustomerService.get()
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, > > Thanks for the update about you upgrading to a newer version. This one > seems to be a tricky one to resolve. We're still working 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 issue a month ago, provided you with the full >> soap request\response and tried out what you recommended, but to no avail. >> Please treat this as a high priority. And let us know what is the root >> cause and what we can try next asap. >> >> Thanks >> Ashley >> On Friday, September 18, 2015 at 5:05:31 PM UTC-7, Nadine Sundquist >> (AdWords API Team) wrote: >>> >>> Hi Ashley, >>> >>> I just checked on the thread that Thanet started about this issue. They >>> haven't been able to figure it out, yet. >>> >>> 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 know the root cause. >>>> >>>> Thanks >>>> Ashley >>>> >>>> On Thursday, September 10, 2015 at 11:39:42 PM UTC-7, Thanet Knack >>>> Praneenararat (AdWords API Team) wrote: >>>>> >>>>> Hi Ashley, >>>>> >>>>> 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: >>>>>> >>>>>> I've replied to your email with the information. Could you please >>>>>> take a look? >>>>>> >>>>>> Thanks >>>>>> Ashley >>>>>> >>>>>> On Wednesday, September 9, 2015 at 8:14:30 PM UTC-7, Thanet Knack >>>>>> Praneenararat (AdWords API Team) wrote: >>>>>> >>>>>>> Hi Ashley, >>>>>>> >>>>>>> I've replied to your email yesterday. Could you please check your >>>>>>> inbox again? >>>>>>> >>>>>>> What I've said in the email is that it seems your log a bit too old >>>>>>> so we can't track back to see what happened. >>>>>>> >>>>>>> Could you please: >>>>>>> >>>>>>>1. Send a recent one ? >>>>>>>2. Try v201506? >>>>>>>3. Add your client customer ID? (I know that it's written that >>>>>>>the client customer ID is not needed but to investigate the problem, >>>>>>> this >>>>>>>may help us.) >>>>>>> >>>>>>> By the way, I still don't get your use case much about using this >>>>>>> service to get client customer ID. >>>>>>> If possible, could you please also give your code snippets 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 convenience. Our availability has been impacted for a long >>>>>>>> time >>>>>>>> now. This is one example request id 00051e629b8f3bc80a4c992354005dfb. >>>>>>>> The >>>>>>>> full soap request/response is already attached. >>>>>>>> >>>>>>>> Thanks >>>>>>>> Ashley >>>>>
Re: Api exception when calling Google.Api.Ads.AdWords.v201502.CustomerService.get()
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 know the root cause. Thanks Ashley On Thursday, September 10, 2015 at 11:39:42 PM UTC-7, Thanet Knack Praneenararat (AdWords API Team) wrote: > > Hi Ashley, > > 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: >> >> I've replied to your email with the information. Could you please take a >> look? >> >> Thanks >> Ashley >> >> On Wednesday, September 9, 2015 at 8:14:30 PM UTC-7, Thanet Knack >> Praneenararat (AdWords API Team) wrote: >> >>> Hi Ashley, >>> >>> I've replied to your email yesterday. Could you please check your inbox >>> again? >>> >>> What I've said in the email is that it seems your log a bit too old so >>> we can't track back to see what happened. >>> >>> Could you please: >>> >>>1. Send a recent one ? >>>2. Try v201506? >>>3. Add your client customer ID? (I know that it's written that the >>>client customer ID is not needed but to investigate the problem, this >>> may >>>help us.) >>> >>> By the way, I still don't get your use case much about using this >>> service to get client customer ID. >>> If possible, could you please also give your code snippets 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 >>>> convenience. Our availability has been impacted for a long time now. This >>>> is one example request id 00051e629b8f3bc80a4c992354005dfb. The full soap >>>> request/response is already attached. >>>> >>>> Thanks >>>> Ashley >>>> >>>> On Tuesday, 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 Team) wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> Could you please provide more information how you use the service? >>>>>> Any SOAP logs or code snippets would help much. >>>>>> Please reply by clicking *Reply privately to author* on the top >>>>>> right button of my comment. >>>>>> >>>>>> Cheers, >>>>>> Thanet, AdWords API Team >>>>>> >>>>>> On Tuesday, September 8, 2015 at 9:17:59 PM UTC+9, jxx...@hotmail.com >>>>>> wrote: >>>>>>> >>>>>>> Thanks Thanet for looking into it. I'm working with Ashley. And >>>>>>> we've been use this way to get customer id for a long time and just >>>>>>> recently that we noticed that we got UnKnownException from Adwards for >>>>>>> this >>>>>>> call. Nothing was changed on our end. So can you please help check why >>>>>>> we >>>>>>> are getting UnknownException. BTW, not all the request failed. Actually >>>>>>> only 2% of the requests got UnknownException error. Thanks a lot for >>>>>>> your >>>>>>> help! >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tuesday, September 1, 2015 at 1:35:38 AM UTC-7, Thanet Knack >>>>>>> Praneenararat (AdWords API Team) wrote: >>>>>>> >>>>>>>> Hi Ashley, >>>>>>>> >>>>>>>> Could you please tell me more about your use case? >>>>>>>> It's true that you don't need to pass arguments to use >>>>>>>> CustomerService, but that's because the default, which is the ID of >>>>>>>> authenticated account, is always returned. >>>>>>>> If you want to g
Re: Api exception when calling Google.Api.Ads.AdWords.v201502.CustomerService.get()
I've replied to your email with the information. Could you please take a look? Thanks Ashley On Wednesday, September 9, 2015 at 8:14:30 PM UTC-7, Thanet Knack Praneenararat (AdWords API Team) wrote: > Hi Ashley, > > I've replied to your email yesterday. Could you please check your inbox > again? > > What I've said in the email is that it seems your log a bit too old so we > can't track back to see what happened. > > Could you please: > >1. Send a recent one ? >2. Try v201506? >3. Add your client customer ID? (I know that it's written that the >client customer ID is not needed but to investigate the problem, this may >help us.) > > By the way, I still don't get your use case much about using this service > to get client customer ID. > If possible, could you please also give your code snippets 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 >> convenience. Our availability has been impacted for a long time now. This >> is one example request id 00051e629b8f3bc80a4c992354005dfb. The full soap >> request/response is already attached. >> >> Thanks >> Ashley >> >> On Tuesday, 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 Team) wrote: >>>> >>>> Hi, >>>> >>>> Could you please provide more information how you use the service? >>>> Any SOAP logs or code snippets would help much. >>>> Please reply by clicking *Reply privately to author* on the top right >>>> button of my comment. >>>> >>>> Cheers, >>>> Thanet, AdWords API Team >>>> >>>> On Tuesday, September 8, 2015 at 9:17:59 PM UTC+9, jxx...@hotmail.com >>>> wrote: >>>>> >>>>> Thanks Thanet for looking into it. I'm working with Ashley. And we've >>>>> been use this way to get customer id for a long time and just recently >>>>> that >>>>> we noticed that we got UnKnownException from Adwards for this call. >>>>> Nothing >>>>> was changed on our end. So can you please help check why we are getting >>>>> UnknownException. BTW, not all the request failed. Actually only 2% of >>>>> the >>>>> requests got UnknownException error. Thanks a lot for your help! >>>>> >>>>> >>>>> >>>>> On Tuesday, September 1, 2015 at 1:35:38 AM UTC-7, Thanet Knack >>>>> Praneenararat (AdWords API Team) wrote: >>>>> >>>>>> Hi Ashley, >>>>>> >>>>>> Could you please tell me more about your use case? >>>>>> It's true that you don't need to pass arguments to use >>>>>> CustomerService, but that's because the default, which is the ID of >>>>>> authenticated account, is always returned. >>>>>> If you want to get information of your child accounts, you need to >>>>>> specify a *clientCustomerId* when authenticating as an MCC to obtain >>>>>> such information. >>>>>> >>>>>> 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 clientCustomerId at first and that account is >>>>>> not managed under your MCC account, I don't think you can get >>>>>> information >>>>>> using CustomerService. >>>>>> >>>>>> Best, >>>>>> Thanet, AdWords API Team >>>>>> >>>>>> On Saturday, August 29, 2015 at 8:31:45 AM UTC+9, Ashley Xu wrote: >>>>>>> >>>>>>> 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
Re: Api exception when calling Google.Api.Ads.AdWords.v201502.CustomerService.get()
Hi Thanet, Did you get my private reply? Please help investigate on your earliest convenience. Our availability has been impacted for a long time now. This is one example request id 00051e629b8f3bc80a4c992354005dfb. The full soap request/response is already attached. Thanks Ashley On Tuesday, 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 Team) wrote: >> >> Hi, >> >> Could you please provide more information how you use the service? >> Any SOAP logs or code snippets would help much. >> Please reply by clicking *Reply privately to author* on the top right >> button of my comment. >> >> Cheers, >> Thanet, AdWords API Team >> >> On Tuesday, September 8, 2015 at 9:17:59 PM UTC+9, jxx...@hotmail.com >> wrote: >>> >>> Thanks Thanet for looking into it. I'm working with Ashley. And we've >>> been use this way to get customer id for a long time and just recently that >>> we noticed that we got UnKnownException from Adwards for this call. Nothing >>> was changed on our end. So can you please help check why we are getting >>> UnknownException. BTW, not all the request failed. Actually only 2% of the >>> requests got UnknownException error. Thanks a lot for your help! >>> >>> >>> >>> On Tuesday, September 1, 2015 at 1:35:38 AM UTC-7, Thanet Knack >>> Praneenararat (AdWords API Team) wrote: >>> >>>> Hi Ashley, >>>> >>>> Could you please tell me more about your use case? >>>> It's true that you don't need to pass arguments to use CustomerService, >>>> but that's because the default, which is the ID of authenticated account, >>>> is always returned. >>>> If you want to get information of your child accounts, you need to >>>> specify a *clientCustomerId* when authenticating as an MCC to obtain >>>> such information. >>>> >>>> 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 clientCustomerId at first and that account is not >>>> managed under your MCC account, I don't think you can get information >>>> using >>>> CustomerService. >>>> >>>> Best, >>>> Thanet, AdWords API Team >>>> >>>> On Saturday, August 29, 2015 at 8:31:45 AM UTC+9, Ashley Xu wrote: >>>>> >>>>> 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 Customer Service, we don't need to pass you any argument. >>>>> >>>>> clientCustomerID is used to obtain info for a specific account. We >>>>> failed before we even reach that step. >>>>> >>>>> For us, it's first call CustomerService to get customer id. Then call >>>>> ManagedCustomerService to get account info. We failed at the first step. >>>>> So >>>>> I don't think it's because we didn't pass in clientCustomerId. Just in >>>>> case, we tried importing from a MCC user in our production environment, >>>>> it >>>>> succeeded. >>>>> >>>>> From the SOAP response, there's a request ID, can we use it to nail >>>>> down to the exact error? That'll help a lot. Thank you! >>>>> >>>>> Thanks >>>>> Ashley >>>>> >>>>> On Friday, August 28, 2015 at 2:09:25 PM UTC-7, Anthony Madrigal wrote: >>>>>> >>>>>> HI Ashley, >>>>>> >>>>>> Are you using your MCC account to make this request or a client >>>>>> account? If it is an MCC account, you will need to specify the >>>>>> *clientCustomerId. >>>>>> *Here are more details on the CustomerService >>>>>> <https://developers.go
Re: Api exception when calling Google.Api.Ads.AdWords.v201502.CustomerService.get()
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 Team) wrote: > > Hi, > > Could you please provide more information how you use the service? > Any SOAP logs or code snippets would help much. > Please reply by clicking *Reply privately to author* on the top right > button of my comment. > > Cheers, > Thanet, AdWords API Team > > On Tuesday, September 8, 2015 at 9:17:59 PM UTC+9, jxx...@hotmail.com > wrote: >> >> Thanks Thanet for looking into it. I'm working with Ashley. And we've >> been use this way to get customer id for a long time and just recently that >> we noticed that we got UnKnownException from Adwards for this call. Nothing >> was changed on our end. So can you please help check why we are getting >> UnknownException. BTW, not all the request failed. Actually only 2% of the >> requests got UnknownException error. Thanks a lot for your help! >> >> >> >> On Tuesday, September 1, 2015 at 1:35:38 AM UTC-7, Thanet Knack >> Praneenararat (AdWords API Team) wrote: >> >>> Hi Ashley, >>> >>> Could you please tell me more about your use case? >>> It's true that you don't need to pass arguments to use CustomerService, >>> but that's because the default, which is the ID of authenticated account, >>> is always returned. >>> If you want to get information of your child accounts, you need to >>> specify a *clientCustomerId* when authenticating as an MCC to obtain >>> such information. >>> >>> 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 clientCustomerId at first and that account is not >>> managed under your MCC account, I don't think you can get information using >>> CustomerService. >>> >>> Best, >>> Thanet, AdWords API Team >>> >>> On Saturday, August 29, 2015 at 8:31:45 AM UTC+9, Ashley Xu wrote: >>>> >>>> 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 Customer Service, we don't need to pass you any argument. >>>> >>>> clientCustomerID is used to obtain info for a specific account. We >>>> failed before we even reach that step. >>>> >>>> For us, it's first call CustomerService to get customer id. Then call >>>> ManagedCustomerService to get account info. We failed at the first step. >>>> So >>>> I don't think it's because we didn't pass in clientCustomerId. Just in >>>> case, we tried importing from a MCC user in our production environment, it >>>> succeeded. >>>> >>>> From the SOAP response, there's a request ID, can we use it to nail >>>> down to the exact error? That'll help a lot. Thank you! >>>> >>>> Thanks >>>> Ashley >>>> >>>> On Friday, August 28, 2015 at 2:09:25 PM UTC-7, Anthony Madrigal wrote: >>>>> >>>>> HI Ashley, >>>>> >>>>> Are you using your MCC account to make this request or a client >>>>> account? If it is an MCC account, you will need to specify the >>>>> *clientCustomerId. >>>>> *Here are more details on the CustomerService >>>>> <https://developers.google.com/adwords/api/docs/guides/managing-accounts#customerservice> >>>>> . >>>>> >>>>> I also noticed you are using v201502. I suggest updating your client >>>>> library to v201506 >>>>> <https://developers.google.com/adwords/api/docs/clientlibraries>. >>>>> >>>>> Regards, >>>>> 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 http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/5dbfc6f1-5502-49d9-bd32-13cef83532e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Api exception when calling Google.Api.Ads.AdWords.v201502.CustomerService.get()
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 Customer Service, we don't need to pass you any argument. clientCustomerID is used to obtain info for a specific account. We failed before we even reach that step. For us, it's first call CustomerService to get customer id. Then call ManagedCustomerService to get account info. We failed at the first step. So I don't think it's because we didn't pass in clientCustomerId. Just in case, we tried importing from a MCC user in our production environment, it succeeded. From the SOAP response, there's a request ID, can we use it to nail down to the exact error? That'll help a lot. Thank you! Thanks Ashley On Friday, August 28, 2015 at 2:09:25 PM UTC-7, Anthony Madrigal wrote: HI Ashley, Are you using your MCC account to make this request or a client account? If it is an MCC account, you will need to specify the *clientCustomerId. *Here are more details on the CustomerService https://developers.google.com/adwords/api/docs/guides/managing-accounts#customerservice . I also noticed you are using v201502. I suggest updating your client library to v201506 https://developers.google.com/adwords/api/docs/clientlibraries. Regards, 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 http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/c562ada6-4dc1-43d4-8037-ef380183f390%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Api exception when calling Google.Api.Ads.AdWords.v201502.CustomerService.get()
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 /api/adwords/mcm/v201502/CustomerService User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.18449) Authorization: ** Content-Type: text/xml; charset=utf-8 SOAPAction: Host: adwords.google.com Content-Length: 699 Accept-Encoding: gzip Connection: Keep-Alive TimeStamp: Fri, 28 Aug 2015 10:42:29 GMT ?xml version=1.0 encoding=utf-8?soap:Envelope xmlns:soap= http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd= http://www.w3.org/2001/XMLSchema;soap:HeaderRequestHeader xmlns= https://adwords.google.com/api/adwords/mcm/v201502;developerToken xmlns= https://adwords.google.com/api/adwords/cm/v201502;**/developerTokenuserAgent xmlns=https://adwords.google.com/api/adwords/cm/v201502; (AwApi-DotNet/18.12.0, Common-Dotnet/3.7.0, .NET CLR/4.0.30319.18449, gzip)/userAgent/RequestHeader/soap:Headersoap:Bodyget xmlns= https://adwords.google.com/api/adwords/mcm/v201502; //soap:Body/soap:Envelope Response Content-Encoding: X-Content-Type-Options: nosniff X-Frame-Options: SAMEORIGIN X-XSS-Protection: 1; mode=block Content-Length: 497 Cache-Control: private, max-age=0 Content-Type: text/xml; charset=UTF-8 Date: Fri, 28 Aug 2015 17:42:29 GMT Expires: Fri, 28 Aug 2015 17:42:29 GMT Server: GSE TimeStamp: Fri, 28 Aug 2015 10:42:29 GMT soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;soap:HeaderResponseHeader xmlns:ns2=https://adwords.google.com/api/adwords/cm/v201502; xmlns= https://adwords.google.com/api/adwords/mcm/v201502;ns2:requestId00051e629b8f3bc80a4c992354005dfb/ns2:requestIdns2:serviceNameCustomerService/ns2:serviceNamens2:methodNameget/ns2:methodNamens2:operations0/ns2:operationsns2:responseTime137/ns2:responseTime/ResponseHeader/soap:Headersoap:Bodysoap:Faultfaultcodesoap:Server/faultcodefaultstring[RequestError.UNKNOWN @ ]/faultstringdetailApiExceptionFault xmlns= https://adwords.google.com/api/adwords/mcm/v201502; xmlns:ns2= https://adwords.google.com/api/adwords/cm/v201502;ns2:message[RequestError.UNKNOWN @ ]/ns2:messagens2:ApplicationException.TypeApiException/ns2:ApplicationException.Typens2:errors xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:type=ns2:RequestErrorns2:fieldPath/ns2:fieldPathns2:trigger/ns2:triggerns2:errorStringRequestError.UNKNOWN/ns2:errorStringns2:ApiError.TypeRequestError/ns2:ApiError.Typens2:reasonUNKNOWN/ns2:reason/ns2:errors/ApiExceptionFault/detail/soap:Fault/soap:Body/soap:Envelope -END API CALL--- Thanks Ashley On Thursday, August 13, 2015 at 6:21:40 AM UTC-7, Anthony Madrigal wrote: Hi Ashley, It depends on what client library https://developers.google.com/adwords/api/docs/clientlibraries they are using. Under the section *Source, *there is a link to the Github page of each respective client library. On that page, there is a section that shows how to enable logging. As an example, this link https://github.com/googleads/googleads-java-lib#user-content-how-do-i-enable-logging is how to enable logging for the Java library. Regards, 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 http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/e25a8c1e-bcc5-4d68-a83a-426bfc7d763a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Api exception when calling Google.Api.Ads.AdWords.v201502.CustomerService.get()
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 *reply privately to author*? This will help give me a clearer picture to what may be causing your error. Thanks, 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 http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/eb183e6f-146d-4c53-b48c-9b5db4a91dc2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Api exception when calling Google.Api.Ads.AdWords.v201502.CustomerService.get()
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 exception has occurred. See ApiException and InnerException fields for more details. StackTrace: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.v201502.CustomerService.get() Source: System.Web.Services Message: [RequestError.UNKNOWN @ ] StackTrace:at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String methodName, Object[] parameters) Thanks Ashley -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/5b6bde22-0376-4bcc-8363-3ad34e55f3c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Lots of 502 bad gateway errors
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 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 Gateway. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String methodName, Object[] parameters) at Google.Api.Ads.AdWords.v201409.ManagedCustomerService.get(Selector serviceSelector) *LogDate* *NumFailures*5/1/201525/2/201515/3/201515/4/201535/4/201565/4/201516 5/12/201545/12/201595/12/2015235/13/201515/13/2015105/14/201545/18/20151 5/18/201525/19/201515/19/201535/19/201535/20/201515/20/201535/21/20152 5/26/201515/26/201515/27/201515/27/201545/28/201565/28/201575/29/201535 5/29/2015385/30/201565/30/20155 -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/36e074fc-05df-4cd1-8efa-6c038e0750e5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: AuthenticationError.CUSTOMER_NOT_FOUND
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 time ago? Or did this happen to your newly created account? Can you provide request and response SOAP logs (with your credential information stripped)? Best, Thanet, AdWords API Team On Tuesday, June 2, 2015 at 6:24:47 AM UTC+9, Nick Zhu wrote: Hi guys, For the past few days we've been seeing a lot of exceptions due to AuthenticationError.CUSTOMER_NOT_FOUND. Google.Api.Ads.AdWords.Lib.AdWordsApiException: An API exception has occurred. See ApiException and InnerException fields for more details. --- System.Web.Services.Protocols.SoapException: [AuthenticationError.CUSTOMER_NOT_FOUND @ ; trigger:'null'] at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String methodName, Object[] parameters) --- End of inner exception stack trace --- at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String methodName, Object[] parameters) at Google.Api.Ads.AdWords.v201409.ManagedCustomerService.get(Selector serviceSelector) We're using the C# .NET library, are you guys aware of any issues with this call, or do you know anything about this error ? Thank you very much, Nick -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/dcf34b67-c28f-41a5-b6e5-570b595c85d0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Lots of 502 bad gateway errors
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 Sync error: WebExceptionProtocolError --- System.Net.WebException: The request failed with HTTP status 502: Bad Gateway. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String methodName, Object[] parameters) at Google.Api.Ads.AdWords.v201409.ManagedCustomerService.get(Selector serviceSelector) *LogDate* *NumFailures*5/1/201525/2/201515/3/201515/4/201535/4/201565/4/201516 5/12/201545/12/201595/12/2015235/13/201515/13/2015105/14/201545/18/20151 5/18/201525/19/201515/19/201535/19/201535/20/201515/20/201535/21/20152 5/26/201515/26/201515/27/201515/27/201545/28/201565/28/201575/29/201535 5/29/2015385/30/201565/30/20155 -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/32b03996-7ae1-4dbe-a8c2-2165e77ef3e2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Lots of 502 bad gateway errors
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 Gateway. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String methodName, Object[] parameters) at Google.Api.Ads.AdWords.v201409.ManagedCustomerService.get(Selector serviceSelector) *LogDate* *NumFailures*5/1/201525/2/201515/3/201515/4/201535/4/201565/4/201516 5/12/201545/12/201595/12/2015235/13/201515/13/2015105/14/201545/18/20151 5/18/201525/19/201515/19/201535/19/201535/20/201515/20/201535/21/20152 5/26/201515/26/201515/27/201515/27/201545/28/201565/28/201575/29/201535 5/29/2015385/30/201565/30/20155 -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/c65d17b3-518a-424d-b746-d738f0b2b3f6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: OperationAccessDenied.ACTION_NOT_PERMITTED error when calling API to get campaigns
Thanks Josh! On Wednesday, January 7, 2015 at 7:54:18 AM UTC-8, Josh Radcliff (AdWords API Team) wrote: Hi Ashley, That error means that the OAuth credentials you are using in your request do not grant you permissions to access the campaigns of the account specified in your 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: 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 trying to download campaigns and keeps getting this error. Timestamp: 1/2/2015 10:16:29 PM, 1/2/2015 10:15:19 PM, 1/2/2015 10:15:11 PM, 1/2/2015 10:14:16 PM UTC Inner Exceptions: Exception Type: Google.Api.Ads.AdWords.Lib.AdWordsApiException Source: AdWordsApiClient_18.3.0 Message: An API exception has occurred. See ApiException and InnerException fields for more details. StackTrace:at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String methodName, Object[] parameters) at Google.Api.Ads.AdWords.v201406.CampaignService.get(Selector serviceSelector) at Microsoft.Advertising.Client.GoogleSync.GoogleSyncClient.GetCampaignsInfo(Int64 customerId)Exception Type: System.Web.Services.Protocols.SoapException Source: System.Web.Services Message: [OperationAccessDenied.ACTION_NOT_PERMITTED @ class com.google.ads.api.serviceimpls.common.action.ReflectiveGetAction] StackTrace:at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String methodName, Object[] parameters) . Reserved 3: Reserved1: Thanks a lot! Ashley -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/bd4ab158-5a74-433e-85e5-1ce3f708c04f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Lots of bad gateway exception when calling Adwords API to download campaigns
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 =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/f5dacd55-490f-405d-bb64-25096d84ca66%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
OperationAccessDenied.ACTION_NOT_PERMITTED error when calling API to get campaigns
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 trying to download campaigns and keeps getting this error. Timestamp: 1/2/2015 10:16:29 PM, 1/2/2015 10:15:19 PM, 1/2/2015 10:15:11 PM, 1/2/2015 10:14:16 PM UTC Inner Exceptions: Exception Type: Google.Api.Ads.AdWords.Lib.AdWordsApiException Source: AdWordsApiClient_18.3.0 Message: An API exception has occurred. See ApiException and InnerException fields for more details. StackTrace:at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String methodName, Object[] parameters) at Google.Api.Ads.AdWords.v201406.CampaignService.get(Selector serviceSelector) at Microsoft.Advertising.Client.GoogleSync.GoogleSyncClient.GetCampaignsInfo(Int64 customerId)Exception Type: System.Web.Services.Protocols.SoapException Source: System.Web.Services Message: [OperationAccessDenied.ACTION_NOT_PERMITTED @ class com.google.ads.api.serviceimpls.common.action.ReflectiveGetAction] StackTrace:at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String methodName, Object[] parameters) . Reserved 3: Reserved1: Thanks a lot! Ashley -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/68421593-a6b8-4bc3-9f39-c66977b53dbe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Intermittent network exceptions: Unable to connect to the remote server
Hi Ray, After a day's investigation, I found the problem is actually on our side. We have some problem with network configuration. Now the issue is resolved and we do not see the errors again. Thank you so much for looking into the issue. Thanks Ashley On Wednesday, July 9, 2014 1:40:56 PM UTC-7, Bikram Bhuyan wrote: PST. San Jose, CA. On Wednesday, July 9, 2014 1:36:01 PM UTC-7, Ray Tsang (AdWords API Team) wrote: Bikram, Thanks for the details - quick question - what timezone is the log file timestamp recorded in? Ray On Wednesday, July 9, 2014 4:20:27 PM UTC-4, Bikram Bhuyan wrote: Some more observation if it helps. After making 5-6 calls it is hanging on the next calls. This is happening consistently. Please see the below log. It made 6 successive calls and it hanged and timed out on 7th call. Then it made 6 successive calls and then the next 7th request timed out. Sending my observation if it help you in doing more analysis. [09 Jul 2014 13:12:44,691-requestInfoLogger:INFO:taskExecutor-1] Request made: Service: AdGroupAdServiceInterfacePort Method: query URL: https://adwords.google.com/api/adwords/cm/v201402/AdGroupAdService; [09 Jul 2014 13:12:47,200-requestInfoLogger:INFO:taskExecutor-1] Request made: Service: AdGroupAdServiceInterfacePort Method: query URL: https://adwords.google.com/api/adwords/cm/v201402/AdGroupAdService; [09 Jul 2014 13:12:47,815-requestInfoLogger:INFO:taskExecutor-1] Request made: Service: AdGroupAdServiceInterfacePort Method: query URL: https://adwords.google.com/api/adwords/cm/v201402/AdGroupAdService; [09 Jul 2014 13:12:48,439-requestInfoLogger:INFO:taskExecutor-1] Request made: Service: AdGroupAdServiceInterfacePort Method: query URL: https://adwords.google.com/api/adwords/cm/v201402/AdGroupAdService; [09 Jul 2014 13:12:49,212-requestInfoLogger:INFO:taskExecutor-1] Request made: Service: AdGroupAdServiceInterfacePort Method: query URL: https://adwords.google.com/api/adwords/cm/v201402/AdGroupAdService; [09 Jul 2014 13:12:49,977-requestInfoLogger:INFO:taskExecutor-1] Request made: Service: AdGroupAdServiceInterfacePort Method: query URL: https://adwords.google.com/api/adwords/cm/v201402/AdGroupAdService; On Wednesday, July 9, 2014 1:07:35 PM UTC-7, Bikram Bhuyan wrote: Hi Ray, We are facing the same kind of issues as yesterday. It worked fine for fetching the campaign list, but when fetching the adgroups and its ads, it hanged in between after 3 successive calls. I was facing the same issues yesterday as well. I will send you the input and output message separately to you. FYI - I ran my calls around 1:06PM PST. If this will help you in looking at your log files etc. Thanks, Bikram. On Wednesday, July 9, 2014 12:34:08 PM UTC-7, Ray Tsang (AdWords API Team) wrote: Bikram and Ashley, Please keep me posted on any changes in terms of frequency of the error. We've made some adjustments. Thanks, Ray On Wednesday, July 9, 2014 3:33:05 PM UTC-4, Ray Tsang (AdWords API Team) wrote: Bikram, Yup, I received it and thanks for the information. We are looking into it. Cheers, Ray On Wednesday, July 9, 2014 12:35:51 PM UTC-4, Bikram Bhuyan wrote: Hi Ray, I sent my information to your id privately. Could you please confirm if you get the information what you are looking for? Thanks, Bikram. On Wednesday, July 9, 2014 7:23:21 AM UTC-7, Ray Tsang (AdWords API Team) wrote: Ashley and Bikram, Please send me both of your MCC CIDs. It will help us. Thanks! Ray On Tuesday, July 8, 2014 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 the similar issues today after I 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 is helpful, I will try get one for you. If the firewall is blocking, shouldn't it fail constantly instead of just intermittently? Is it possible that our requests are throttled? Thanks! Ashley 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 wrote: 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
Intermittent network exceptions: Unable to connect to the remote server
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 --- System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 74.125.25.138:443 Does anyone know what is going on? Why it starts failing intermittently now? Thanks! -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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. For more options, visit https://groups.google.com/d/optout.
Re: 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, February 14, 2014 9:06:42 AM UTC, Jeremy K wrote: Hi Danial, I've now made some progress - it seems that it works when connected to Wifi, but not when connected through the network. So the network administrator is looking into this. However, he asked is there a specific URL that we need to unblock? e.g. something.google.com? Thank you Jeremy On Thursday, February 13, 2014 9:53:30 AM UTC, Danial Klimkin wrote: Hi Jeremy, It's not much we can help here with unfortunately, as the issue is your local configuration. It is possible ruby picks up some local proxy settings, or dot net picks up some wrong settings. I suggest checking with your network administrator. -Danial, AdWords API Team. On Wednesday, February 12, 2014 7:02:57 PM UTC+4, Jeremy K wrote: Hi Danial, Thanks for your reply. I've been told that yes we do use a transparent proxy. I'm not sure what implication that has. Is there a way around it? I should add that the guy who got your ruby sample working had no problem. And I've checked that his config settings (e.g. Developer Token/Customer Id) are identical to mine. I just find is strange that it works fine in ruby but not .net. Do you have any other ideas as to what I can do next / what could be causing the problem? Thanks Jeremy On Tuesday, February 11, 2014 2:50:23 PM UTC, Danial Klimkin wrote: Hello Jeremy, Unfortunately we can not advise on the client side setup or network issues. The error message sounds like a networking issue to me. Do you happen to use a proxy / transparent proxy? -Danial, AdWords API Team. On Monday, February 10, 2014 6:55:14 PM UTC+4, Jeremy K wrote: Hi Danial, As far as I'm aware I can access port 443 for *.google.com I've opened up the windows firewall by adding inbound and outbound rules to be completely sure. Is there anything else that I need to do in order to access 443? Or do you have any other suggestions as to why its not working? Thanks Jeremy On Monday, February 10, 2014 10:23:13 AM UTC, Danial Klimkin wrote: Hello Jeremy, Please make sure you can access google servers from the box you are running the app on. You'll need https port (443) to be accessible for *. google.com. -Danial, AdWords API Team. On Friday, February 7, 2014 4:48:08 PM UTC+4, Jeremy K wrote: Hi, Unfortunately I'm getting an error when I try to run GetCampaigns in the c# .net sample that I downloaded from: https://github.com/googleads/googleads-adwords-dotnet-lib/releases/tag/v16.6.0 What's frustrating is that a colleague has managed to get this working in ruby and I'm using the exact same parameters (e.g. ClientCustomerId, UserAgent, DeveloperToken) as he is. The first expectation that I get is : Unable to connect to the remote server. Then the inner exception is: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. I've tried this in both v201306 and v201309 but I get the same error. Does anyone have any ideas please as to what's gone wrong? Thank you PS Posted once and my post didn't appear so hoping it doesn't double post -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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. For more options, visit https://groups.google.com/d/optout.
Re: Intermittent network exceptions: Unable to connect to the remote server
Hi Ray, Yes, it's persistent. It starts happening around 2 or 3 weeks ago and the frequency has been increasing. From our monitor, more than 10 % of our daily requests have failed due to this. It either failed at getting access token for oauth or getting a list of accounts or campaigns from adwords. However it's not happening continuously. Like if I manually retry, it will succeed. Please let me know what could be the cause and what can I do to mitigate. Thank you! Ashley On Tuesday, July 8, 2014 11:41:34 AM UTC-7, Ray Tsang (AdWords API Team) wrote: Ashley, Please let me 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 failures of Unable to connect to the remote server. Sync error: WebExceptionOther --- System.Net.WebException: Unable to connect to the remote server --- System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 74.125.25.138:443 Does anyone know what is going on? Why it starts failing intermittently now? Thanks! -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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. For more options, visit https://groups.google.com/d/optout.
Re: Intermittent network exceptions: Unable to connect to the remote server
We are making soap call. The request namespace is https://adwords.google.com/api/adwords/mcm/v201402. Below are some of the traceroute. tracert 74.125.25.138 Tracing route to pa-in-f138.1e100.net [74.125.25.138] over a maximum of 30 hops: 11 ms1 ms1 ms 10.28.76.3 2 1 ms1 ms1 ms port-channel33-569.ch1-x7x-1b.ntwk.msn.net [207.46.202.3] 3 *** Request timed out. 4 *** Request timed out. 5 *** Request timed out. 6 *** Request timed out. 7 *** Request timed out. 8 *** Request timed out. 9 *** Request timed out. 10 *** Request timed out. 11 *** Request timed out. 12 *** Request timed out. 13 *** Request timed out. 14 * tracert 74.125.28.113 Tracing route to pc-in-f113.1e100.net [74.125.28.113] over a maximum of 30 hops: 11 ms1 ms1 ms 10.28.76.3 21 ms1 ms1 ms port-channel33-569.ch1-x7x-1b.ntwk.msn.net [207.46.202.3] 3 *** Request timed out. 4 *** Request timed out. 5 *** Request timed out. 6 *** Request timed out. 7 *** Request timed out. 8 *** Request timed out. 9 *** Request timed out. 10 *** Request timed out. portqry /n 74.125.25.138 /e 443 Querying target system called: 74.125.25.138 Attempting to resolve IP address to a name... IP address resolved to pa-in-f138.1e100.net TCP port 443 (https service): LISTENING TCP port 443 (https service): LISTENING portqry /n 74.125.28.113 /e 443 Querying target system called: 74.125.28.113 Attempting to resolve IP address to a name... IP address resolved to pc-in-f113.1e100.net TCP port 443 (https service): LISTENING On Tuesday, July 8, 2014 1:23:35 PM UTC-7, Ray Tsang (AdWords API Team) wrote: Ashley, A follow up question - could I trouble you to confirm the DNS name that it's trying to reach, and a traceroute to that particular IP address from your server? 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 and the frequency has been increasing. From our monitor, more than 10 % of our daily requests have failed due to this. It either failed at getting access token for oauth or getting a list of accounts or campaigns from adwords. However it's not happening continuously. Like if I manually retry, it will succeed. Please let me know what could be the cause and what can I do to mitigate. Thank you! Ashley On Tuesday, July 8, 2014 11:41:34 AM UTC-7, Ray Tsang (AdWords API Team) wrote: Ashley, Please let me 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 failures of Unable to connect to the remote server. Sync error: WebExceptionOther --- System.Net.WebException: Unable to connect to the remote server --- System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 74.125.25.138:443 Does anyone know what is going on? Why it starts failing intermittently now? Thanks! -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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. For more options, visit https://groups.google.com/d/optout.
Re: Intermittent network exceptions: Unable to connect to the remote server
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 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 --- System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 74.125.25.138:443 Does anyone know what is going on? Why it starts failing intermittently now? Thanks! -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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. For more options, visit https://groups.google.com/d/optout.
Re: Intermittent network exceptions: Unable to connect to the remote server
It's not for one user but randomly failed for different customers. If you think the MCC CID is helpful, I will try get one for you. If the firewall is blocking, shouldn't it fail constantly instead of just intermittently? Is it possible that our requests are throttled? Thanks! Ashley 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 wrote: 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 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 --- System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 74.125.25.138:443 Does anyone know what is going on? Why it starts failing intermittently now? Thanks! -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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. For more options, visit https://groups.google.com/d/optout.
Re: Intermittent network exceptions: Unable to connect to the remote server
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 the similar issues today after I 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 is helpful, I will try get one for you. If the firewall is blocking, shouldn't it fail constantly instead of just intermittently? Is it possible that our requests are throttled? Thanks! Ashley 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 wrote: 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 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 --- System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 74.125.25.138:443 Does anyone know what is going on? Why it starts failing intermittently now? Thanks! -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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. For more options, visit https://groups.google.com/d/optout.
