v200909 error setting Campaign Monthly Budget

[pete]

Hi

I'm migrating our dot Net interface with the Adwords API to utilise
v200909; as per Google recommendations, I'm also migrating to the
Adwords dot net client library instead of generating proxy stubs from
the WSDL's (due to the Namespace conflict).

During testing, I attempted to set a Campaign Monthly budget where it
is not allowed.

Using v13 and associated WSDL proxies I'm able to parse a validation
error "One or more input elements failed validation. : This customer
does not have access to monthly budgets".
This is useful.

Using the dot net client and v200909 - I get an ambiguous response
"InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @" - (SOAP response
below).
This is not useful.

Do I need to do anything else to get at the underlying exception or is
this all I can get?

regards

pete


<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<ResponseHeader xmlns="https://adwords.google.com/api/adwords/cm/
v200909">
<requestId>60dafca05d328ca9b73ddb4e0cd07c3d</requestId>
<operations>1</operations>
<responseTime>389</responseTime>
<units>1</units>
</ResponseHeader>
</soap:Header>
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ </
faultstring>
<detail>
<ApiExceptionFault xmlns="https://adwords.google.com/api/
adwords/cm/v200909">
<message>InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ </
message>
<ApplicationException.Type>ApiException</
ApplicationException.Type>
<errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance" xsi:type="InternalApiError">
<fieldPath>
</fieldPath>
<trigger>
</trigger>
<ApiError.Type>InternalApiError</ApiError.Type>
<reason>UNEXPECTED_INTERNAL_API_ERROR</reason>
</errors>
</ApiExceptionFault>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>

[AdWords API Advisor]

Hi Pete,

I'm glad that you are starting to migrate to the v2009 API. This
particular error should have been returned in a more identifiable way,
so you can catch and handle it client side. I'll work with the core
engineering team to have this fixed. Thanks for bringing this issue
to our attention.

Best,
- Eric Koleda, AdWords API Team.