Hi Everybody,
I just wanted to make sure you all are aware of our new recommend way to
test your code, real production test accounts!
https://developers.google.com/adwords/api/docs/test-accounts
Best,
- David Torres - AdWords API Team
On Friday, November 9, 2012 8:16:11 PM UTC-5, Gatsby Lee w
Takeshi,
どうもありがとう.
It is working fine now.
Again, thank you for your quick fix.
Gatsby
On Thursday, November 8, 2012 11:19:47 PM UTC-8, Takeshi Hagikura wrote:
>
> Hello,
>
> Apologies for the inconvenience.
> The issue has been fixed now.
> If you are still seeing the error, can you please let
It works BUT when I use the *CategoryProductsAndServicesSearchParameter* it
doesn't work and I get: UNEXPECTED_INTERNAL_API_ERROR.
Have you got the same?
D.
Il giorno venerdì 9 novembre 2012 09:54:50 UTC+1, WA ha scritto:
>
> Yes! it seems to work now. thanks.
>
> Le vendredi 9 novembre 2012 08:
Yes! it seems to work now. thanks.
Le vendredi 9 novembre 2012 08:19:47 UTC+1, Takeshi Hagikura a écrit :
>
> Hello,
>
> Apologies for the inconvenience.
> The issue has been fixed now.
> If you are still seeing the error, can you please let us know again?
>
> Thanks,
> - Takeshi, AdWords API Team
Hello,
Apologies for the inconvenience.
The issue has been fixed now.
If you are still seeing the error, can you please let us know again?
Thanks,
- Takeshi, AdWords API Team
2012年11月9日金曜日 3時29分38秒 UTC+9 Gatsby Lee:
>
> Hello,
>
> this issue is getting worse instead better.
> I got this issue e
Hello,
this issue is getting worse instead better.
I got this issue even with us location id.
When is Google Adwords team planning to fix this?
Gatsby
On Tuesday, October 9, 2012 2:07:09 AM UTC-7, Patrick Fischer wrote:
>
> Hi,
>
> I'm using the lastest adwords api v201209 with the php client s
Getting the same error for v201206 now also. Looks like they made a rogue
update to the older, deprecated API backend. Using US (2840) as the country
code. Failing in TIS (keyword/stats) and TrafficEstimaterService as well.
On Thursday, November 8, 2012 7:20:16 AM UTC-5, Martin wrote:
>
> I am g
I am getting these errors using v201206 as well, not as often, but still do.
Using the java client.
com.google.api-ads
adwords-axis
1.11.0
On Wednesday, October 24, 2012 1:20:55 AM UTC+2, Gatsby Lee wrote:
>
> try to use 201206.
> I am using that one instead of 201209 because this issue.
>
I am also getting this error
>
> $selector = new TargetingIdeaSelector();
> $selector->requestType = 'STATS';
> $selector->ideaType = 'KEYWORD';
> $selector->requestedAttributeTypes = array('KEYWORD_TEXT', 'COMPETITION',
> 'SEARCH_VOLUME');
> $selector->localeCode = 'de_DE';
> $selector->currency
Hi Schmilblick and WA,
We are aware of this issue and are looking into it. I'll update this thread
as soon as we have any more information.
Regards,
Paul Matthews.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
same in here with dotnet library :
[CriterionError.INVALID_CRITERION_ID @
selector.searchParameters[1].locations[0]; trigger:'2250']
It randomely answer this.
Any idea?
Le jeudi 8 novembre 2012 10:05:45 UTC+1, Schmilblick a écrit :
>
> Hello Paul/AdWords API Team,
>
> We are currently experi
Hello Paul/AdWords API Team,
We are currently experiencing the same problem
with CriterionError.INVALID_CRITERION_ID.
Pasting request and response below:
SOAP request: http://dpaste.com/827088/
Response: http://dpaste.com/827089/
This is with v201206 in production.
On Wednesday, October 31,
Hi Terrafant,
Whilst you're still seeing issues with the service, I'd recommend using
v201206 for these requests (in production code anyway). That said, I always
recommend upgrading to the latest version as soon as possible. If you are
still seeing this issue in the coming days, we'd love to kn
Hi Paul, I use Java client code and sometimes I get this error. Will there
be a fix in a short time or should we use v201206?
On Wednesday, October 24, 2012 11:32:39 AM UTC+3, Paul Matthews wrote:
>
> Hi Gatsby, Andrezza, Steven
>
> There is currently a bug that is affecting a small number of TIS
thank you Paul!!
On Wednesday, October 24, 2012 1:32:39 AM UTC-7, Paul Matthews wrote:
>
> Hi Gatsby, Andrezza, Steven
>
> There is currently a bug that is affecting a small number of TIS queries.
> We're currently working on a fix and expect the problem to be resolved
> within a few days.
>
> If
no problem :)
On Tuesday, October 23, 2012 5:11:36 PM UTC-7, Steven wrote:
>
> 201206 works fine, thanks for the prompt reply. I hope someone will update
> this thread when a 201209 patch has been posted.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussio
Hi Gatsby, Andrezza, Steven
There is currently a bug that is affecting a small number of TIS queries.
We're currently working on a fix and expect the problem to be resolved
within a few days.
If you continue to experience this problem, please let us know.
-Paul, AdWords API Team.
On Wednesday,
201206 works fine, thanks for the prompt reply. I hope someone will update
this thread when a 201209 patch has been posted.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
try to use 201206.
I am using that one instead of 201209 because this issue.
On Tuesday, October 23, 2012 4:11:46 PM UTC-7, Steven wrote:
>
> Any movement on this? We have the same issue and we cant deploy the newest
> version without a workaround.
>
> On Friday, October 19, 2012 5:41:56 AM UTC-7
Here is the response.
[ERROR]APIExceptionstdClass Object
(
[ApiExceptionFault] => stdClass Object
(
[message] => [CriterionError.INVALID_CRITERION_ID @
selector.searchParameters[1].locations[0]; trigger:'2300']
[ApplicationException.Type] => ApiException
Any movement on this? We have the same issue and we cant deploy the newest
version without a workaround.
On Friday, October 19, 2012 5:41:56 AM UTC-7, Danial Klimkin wrote:
>
> Hello Gatsby, Andrezza,
>
>
> Please send me the request and response XML logs for the call with an
> error over *email
Hello Gatsby, Andrezza,
Please send me the request and response XML logs for the call with an error
over *email*. (Reply button on the forum).
-Danial, AdWords API Team.
On Friday, October 19, 2012 3:22:14 AM UTC+4, Andrezza wrote:
>
> Danial, I'm using the lastest adwords api v201209 with t
Danial, I'm using the lastest adwords api v201209 with the java client
software and I have the same problem.
The services are returning this error randomly and we are using the
production environment.
Andrezza
Em quinta-feira, 11 de outubro de 2012 09h30min00s UTC-3, Danial Klimkin
escreveu:
Danial,
Even though we are using the production server to get data, we still see
the same error.
Gatsby
On Thursday, October 11, 2012 5:30:00 AM UTC-7, Danial Klimkin wrote:
>
> Hello Patrick,
>
>
> The sandbox environment is good for testing only and all data is
> generated. The services can
Hello Patrick,
The sandbox environment is good for testing only and all data is generated.
The services can return zeroes, random values or an error, depending on
service.
-Danial, AdWords API Team.
On Tuesday, October 9, 2012 1:07:09 PM UTC+4, Patrick Fischer wrote:
>
> Hi,
>
> I'm using t
Hi,
I'm using the lastest adwords api v201209 with the php client software.
Using the same code in sandbox instead of the production server fails with
the following message: Fatal error: Uncaught SoapFault exception:
[soap:Server] [CriterionError.INVALID_CRITERION_ID @
selector.searchParameter
26 matches
Mail list logo
