Hi Josh,
Anyways, you might want to report an issue in the appropriate client
library's issue tracker. I remember that .NET client library had a similar
issue long time back, which was traced back to a setting named
maximumErrorResponseLength in system.net runtime library. It defaulted to
64K,
The solution in the end was to delete certain Campaign Negatives that
didn't seem to work well with CampaignCriterionService.Get.
Don't know why we had this campaign negative in the account but you'd
think it should still be valid.
[in charge
education__
Hi,
I forgot to mention that for the previous case I was using paging with
a size of 1000 keywords. The SOAP request is as follows:
http://schemas.xmlsoap.org/soap/
encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:ZSI="http://www.zolera.com/schemas/ZSI/"; xmlns:xsd="h
Hi.
I think that this happens cause you're trying to download all 88653
entries.
Try to download this data using Paging, and group keywords by 3000 for
example.
Regards,
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspo
Hey all,
while using CampaignCriterionService.Get, I am receiving a SOAP
response that seems to be cut off, leading to the SoapBuffer raising
an exception "Unable to parse SOAP buffer for incoming messages. no
element found: line 2, column 318897". All previous Get calls work
fine until this speci
