Monday, March 26, 2012

Web Service Error

When trying to run a windows application on one machine that accesses a web service on another I get the following error message:

client found response content type of 'text/html; charset=utf-8' but expected 'text/xml'

What might this mean?

It's written in visual basic .net.You faced this problem in 2002 i think you must have been over it by now .... as am facing it badly and need its solution as sooon as possible ... Kindly help me out ... you are my last hope...

harris_moin@.hotmail.com
Wow, that was a while ago. I've run into alot of things with web services since then so I'm not sure what my fix was. Describe to me how your system is set up and what you're doing to get that error. I may be able to help from there.
Hmmm ...

Actually i am using asp.net and visual c# in the first page am using popchart control which is working fine in the second page am using snowflake control there its giving me this problem.

Client found response content type of 'text/html', but expected 'text/xml'

On my machine where i have the whole vs.net installed its working fine. But am trying to run it on a machine where i have just installed vs.net framework 1.1 ,,,, with the other softwares i need ... everything seems to be working fine but at snowflake page it gives me this error.

I have xml sdk,popcharts,snowflakes,iis, and a few more things installed on my system to run this application.

Hope this info helps. :)
I actually just duplicated the error. I have an appSettings tag in my Web.Config file that contains a connection string that I use throughout my application. I was able to duplicate the error by removing a double quote from my connectionstring:

<appSettings><add key="ConnectString" value="Server=MyServer;Uid=sa;pwd=;database=MyDatabase"/>

</appSettings>

In this case I removed the double quote after the word 'MyDatabase'. When I tried to run my app I got the same error you're getting. My first instinct without seeing your code is to say that you've got something wrong with your web.config file.

I hope that helps a little.
still no luck :mad: :mad: :mad: :mad: :confused:

0 comments:

Post a Comment