New error starting last night: org.xml.sax.SAXException: Invalid element in com.google.api.ads.adwords.axis.v201601.cm.ExtensionSetting - ExtensionSetting.Type

233 views
Skip to first unread message

joel

unread,
May 6, 2016, 8:26:13 AM5/6/16
to AdWords API Forum

It looks like the CampaignExtensionSettingService is now returning a new element in the SOAP XML that's unrecognized. This started happening yesterday. It's causing the SAX parser and API call to fail. Any idea how to fix? Do we need to pull the newest client library? Below is a sanitized response XML showing the new field. Thanks!


Joel


<?xml version="1.0" encoding="UTF-8"?>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

    <soap:Header>

        <ResponseHeader xmlns="https://adwords.google.com/api/adwords/cm/v201601">

            <requestId>0005322b73b334600a815112f90f1db6</requestId>

            <serviceName>CampaignExtensionSettingService</serviceName>

            <methodName>get</methodName>

            <operations>0</operations>

            <responseTime>482</responseTime>

        </ResponseHeader>

    </soap:Header>

    <soap:Body>

        <getResponse xmlns="https://adwords.google.com/api/adwords/cm/v201601">

            <rval>

                <totalNumEntries>1</totalNumEntries>

                <Page.Type>CampaignExtensionSettingPage</Page.Type>

                <entries>

                    <campaignId>1234</campaignId>

                    <extensionType>SITELINK</extensionType>

                    <extensionSetting>

                        <extensions xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="SitelinkFeedItem">

                            <feedId>1234</feedId>

                            <feedItemId>1234</feedItemId>

                            <status>ENABLED</status>

                            <feedType>SITELINK</feedType>

                            <ExtensionFeedItem.Type>SitelinkFeedItem</ExtensionFeedItem.Type>

                            <sitelinkText>Text</sitelinkText>

                            <sitelinkLine2>Text</sitelinkLine2>

                            <sitelinkLine3>Text</sitelinkLine3>

                            <sitelinkFinalUrls>

                                <urls>http://mysite.com</urls>

                            </sitelinkFinalUrls>

                        </extensions>

                        </extensions>

                        <ExtensionSetting.Type>ExtensionSetting</ExtensionSetting.Type>

                    </extensionSetting>

                </entries>

            </rval>

        </getResponse>

    </soap:Body>

</soap:Envelope>

Alex Jones

unread,
May 6, 2016, 12:07:38 PM5/6/16
to AdWords API Forum
I'm also getting this error.

Michael Cloonan (AdWords API Team)

unread,
May 6, 2016, 1:12:00 PM5/6/16
to AdWords API Forum
Hello,

Are you requesting the ExtensionType field in your get request? That field in the selector is what causes this field to be returned.

In any case, if the Java library is unable to parse the field, then you should file a bug at the Java library's issue tracker: https://github.com/googleads/googleads-java-lib/issues

Regards,
Mike, AdWords API Team

Alex Jones

unread,
May 6, 2016, 1:15:23 PM5/6/16
to AdWords API Forum
We are requesting it, and we've been successfully processing using that field for several months now. We're not recently redeployed our Adwords tool suite, and this error first occurred yesterday, so I'm wondering if these was an unintended change in the Adwords API.  I'll open a ticket as requested. 

Michael Cloonan (AdWords API Team)

unread,
May 6, 2016, 1:20:13 PM5/6/16
to AdWords API Forum
Hello,

I want to narrow down whether this was a change with the XML that the AdWords API returns, or a change in the Java library's ability to parse the XML. Do you happen to have a log from before, when this was still working fine, so that we can see if the SOAP response included this field?

If the SOAP XML from the API has changed overnight unexpectedly, I will check with engineering to see what's going on.

Regards,
Mike, AdWords API Team

Alex Jones

unread,
May 6, 2016, 1:29:55 PM5/6/16
to AdWords API Forum
I do not have any SOAP logs from before the issue occurred, but I am currently working to reproduce the issue and generate some SOAP in our test account. I'll send that along once I have it.

I do have some of our application logs that show it was correctly interacting with Ad Extensions on May 3rd, but they don't provide any Soap diagnostics with them.

Our logs indiciate We first encounter this Error on 2016-05-05 13:23:14 EST. I don't know if that is helpful. Additionally, our last deploy of our Adwords Suite was 2016-04-20, so I feel it's unlikely something changed in our toolsuite. 

joel

unread,
May 6, 2016, 1:57:56 PM5/6/16
to AdWords API Forum
I don't have any SOAP logs from before it occurred either. We also haven't updated the Java library so it seems like it must be an unexpected change in the XML that the API returns.

And to answer your question we are requesting ExtensionType in both the selector fields and in a predicate, "ExtensionType = 'SiteLink'"

-Joel

Michael Cloonan (AdWords API Team)

unread,
May 6, 2016, 2:08:03 PM5/6/16
to AdWords API Forum
Hello,

Since this seems to be a common issue (I've gotten one other report of this outside of this thread as well), I've reached out to engineering to see if they know what's different. I will post here when I hear something back.

Regards,
Mike, AdWords API Team

Alex Jones

unread,
May 6, 2016, 2:08:11 PM5/6/16
to AdWords API Forum
I'm still working on getting SAOP, but I've noticed it's an intermittent problem. We retried several of the failed requests, and a majority succeed, but some remained failed. Perhaps this is a routing issue?


On Friday, May 6, 2016 at 8:26:13 AM UTC-4, joel wrote:

Antonio Parraga

unread,
May 6, 2016, 4:36:22 PM5/6/16
to AdWords API Forum
Same here:

org.xml.sax.SAXException: Invalid element in com.google.api.ads.adwords.axis.v201509.cm.ExtensionSetting - ExtensionSetting.Type


We haven´t touch anything in our code :(

Michael Cloonan (AdWords API Team)

unread,
May 10, 2016, 10:03:30 AM5/10/16
to AdWords API Forum
Hello,

I have confirmed that this was an unintended change on our side and that engineering is working on reverting the behavior. I will follow up here when the fix is live.

Regards,
Mike, AdWords API Team

Michael Cloonan (AdWords API Team)

unread,
May 11, 2016, 1:16:54 PM5/11/16
to AdWords API Forum
Hello,

This fix is now live. I just tested it myself to confirm. If you're still experiencing this issue, please let me know so that I can follow up with engineering.

Regards,
Mike, AdWords API Team
Reply all
Reply to author
Forward
0 new messages