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

2013-10-24 Thread 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

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

2013-10-24 Thread Glyph
Simple indeed. that was exactly what was needed. it fixed the issue. Thanks for staying on this and figuring it out! On Thursday, October 24, 2013 10:58:28 AM UTC-4, Paul Matthews (AdWords API Team) wrote: Hi Glyph, Our .NET library creator informs me that this is a common problem and has

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

2013-10-21 Thread 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

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

2013-10-20 Thread 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. On Saturday, October 19, 2013 5:15:52 AM UTC-4, Paul Matthews (AdWords API Team) wrote: Hi Glyph, I too have viewed the

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

2013-10-20 Thread 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. On Sunday, 20 October 2013 18:37:07 UTC+1, Glyph wrote: The issue is with the RESPONSE, not the request. The response comes back, and has some chars near the

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

2013-10-19 Thread 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. On Thursday, 17 October 2013 21:58:11 UTC+1, Glyph wrote: upgraded

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

2013-10-17 Thread Glyph
upgraded to latest .net client library for adwords(16.2) same issue on some responeses: requestId0004e8f60a95f0400aed8a506e0c/requestId On Wednesday, October 16, 2013 12:32:55 PM UTC-4, Glyph wrote: I'm doing a mutate call on the AdGroudAd service using the .net client lib v 15.5 And

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

2013-10-16 Thread 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