Error from web service - charset=utf-8

[John S]

Using VB.NET 2005, I created a Web Service that returns a dataset from a SQL
Server database.

In the same solution I created a test GUI with a Windows form to display the
results.

It worked fine on my development PC but when I moved the Web Service to a
server on our network I get the following error:

"Client found response content type of 'text/html; charset=utf-8', but
expected 'text/xml'."

Can anyone explain?

Thanks

[Steven Cheng[MSFT]]

Hello John,

As for the following exception message:

=======================
"Client found response content type of 'text/html; charset=utf-8', but
expected 'text/xml'."
=======================

it is usually caused by the server-side ASP.NET webservice has encountered
some error and throw out exceptions(not in webservice code, maybe at
initialize time). For such scenario, I suggest you perform the following
tests:

1. Use IE browser to visit the asmx service endpoint directly to see
whether you can view the default webservice description page and the test
page correct. If there is any error at compilation or initializtion time,
it will report error in browser.

2. When use webservice proxy to call the webservice, we can use some trace
tool to capture the SOAP message (request and response) transfered between
the client and server, you may get some useful information in it. The
"Trace Utility" in SOAP toolkit 3.0 is a useful trace tool you can use:

#SOAP Toolkit 3.0
http://www.microsoft.com/downloads/d...0DD-CEEC-4088-
9753-86F052EC8450&displaylang=en

BTW, have you sufficient permission to access the deployment server? If so,
you can check the event log on the server machine to see whether there is
any useful error entry specific to the webservice application.

Please let me know if the above things helps or if you have any new finding.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

This posting is provided "AS IS" with no warranties, and confers no rights.

[John S]

Steve,

I went on the server and used IE as suggested.

The error then was totally different and a quick search showed that the
ASP.NET version was wrong on the properties in IIS.

I thought I'd changed it already, but...

Any way, it now works

Many thanks

[Steven Cheng[MSFT]]

Thank's fine.

Glad that you've got it working.

Good luck!

Steven Cheng

Microsoft MSDN Online Support Lead