Re: intermittent UNAUTHENTICATED errors: "The error code is not in this version"

[Anshu Tomar]

We also started having the same issue while using GoogleAdsService for pulling some reports. We are using the v11 version of the API and have been using it for a while now. The error comes randomly.

On Monday, November 14, 2022 at 3:07:56 PM UTC-5 Maria Cook wrote:

Hi, we started to see these intermittent errors about 2 hours ago and not sure what might be causing them. 

We use UserListService, OfflineUserDataJobService, and GoogleAdsService (to make search calls for user lists).

No changes have been made to our authentication / authorization setup or any of the API usage which have successfully working for a few months now, and some of the calls do succeed while others fail, even when they operate on the same UserList. 

We are calling v11 of the Google Ads API, using Python SDK  https://github.com/googleads/google-ads-python.

Please let me know if there is other information that can help diagnose the issue. Here is an example error:

Reason: [(<_InactiveRpcError of RPC that terminated with:
        status = StatusCode.UNAUTHENTICATED
        details = "Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project."
        debug_error_string = "{"created":"@1668455667.707321867","description":"Error received from peer ipv4:172.253.63.95:443","file":"src/core/lib/surface/call.cc","file_line":966,"grpc_message":"Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.","grpc_status":16}"
>, <_InactiveRpcError of RPC that terminated with:
        status = StatusCode.UNAUTHENTICATED
        details = "Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project."
        debug_error_string = "{"created":"@1668455667.707321867","description":"Error received from peer ipv4:172.253.63.95:443","file":"src/core/lib/surface/call.cc","file_line":966,"grpc_message":"Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.","grpc_status":16}"
>, errors {
  error_code {
    authentication_error: UNKNOWN
  }
  message: "The error code is not in this version."
}
request_id: "DQuky4Se37BNmlLc0a5GxQ"
, 'DQuky4Se37BNmlLc0a5GxQ')]

[Christian H.]

Same problem here: UNAUTHENTICATED / USER_PERMISSION_DENIED / AUTHORIZATION_ERROR errors since ~ 18:30 CET. (using java google-ads lib 21.0 / v11)

[Maria Cook]

I see now there is an incident posted for this time on status dashboard: https://ads.google.com/status/publisher/incidents/xemZL1ML4JrZeDuUs2pU, which is marked as resolved. 

Indeed we have not seen any more errors in the past couple hours, so hoping this is the end of it :) 

[Google Ads API Forum Advisor]

Hi everyone,

This is Carmela from the Google Ads API team. Thank you for raising this concern to us.

@Maria
Please note that I have to delete your first post in this forum thread as it contains your logs. Also, thank you for your confirmation that you are not seeing errors on your end anymore. 

Moving forward, based on our Google Ads Status Dashboard, there's indeed a reported issue where users see errors. Having said that, since Maria confirmed that they are not seeing errors on their end, @Anshu and @Christian, can you also confirm if you are still seeing errors on your end or it is already working fine?

Regards,

Carmela Google Ads API Team

ref:_00D1U1174p._5004Q2gOhVt:ref

[Christian H.]

Yes it works for me. The last error I see was at 20:46 UTC.

[Google Ads API Forum Advisor]

Hi Christian,

Thank you for getting back to us. I hope you are doing well today.
 

Our team is glad to hear that it works now. If you have further questions / concerns for our team, please feel free to get back to us. We will be happy to address it.
 

Regards,

Darwin Google Ads API Team

ref:_00D1U1174p._5004Q2gOhVt:ref

[Anshu Tomar]

The frequency of the error has definitely reduced. But, we are still getting it in some runs.

[Google Ads API Forum Advisor]

Hi Anshu,

Thank you for the reply.

For our team to further check and validate the errors you are getting in some runs, could you provide us with the updated complete API logs (request and response with request-id) generated on your end? Note that this can be requested or provided to the developer handling the Google Ads API transactions when logging of the API requests has been enabled. You may check here and click your client library for the specific guideline to enable it.

For REST interface requests, you can enable logging via the curl command by using the -i flag. This will cause the tool to include the HTTP response headers in the output.

You may then send the requested information via the Reply privately to the author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.

Best regards,

Heidi Google Ads API Team

​​​​​​​

ref:_00D1U1174p._5004Q2gOhVt:ref

[Anshu Tomar]

Hi,

Seems like the error is not coming anymore. We can close this thread. If it happens again, I will open up a new thread.
Thanks!