Invalid schema: Not yet initialized

[Rob]

 Hello,

 Recently I'm facing the following error when trying to connect to the AdWords API: "Invalid schema: Not yet initialized"

  Using the the same connection with same parameters  (clinetid, developer token etc.) I was able to connect and get data from API's reports.

Could you please confirm what can be the reason of the issue taking into account my error message. (I can provide more connection details if needed)

Thanks,

Rob

[Google Ads API Forum Advisor Prod]

Hi Rob,

Thank you for reaching out. Can you please make sure that you have followed the steps mentioned in this guide while creating report definition and submitting request to Google server? If yes, could you please share the complete XML report definition schema in API used while generating reports along with the client customer id and error response for me to investigate this issue further? Please use Reply privately to author option while sharing the details.

Regards,
Nikisha Patel, Google Ads API Team

ref:_00D1U1174p._5001UKMBbW:ref

[Admin BI]

Hi Nikisha

I have shared my customer id in the private message. Do you happen to know what can trigger such error?

Best regards, 

Robert

[Google Ads API Forum Advisor Prod]

Hello,

Yes, we received your client customer id and the error response in the private message. Here is what I replied to that email:
"Could you please verify if your credentials are correct? Please try the below CURL request provided and see if you are able to generate the access token. If your credentials are correct, you should be able to generate an access token for the below CURL request.

curl https://www.googleapis.com/oauth2/v4/token \
-d refresh_token=your-refresh_token \
-d client_id=your-client-id \
-d client_secret=your-client-secret \
-d grant_type=refresh_token

If your credentials are incorrect or the issue persists, could you please try generating a new refresh token using this guide and retry your request. Please let me know if you still face any issues."

Regards,
Nikisha Patel, Google Ads API Team

ref:_00D1U1174p._5001UKMBbW:ref

[Julia K.]

Hello,

has this issue been solved? We have the very same problem. The credentials are correct and we were able to generate a new access token.

Regards,

Julia

[Google Ads API Forum Advisor Prod]

Hi Julia,

Could you please try generating new refresh token using this guide and retry your request as mentioned in my previous response? If the issue persists, could you please share the client customer id against which the API call is made and the email address using which the OAuth credentials are generated for me to investigate this further? Please use Reply privately to author option while sharing the details.

Regards,
Nikisha Patel, Google Ads API Team

ref:_00D1U1174p._5001UKMBbW:ref

[Julia K.]

Hi Nikisha,

do you have any updates on this? I sent you the credentials in a private message a little while ago.

It seems that we can call the API with other methods and that the problem only occurs when using the Microsoft Azure DataFactory. So might be you changed something in the API at the beginning of October that Microsoft has not adapted to?

Cheers,

Julia

[Google Ads API Forum Advisor Prod]

Hi Julia,

We haven't received the requested information privately and awaiting these details to assist you further. Could you please retry sending the requested details for me to investigate this further on my end? Also, no new changes are introduced in API that can cause this issue. You could refer to the Release Notes and blog post for all the updates in the API.

Regards,
Nikisha Patel, Google Ads API Team

ref:_00D1U1174p._5001UKMBbW:ref