Response is not well-formed XML - using .net client libarary 15.5

[Glyph]

I'm doing a mutate call on the AdGroudAd service using the .net client lib v 15.5

And the response I'm getting looks like valid soap/xml when i look at it in fiddler, but i get an invalidoperationexception when reading the response saying that "Response is not well-formed XML".

Is there a known bad character or something in the response causing the .net web service client to throw this exception?

Here's the requestId that's giving me the problem.

<requestId>

        0004e8ddab5e6fc00aedc64600000f77

      </requestId>

[Glyph]

upgraded to latest .net client library for adwords(16.2)  same issue on some responeses:

<requestId>0004e8f60a95f0400aed8a5000006e0c</requestId>

[Paul Matthews (AdWords API Team)]

Hi Glyph,

I too have viewed the request in an XML browser and it seems to be formatted correctly. Do you have this issue on any other (smaller) requests? Or is it this particular request?

Regards,

- Paul, AdWords API Team.

[Glyph]

The issue is with the RESPONSE, not the request.   The response comes back, and has some chars near the beginning that make .net throw an invalidoperation exception.

[Paul Matthews (AdWords API Team)]

Apologies, I indeed meant response.

Is this happening on other requests too? Or only this one?

Regards,

- Paul, AdWords API Team.

[Glyph]

It happens intermittantly on calls to mutate on the adgroupcriterion service.

the adwords api client says the bad chars are near 1,1 in the response, so I'm guessing that there are some non-printable characters near the beginning of the response that are causing the issue.

I agree, If you just look at the response, it does 'appear' to be valid xml.

[Paul Matthews (AdWords API Team)]

Hi Glyph,

Our .NET library creator informs me that this is a common problem and has a standard fix.

.NET's WebRequest class trims the response to a default of 64K if it gets an http error response code. The AdWords API returns a failed response with a 500 code, and if the error response is too long (e.g. policy violation with stack trace), .NET trims the response, thus causing invalid xml error in the SOAP layer.

You should be able to resolve this by changing the App.config to include the following lines:

  <system.net>

    <settings>

      <httpWebRequest maximumErrorResponseLength="-1"  />

    </settings>

  </system.net>

Regards,

- Paul, AdWords API Team.

[Glyph]

Simple indeed.  that was exactly what was needed. it fixed the issue.

Thanks for staying on this and figuring it out!