Good morning Nadine.
Once again, thank you a lot for your answers !!
Today, it seems to work fine again. But, I turned off all access from the
API yesterday all day long. I do not know if it is a coincidence or the
good thing to do...
Some requests succeed if I try again. But, the number of
Hi Pierre,
If you are not getting back a request ID, this means that the failed
requests are not making it to our servers. In that case, I can't
troubleshoot from our side. You may need to sit down with a network
administrator to trace the failed requests.
Best,
Nadine, AdWords API Team
On
Good morning Nadine and everyone !!!
Since Yesterday, I get the same issues as previously wrote.
I still do not understand what is happening. I did not have change anything
in the code, server or network.
I have tried to update my code as in the post gave by Nadine.
Unfortunately, that did not
Little Update !!
I get a new error :
- Error finding uri property (I did not find anything about this one in
this forum)
If I follow the calls, usually, it starts with :
1 -- SOAP-ERROR: Parsing WSDL: Couldn't load from
Hi Pierre,
I don't believe that you are having rate limit
https://developers.google.com/adwords/api/docs/guides/rate-limits issues
because you would be getting an error if you had hit the rate limit. Does
the request succeed if you try again? If you're getting back a request ID
in your error,
Good morning Nadine !!!
Thank you a lot for your answer.
I did not have try those solutions from the post because, every thing seems
to work fine again this morning o_O
But, I will keep this post preciously !!
My network administrator has found out that Google has changed some DNS...
Maybe,
Good afternoon,
Since this morning (May 7th 2015), I have got many errors :
- Bad Gateway
- Failed to load response into DOM: DOMDocument::loadXML(): Empty string
supplied as input in
**/Google/src/Google/Api/Ads/Common/Lib/AdsSoapClient.php on
line 268
- [WSDL] SOAP-ERROR:
Hello Pierre,
Check out this post
https://groups.google.com/d/msg/google-doubleclick-for-publishers-api/K7UQNyllhqU/XRZ2EADXyiIJ
to
see if the solutions provided there will fix you problem.
Thanks,
Nadine, AdWords API Team
On Thursday, May 7, 2015 at 11:33:02 AM UTC-4, Pierre Augereau wrote:
