Hello Jeff, I appreciate your help, thank you very much. I just sent an email to adwordsapiadvi...@google.com with my MCC customer-id.
best regards, --qu On 6 Mai, 16:58, AdWords API Advisor <adwordsapiadvi...@google.com> wrote: > Hello Qu, > > If you could give me some more information about your requests I > could do some spot checks in the production logs--I'm not sure that > anything conclusive will turn up, but I'll see. Either a requestId > from the SOAP response header of a successful request, or the customer > id number of your MCC account should give me enough info about your > account to find your requests. > > Cheers, > -Jeff Posnick,AdWordsAPI Team > > On May 5, 5:11 am, quaylar <che...@gmx.net> wrote: > > > Hi again Jeff, > > > Unfort. i wasnt able to resolve this issue so far. > > Is it possible forAdwordsSupport, to check their logs regarding the > > "api hit-limit" that was mentioned > > by you in one of the linked threads? > > It would be of great help to know, whether the connection was really > > reset on Google's side, or > > whether something else is the problem here. > > I'd gladly email you the email-adresses of the accounts that are > > accessed here, so u can check your logs regarding > > any error-messages. > > > regards, > > > --qu > > > On 30 Apr., 18:23, quaylar <che...@gmx.net> wrote: > > > > Hello Jeff, > > > > Thank u very much for your answer, i will try to give u more detailed > > > information. > > > As i stated before, the whole sync is taking 1,5-2h usually, right now > > > this exception > > > occurs after abt 1h. > > > The point is, there is no single individual call to the API that is > > > supposed to take a long time. > > > Due to the nature of this application, i was not able to make API > > > calls, passing in arrays of objects, but > > > rather had to pass each object in a separate API-Call. > > > Im aware of the fact, that passing in arrays, saves lots of protocol- > > > overhead, but it would require me to > > > rewrite parts of the application. Moreover i guess _then_ the > > > possibilty for long individual API-Calls would > > > increase. > > > > However as i said, there are not really long API-Calls, im not > > > generating reports, im just adding/deleting/modifying > > > campaigns/ad-groups/ads/keywords. > > > Nothing else. > > > > So i guess the duration of individual calls cant be a problem here - > > > is there any other possible reason? > > > I will check out the information in the link provided, thanks so far > > > Jeff. > > > > regards, > > > > --qu > > > > On 30 Apr., 17:47,AdWordsAPI Advisor <adwordsapiadvi...@google.com> > > > wrote: > > > > > Hello Quaylar, > > > > > If the individual API calls you're making taking an exceedingly long > > > > time to complete, then yes, it's possible that theAdWordsAPI server > > > > is closing the connection (and this may also manifest itself as the > > > >502-BadGatewayerrors). But they would have to be very long > > > > operations, and chances are there's a more efficient way of doing what > > > > you're trying to do. > > > > > You mention 1.5 to 2 hours to complete the full sync, but which > > > > individualAdWordsAPI calls are you making? How long does it take the > > > > longest individual call to complete (or how long elapses between the > > > > start of the call and the timeout error)? > > > > > Also, I wanted to bring your attention to some of the material linked > > > > to in this thread: > > > > > http://groups.google.com/group/adwords-api/browse_thread/thread/78598... > > > > > including some settings that are supposed to help the .NET runtime > > > > handle HTTP connections more robustly. > > > > > Cheers, > > > > -Jeff Posnick,AdWordsAPI Team > > > > > On Apr 30, 7:01 am, quaylar <che...@gmx.net> wrote: > > > > > > Hello all, > > > > > > I wrote and im still maintaining an ASP.NET application that is > > > > > holding theadwords-campaigns of various customers in a database, and > > > > > synchronizing them with Google in regular intervals. > > > > > This has been working almost flawless for a few months now, > > > > > nevertheless, within the last 2-3 weeks my client got timeouts from > > > > > time to time when starting sync, and since day before yday, he has not > > > > > been able at all to synchronize his campaigns anymore. > > > > > > He is maintaining 2 master-accounts, and accessing several accounts > > > > > through them. From time to time he is getting a timeout-exception that > > > > > says smthing like "A connection that was expected to be established > > > > > was closed", for both master-accounts. > > > > > > Yday he got an exception saying "An existing connection was forcibly > > > > > closed by the remote host" for both master-accounts, he kept trying > > > > > and was able to synchronize one of them. > > > > > Although the other one remains showing this exception, and in addition > > > > > sometimes shows a "Error502-Badgateway" error page. > > > > > > The client says, the synchronisation of this one master-account, > > > > > usually takes 1,5-2h, could this be the reason? Is there any timeout > > > > > on Google's side that is resetting the connection after this amount of > > > > > time? > > > > > Is there any hit-limit on the API, any max. usage-time at once etc, > > > > > that could cause such a behaviour? > > > > > > Problem is, that this one master-account has many customers underneath > > > > > it which need to be synchronized with Google and whose ads need to be > > > > > activated. > > > > > > Any help would be very much appreciated! > > > > > > best regards, > > > > > > --qu --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
