Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Oct 28, 2011 01:22 PM by Bobs Shekar
May 10, 2006 11:23 PM|LINK
May 11, 2006 03:47 AM|LINK
Mar 27, 2008 07:59 PM|LINK
Ben74, thank you so much for posting this. It is very easy to forget to add this in the web.config especially if you did not start the project as a webservice project. The error does not even give a clue that this is the issue. I was pulling my hair out
for a while with this error. Adding the above lines to the web.config fixed the error for me.
ASP.net webservice format unrecognized unexpectedly ending error
Apr 19, 2008 09:20 AM|LINK
Could be permissions, but I think, as was the main topic in the previous post, you first have to find out what the error is.
If you are using Internet Explorer, turn off (on the machine you see the useless error on)
Show friendly HTTP error messages
In tools, options, advanced.
May 14, 2008 06:30 PM|LINK
Thank you very much! Fixed my problem right up!
Sep 04, 2008 02:58 AM|LINK
Awesome, that fixed my problem perfectly.
Feb 02, 2009 02:31 PM|LINK
Thanks a ton.
I had the same problem as error message posted above. My problem was that I was calling the webservice with a plain old http form post - which worked fine when I built and ran the web service project locally - but once I deployed it I got the error.
What is with Microsoft with stuff like this? Why would they let this code run locally but not once deployed? If it works in one place it should work in the other...
Feb 05, 2009 01:29 AM|LINK
Likely the configuration was different between the local machine and the server you deployed to.
This isn't specific to Microsoft. This kind of thing is endemic to computers - it was happening to me over 30 years ago, before there
was a Microsoft. There will just naturally be differences between Development and Production. That implies that the behavior of your program could differ when it's deployed to Production. Proper QA can help ensure this does not happen in any bad way.
May 08, 2009 09:47 AM|LINK
May 19, 2009 01:51 PM|LINK
i found the solution. i put the following in my web.config
Thanks a lot... that was a quick solution that made my life easy