In addition, please also send me the full Java version number as well. Thanks,
On Friday, July 11, 2014 1:54:34 PM UTC-4, Ray Tsang (AdWords API Team) wrote: > > Bikram, > > Traceroute is a separate utility that may have been included with the OS - > for Windows, see tracert <http://support.microsoft.com/kb/162326>. > > Secondly, what is the Windows full version # and SP #? > > We are currently not detecting any abnormalities here, it would be worth > to check if there are other internal network settings in your datacenter > that may be causing issues. > > Thanks, > > On Friday, July 11, 2014 12:18:25 PM UTC-4, Bikram Bhuyan wrote: >> >> Hi Ray, >> >> Yes we are still facing the timeout issues at various calls. Yes we are >> running in windows platform. I am not sure where can I find the traceroute >> file. Do you mean to say "soap.log" which is generated for each timeouts? >> I have this file with my log. If you need that I can send it. Please let >> me know. >> >> Thanks, >> Bikram. >> >> On Friday, July 11, 2014 8:22:29 AM UTC-7, Ray Tsang (AdWords API Team) >> wrote: >>> >>> Bikram, >>> >>> Following up on this - are you still experiencing the same issues? >>> Secondly, are you running on a Windows platform? >>> Lastly, could I trouble you to send me a result of traceroute as well? >>> >>> Thanks! >>> >>> Ray >>> >>> On Wednesday, July 9, 2014 4:40:56 PM UTC-4, 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 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.
