Hi Phillip,
Thanks for all the additional information. Giving us the batch job IDs
meant I could retrieve the output that was being parsed, which made it
easily reproducible. It was indeed an issue in the Perl library. I've made
a fix, and the fix will be in the next push of the Perl client lib
Hi Phillip,
In that case, do you happen to have the BatchJobIds in which this error
occurred? It'll be helpful in identifying the source of the issue.
Thanks,
Shwetha, AdWords API Team.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://goog
Unfortunately we don't log the full SOAP response on failures (they are all
processed through the adwords perl library so they aren't typically of use
for debugging to us). On top of that, we implemented a work-around in
which we don't use the batch job service in order to not have this affect
Hi Phil,
Do you happen to have the SOAP request/response logs for the request which
encountered the OperationAccessDenied error? Please use *Reply privately to
author* when responding. An sample error looks like this:
http://www.w3.org/2001/XMLSchema-instance"; xsi:type=
"OperationAccessDenied
Relates to https://groups.google.com/forum/#!topic/adwords-api/aTOWJMBFH1M
Parsing OperationAccessDenied error objects using the above perl library
(Google::Ads::Common::ErrorUtils::get_source_operation_index() )is
returning undef. It appears that the adwords library code expects calling
get_