And to follow up on this once more:
For 2 days now im getting a "A connection that was expected to be
established was closed by the server"-Webexception..*sigh*
Is Google doing any kind of maintainance atm?
On 26 Mai, 10:52, quaylar wrote:
> Hello Jeff,
>
> Just wanted to let u know, that the e
Hello Jeff,
Just wanted to let u know, that the errors have not occured for 2
weeks now.
Apart from this change concerning the "Expect: 100-continue" header i
havent changed
anything in my code.
Anyways, this change did not seem to do the trick, since a different
type of error occured aftwards.
pletely without any disconnections.
> About the SOAP log; I have enabled the SOAP log file from now on. As soon as
> our tool runs into a forcibly closed connection, I will send you the log.
>
> Cheerz
>
> Paz
>
>
>
> > Date: Mon, 11 May 2009 12:43:19 -0700
> >
.
Cheerz
Paz
> Date: Mon, 11 May 2009 12:43:19 -0700
> Subject: AdWords API Re: API-Access impossible
> From: adwordsapiadvi...@google.com
> To: adwords-api@googlegroups.com
>
>
> Hello Pazcal,
>
> I've been speaking to Qu offthread and gathering some additio
Hello Pazcal,
I've been speaking to Qu offthread and gathering some additional
data, but no, there is not currently any indication as to what the
cause or resolution is.
If you happen to have a SOAP log of a request that resulted in a
disconnection, feel free to pass it along to the email addr
Hi Jeff and Qu,
The reason why I'm react is because I'm running into the same
problems. Since I've updated to API v13, I'm having the same errors.
Only the strangest thing I have is, it isn't happening every time...
We are running our tool every night at 04.00 GMT +1. Sometimes the
tool complete
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
wrote:
> Hello Qu,
>
> If you could give me some more information about your requests I
> could do so
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 yo
Hi again Jeff,
Unfort. i wasnt able to resolve this issue so far.
Is it possible for Adwords Support, 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 si
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 tim
Hello Quaylar,
If the individual API calls you're making taking an exceedingly long
time to complete, then yes, it's possible that the AdWords API server
is closing the connection (and this may also manifest itself as the
502 - Bad Gateway errors). But they would have to be very long
operations,
11 matches
Mail list logo
