I got that error every 2 weeks. Received an email from API Team in June
2012 that advised me to add one more line into the source code (I'm using
.NET client library)
Hi Minh,
AdWords API .NET library caches authTokens, and reuse them, it doesn't
create a new authToken everytime you create a new AdWordsUser. AuthTokens
expire after a while (about 2 weeks), this explains the issue you are
seeing.
The .NET client library can do an automatic retry to get a new authToken
when one expires. To use this feature, you need to set a value to
Config.RetryCount. Something like:
user.Config.RetryCount = 3;
Hope this helps. Let me know if you have more questions.
Cheers,
Anash P. Oommen,
AdWords API Advisor.
It actually didn't solve the problem. In the latest API, that line was
moved into the Config file
<AdWordsApi>
<add key="LogPath" value="" />
<add key="LogToConsole" value="false" />
<add key="LogToFile" value="false" />
<add key="MaskCredentials" value="true" />
<add key="LogErrorsOnly" value="false" />
<!-- Use this key to automatically retry a call that failed due to a
recoverable error like expired credentials. -->
<add key="RetryCount" value="3"/>
So, what I can do now? Restart the service in production server bi-weekly
to clear the cache.
On Monday, 2 April 2012 05:07:41 UTC-7, Zweitze wrote:
>
> Hi,
> Since April 1st we get AuthenticationError.GOOGLE_ACCOUNT_COOKIE_INVALID
> every time we call an API function - usually ServicedAccountService.get()
>
> Sample requestId: 0004bcaca5492e200aec2087000020f2
> Soap detail:
> <detail>
> <ApiExceptionFault xmlns="
> https://adwords.google.com/api/adwords/mcm/v201109"; xmlns:ns2="
> https://adwords.google.com/api/adwords/cm/v201109";>
> <ns2:message>AuthenticationError.GOOGLE_ACCOUNT_COOKIE_INVALID @
> Service[ServicedAccountService.get]</ns2:message>
>
> <ns2:ApplicationException.Type>ApiException</ns2:ApplicationException.Type>
> <ns2:errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:type="ns2:AuthenticationError">
> <ns2:fieldPath>
> </ns2:fieldPath>
> <ns2:trigger>
> </ns2:trigger>
>
> <ns2:errorString>AuthenticationError.GOOGLE_ACCOUNT_COOKIE_INVALID</ns2:errorString>
>
>
> <ns2:ApiError.Type>AuthenticationError</ns2:ApiError.Type>
> <ns2:reason>GOOGLE_ACCOUNT_COOKIE_INVALID</ns2:reason>
> </ns2:errors>
> </ApiExceptionFault>
> </detail>
>
> This happens on the production server only. Running in an development
> environment, with the *same* authentication token, gives no problems. We
> tried this with (far) over one hundred accounts, all giving this error.
>
> Thanks in advance,
> Zweitze.
>
> PS: I also mailed this to adwordsap...@google <javascript:>. Apparently
> that address isn't monitored that well anymore, last time it took six(!)
> days before I got a response. Please note this is very urgent for us.
>
>
>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
