soapenv:Server.generalException

1,686 views
Skip to first unread message

winnie

unread,
Jul 7, 2008, 3:57:14 AM7/7/08
to AdWords API Forum
Hi all,
During I tried to add a new campaign in the sandbox, I got the
following error:
Server.generalException
An internal error has occurred. Please retry your request.

I used API V12, in V11 it worked fine without any problem. (Of course
using dailyBudget instead of budgetAmount and budgetPeriod)

I sent the following request (I removed the values of the header):

- <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/
envelope/" xmlns:ns1="https://adwords.google.com/api/adwords/v12"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <SOAP-ENV:Header>
<ns1:useragent>The name if the User Agent</ns1:useragent>
<ns1:password>myPassword</ns1:password>
<ns1:email>myEmail</ns1:email>
<ns1:clientEmail>client_1+clientEmail</ns1:clientEmail>
<ns1:developerToken>myEmail++EUR</ns1:developerToken>
<ns1:applicationToken>AppToken</ns1:applicationToken>
</SOAP-ENV:Header>
- <SOAP-ENV:Body>
- <ns1:addCampaignList>
- <ns1:campaigns>
<ns1:budgetAmount>33000000</ns1:budgetAmount>
<ns1:budgetOptimizerSettings xsi:nil="true" />
<ns1:budgetPeriod>Daily</ns1:budgetPeriod>
<ns1:contentTargeting xsi:nil="true" />
<ns1:conversionOptimizerSettings />
<ns1:enableSeparateContentBids xsi:nil="true" />
<ns1:endDay xsi:nil="true" />
<ns1:geoTargeting xsi:nil="true" />
<ns1:id>0</ns1:id>
<ns1:languageTargeting xsi:nil="true" />
<ns1:name>#2 - Valami2</ns1:name>
<ns1:networkTargeting xsi:nil="true" />
<ns1:schedule xsi:nil="true" />
<ns1:startDay xsi:nil="true" />
<ns1:status>Paused</ns1:status>
</ns1:campaigns>
</ns1:addCampaignList>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>


The response was:

- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/
envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <soapenv:Header>
<responseTime soapenv:actor="http://schemas.xmlsoap.org/soap/actor/
next" soapenv:mustUnderstand="0" xmlns="https://adwords.google.com/api/
adwords/v12">65</responseTime>
<operations soapenv:actor="http://schemas.xmlsoap.org/soap/actor/
next" soapenv:mustUnderstand="0" xmlns="https://adwords.google.com/api/
adwords/v12">0</operations>
<units soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
soapenv:mustUnderstand="0" xmlns="https://adwords.google.com/api/
adwords/v12">0</units>
<requestId soapenv:actor="http://schemas.xmlsoap.org/soap/actor/
next" soapenv:mustUnderstand="0" xmlns="https://adwords.google.com/api/
adwords/v12">f3053c1054a3388ea164c2839f8cf605</requestId>
</soapenv:Header>
- <soapenv:Body>
- <soapenv:Fault>
<faultcode>soapenv:Server.generalException</faultcode>
<faultstring>An internal error has occurred. Please retry your
request.</faultstring>
- <detail>
- <ns1:fault xmlns:ns1="https://adwords.google.com/api/adwords/v12">
<ns1:code>0</ns1:code>
<ns1:message>An internal error has occurred. Please retry your
request.</ns1:message>
</ns1:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

AdWords API Advisor

unread,
Jul 7, 2008, 1:12:46 PM7/7/08
to AdWords API Forum
Hello Winnie,

The internal exception is being caused by the
<ns1:conversionOptimizerSettings /> element in your request. If it
were either omitted completely, or if it
were marked as nil (i.e. <ns1:conversionOptimizerSettings
xsi:nil="true" />) then the request should work fine, but as it is,
our SOAP server attempts to deserialize it and runs into a
NullPointerException.

If you're having trouble figuring out how to either omit or
explicitly mark that element as nil, let us know what language and
client library you're using as well as the relevant code snippet and
we should be able to help.

Cheers,
-Jeff Posnick, AdWords API Team

winnie

unread,
Jul 8, 2008, 7:15:48 AM7/8/08
to AdWords API Forum
Hi Jeff,
Thank you for your response. Unfortunatelly I cannot set it to nil,
because conversionOptimizerSettings is not nillable, I checked it in
the WSDL. But omitting the whole conversionOptimizerSettings solved my
problem, thx again.

On júl. 7, 19:12, AdWords API Advisor <adwordsapiadvi...@google.com>
wrote:
Reply all
Reply to author
Forward
0 new messages