InternalApiError in AdGroupExtensionSettingService

37 views
Skip to first unread message

Евгений Лебедев

unread,
Aug 21, 2015, 9:00:31 AM8/21/15
to AdWords API Forum
Hello. I'm tryign to create CallFeed in Adgroup and get InternalApiError. Help please to figure out what is the problem.

REQUEST
Connection: Keep-Alive
User-Agent: PHP-SOAP/5.6.10-1+deb.sury.org~trusty+1, gzip
Accept-Encoding: gzip, deflate
Content-Encoding: gzip
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
Content-Length: 576
Authorization: Bearer ***

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="https://adwords.google.com/api/adwords/cm/v201506" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 
<SOAP-ENV:Header>
   
<ns1:RequestHeader>
     
<ns1:clientCustomerId>3356694810</ns1:clientCustomerId>
     
<ns1:developerToken>***</ns1:developerToken>
     
<ns1:userAgent>***</ns1:userAgent>
   
</ns1:RequestHeader>
 
</SOAP-ENV:Header>
 
<SOAP-ENV:Body>
   
<ns1:mutate>
     
<ns1:operations>
       
<ns1:operator>ADD</ns1:operator>
       
<ns1:operand>
         
<ns1:adGroupId>19873527426</ns1:adGroupId>
         
<ns1:extensionType>CALL</ns1:extensionType>
         
<ns1:extensionSetting>
           
<ns1:extensions xsi:type="ns1:CallFeedItem">
             
<ns1:callPhoneNumber>044-529-23-67</ns1:callPhoneNumber>
             
<ns1:callCountryCode>UA</ns1:callCountryCode>
             
<ns1:callTracking>false</ns1:callTracking>
             
<ns1:callOnly>false</ns1:callOnly>
             
<ns1:callConversionType/>
           
</ns1:extensions>
         
</ns1:extensionSetting>
       
</ns1:operand>
     
</ns1:operations>
   
</ns1:mutate>
 
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>


RESPONSE
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset=UTF-8
Content-Encoding: gzip
Date: Fri, 21 Aug 2015 08:24:11 GMT
Expires: Fri, 21 Aug 2015 08:24:11 GMT
Cache-Control: private, max-age=0
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Content-Length: 547
Server: GSE

<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 
<soap:Header>
   
<ResponseHeader xmlns="https://adwords.google.com/api/adwords/cm/v201506">
     
<requestId>00051dcdfe0b45700a810041b304f3f2</requestId>
     
<serviceName>AdGroupExtensionSettingService</serviceName>
     
<methodName>mutate</methodName>
     
<operations>1</operations>
     
<responseTime>558</responseTime>
   
</ResponseHeader>
 
</soap:Header>
 
<soap:Body>
   
<soap:Fault>
     
<faultcode>soap:Server</faultcode>
     
<faultstring>[InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ com.google.ads.api.services.common.error.InternalApiError.&lt;init&gt;(InternalApiErro]</faultstring>
     
<detail>
       
<ApiExceptionFault xmlns="https://adwords.google.com/api/adwords/cm/v201506">
         
<message>[InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ com.google.ads.api.services.common.error.InternalApiError.&lt;init&gt;(InternalApiErro]</message>
         
<ApplicationException.Type>ApiException</ApplicationException.Type>
         
<errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="InternalApiError">
           
<fieldPath/>
           
<trigger/>
           
<errorString>InternalApiError.UNEXPECTED_INTERNAL_API_ERROR</errorString>
           
<ApiError.Type>InternalApiError</ApiError.Type>
           
<reason>UNEXPECTED_INTERNAL_API_ERROR</reason>
         
</errors>
       
</ApiExceptionFault>
     
</detail>
   
</soap:Fault>
 
</soap:Body>
</soap:Envelope>

Josh Radcliff (AdWords API Team)

unread,
Aug 24, 2015, 10:04:38 AM8/24/15
to AdWords API Forum
Hi,

That looks like an issue on our side. I've raised this with the engineering team and will post back as soon as I have an update.

Thanks,
Josh, AdWords API Team
Message has been deleted

Eugene Lebediev

unread,
Aug 25, 2015, 2:45:51 AM8/25/15
to AdWords API Forum
Thanks for reply. Looking forward to fix.

Josh Radcliff (AdWords API Team)

unread,
Sep 11, 2015, 2:41:48 PM9/11/15
to AdWords API Forum
Hi Eugene,

The fix for this issue is in. Please let me know if you still see this error occurring.

Thanks,
Josh, AdWords API Team
Reply all
Reply to author
Forward
0 new messages