Hello,
Okay, if the MCC and AdWords accounts are properly linked, could you
make sure that you're not accidentally going against the Sandbox
environment?
What would be easiest at this point is if you could turn on SOAP
logging and take a look at the XML of the SOAP fault you're getting
back. C
I confirm no problem with MCC and AdWords account.
so it could a quota problem?
thanks
On 20 Mag, 19:54, Heisenbug wrote:
> As for your questions I'll check it soon,
> as for now, if I've api unit to zero could I've this problem too?
> thanks again
>
> On 20 Mag, 19:39, AdWords API Advis
As for your questions I'll check it soon,
as for now, if I've api unit to zero could I've this problem too?
thanks again
On 20 Mag, 19:39, AdWords API Advisor
wrote:
> Hello,
>
> I'm afraid that doesn't really answer my questions. Assuming you're
> sending request to the Production environment
Hello,
I'm afraid that doesn't really answer my questions. Assuming you're
sending request to the Production environment, have you confirmed that
the MCC account in context.email has access to the child AdWords
account whose customer id is given in context.clientId?
Cheers,
-Jeff Posnick, AdWor
I use this code to acces production account..
Hashtable headers = new Hashtable();
headers.put("email", context.email);
headers.put("password", context.pswadwords);
headers.put("useragent", context.useragent);
headers.put("developerToken", context.developertoken);
headers.put("applicationToke
Hello,
Are you trying to access the Production or Sandbox environments?
The error you're getting would indicate that you're specifying
"842-310-1923" as the clientCustomerId SOAP request header, but the
email header you're specifying isn't a valid MCC for that account. If
you're going against
