XML errors in webservice call

[Colin Young]

I am creating some code that runs in Excel using VSTO. I am trying to get
some xml from a webservice, using the following code:

GBWPipeline.PipelineService pipeline = new GBWPipeline.PipelineService();
string xml = pipeline.GetOfferSale(OfferSheetId, CustomerId).GetXml();

I get a "There is an error in XML document. (1, 220)" message. If I execute
the same method from WebServiceStudio, it works fine (using the same values
for the parameters) and returns the xml that I expect (and doesn't complain
about any errors). It also works in a normal WinForms application. It is
only inside Excel that it fails.

I have other Excel workbooks that also retrieve xml from webservices and
they work. Thanks for any suggestions.

Colin

[Tom Egginger]

Hello Colin,

I actually have not used vsto - but I faced a similar
problem using MSXML (using vb6) accessing a .net
WebService .

A .Net TestClient Application has been able to call the
WebService without any problems, but MSXML failed with
an "invalid unicode character"-error.

I assume there are some "differences" handling unicode
(invalid or not) between MSXML and others (like IE, .Net,
XMLSpy,...) - is it possible, that vsto is based on MSXML?

I finally ended up (workaround solution due to lack of
time) decoding the "problematic" fields as base64...

Hope this helps

Regards,

Tom

-----Original Message-----
I am creating some code that runs in Excel using VSTO. I am trying to getsome xml from a webservice, using the following code:

GBWPipeline.PipelineService pipeline = new GBWPipeline.PipelineService();string xml = pipeline.GetOfferSale(OfferSheetId, CustomerId).GetXml();
I get a "There is an error in XML document. (1, 220)" message. If I executethe same method from WebServiceStudio, it works fine (using the same valuesfor the parameters) and returns the xml that I expect (and doesn't complainabout any errors). It also works in a normal WinForms application. It isonly inside Excel that it fails.

I have other Excel workbooks that also retrieve xml from webservices andthey work. Thanks for any suggestions.

Colin
.

[Colin Young]

Thanks. I'll keep that in mind, but right now there is nothing in the
problem XML that isn't also in other XML that is working in different Excel
solutions (at least as far as I can tell). I'll be doing some more testing
today to see if I can turn up any clues, so maybe this tip will help there.

Colin

"Tom Egginger" <to*********@ggmmxx.net> wrote in message
news:25*****************************@phx.gbl...

Hello Colin,

I actually have not used vsto - but I faced a similar
problem using MSXML (using vb6) accessing a .net
WebService .

A .Net TestClient Application has been able to call the
WebService without any problems, but MSXML failed with
an "invalid unicode character"-error.

I assume there are some "differences" handling unicode
(invalid or not) between MSXML and others (like IE, .Net,
XMLSpy,...) - is it possible, that vsto is based on MSXML?

I finally ended up (workaround solution due to lack of
time) decoding the "problematic" fields as base64...

Hope this helps

Regards,

Tom

-----Original Message-----
I am creating some code that runs in Excel using VSTO. I

am trying to get

some xml from a webservice, using the following code:

GBWPipeline.PipelineService pipeline = new

GBWPipeline.PipelineService();

string xml = pipeline.GetOfferSale(OfferSheetId,

CustomerId).GetXml();

I get a "There is an error in XML document. (1, 220)"

message. If I execute

the same method from WebServiceStudio, it works fine

(using the same values

for the parameters) and returns the xml that I expect

(and doesn't complain

about any errors). It also works in a normal WinForms

application. It is

only inside Excel that it fails.

I have other Excel workbooks that also retrieve xml from

webservices and

they work. Thanks for any suggestions.

Colin
.