Hello Danial,

Right on target! That was the problem and it's solved now. Thank you so 
much for your patience and kind support.

Best regards,
Bernardo

Quinta-feira, 10 de Janeiro de 2013 11:23:40 UTC, Danial Klimkin escreveu:
>
> Hello Bernardo,
>
>
> It sounds like we are getting closer! First of all, you can email me 
> directly in the groups by using drop down list on the right and choosing 
> "Reply to author".
>
> Now, the request you are sending is valid for ClientLogin only. For OAuth 
> you need to remove this from the SOAP:
>
>   <authToken>{2}</authToken>" 
>
> and add the bearer-type OAuth token in the HTTP headers (again, the 
> library would do that for you).
>
> The HTTP header should look like:
>
> Authorization: Bearer <oauth access token>
>
> So you can use something like:
>
>   webRequest.Headers.Add("Authorization", String.Format("Bearer {2}", 
> token))
>
>
> -Danial, AdWords API Team.
>
>
> On Wednesday, January 9, 2013 8:26:00 PM UTC+4, Bernardo Alves wrote:
>>
>> Hello Danial,
>>
>> Thanks again for your support. The endpoint is correct.
>>
>> I managed to capture the xml response alon with the "(500) Internal 
>> Server Error" and the actual error is GOOGLE_ACCOUNT_COOKIE_INVALID. I'm 
>> sorry, I can't find your email to send you the full xml response... (or G+).
>>
>> The strange thing about this error is that I can use the same OAuth 
>> credentials to pull reports against the 
>> https://adwords.google.com/api/adwords/reportdownload/v201206 service. 
>> If it were an authorization issue, the the error message would be 
>> different, right? So why do I get an authentication error?
>>
>> I'm sorry to persist on solving this problem. Would there be an 
>> alternative way to to obtain the list of managed client IDs of my MCC 
>> account, so I can pull reports for each of them?
>>
>> Best Regards,
>> Bernardo
>>
>> Quarta-feira, 9 de Janeiro de 2013 11:46:58 UTC, Danial Klimkin escreveu:
>>>
>>> Hello Bernardo,
>>>
>>>
>>> Make sure the endpoint you are sending the request to matches the 
>>> namespace. It should be 
>>>
>>>  
>>> https://adwords.google.com/api/adwords/mcm/v201209/ManagedCustomerService
>>>
>>> Also, see article on how to capture SOAP messages with the DotNet 
>>> library:
>>>
>>>   
>>> https://code.google.com/p/google-api-adwords-dotnet/wiki/HowToCaptureSoapMessages
>>>
>>>
>>> -Danial, AdWords API TEam.
>>>
>>>
>>>
>>> On Wednesday, January 9, 2013 2:43:20 PM UTC+4, Bernardo Alves wrote:
>>>>
>>>> Hello Danial,
>>>>
>>>> I am using an account which I believe is MCC, with access level 
>>>> configured as "Administrative Access". I work for a media agency and we 
>>>> handle many client accounts. I have also tried with the "Client 
>>>> Manager"account we use, which is configured with "User interface and API" 
>>>> access type. They both fail with the same error.
>>>>
>>>> In the meantime, since the .net environment didn't offer any more 
>>>> details besides "(500) Internal Server Error" I sent the request throgh 
>>>> the 
>>>> OAuth playground. The error persists, but I got a response with additional 
>>>> xml, as you asked, which might be useful:
>>>>
>>>> HTTP/1.1 500 Internal Server Error
>>>> Content-length: 219
>>>> X-xss-protection: 1; mode=block
>>>> X-content-type-options: nosniff
>>>> X-google-cache-control: remote-fetch
>>>> -content-encoding: gzip
>>>> Server: GSE
>>>> Reason: Internal Server Error
>>>> Via: HTTP/1.1 GWA
>>>> Cache-control: private, max-age=0
>>>> Date: Wed, 09 Jan 2013 10:25:44 GMT
>>>> X-frame-options: SAMEORIGIN
>>>> Content-type: text/xml; charset=UTF-8
>>>> Expires: Wed, 09 Jan 2013 10:25:44 GMT
>>>>
>>>> <soap:Envelope 
>>>> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><soap:Fault><faultcode>soap:VersionMismatch</faultcode><faultstring>INVALID_VERSION</faultstring></soap:Fault></soap:Body></soap:Envelope>
>>>>
>>>>
>>>> Any ideas about this INVALID_VERSION thing? Thanks again for your kind 
>>>> support.
>>>>
>>>> Best regards,
>>>> Bernardo
>>>>
>>>>>
>>>>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en



Reply via email to