Hello Marek,
From your description, you're getting the following exception when
consuming a certain webservice on a partiuclar client machine, correct?
[quoted text, click to view] >>>>>>>>>>>>>>
System.Xml.XmlException: There is an unclosed literal string. Line 1,
<<<<<<<<<<<<<<
Based on my experience, such exception is normally caused by some
parameters passed in webmethod contains invalid string. For example, when
you directly pass string parameter that contains XML reserved
characters(such as < > & ), it will make the SOAP xml message
corrupted. Here is a web thread discussing on this:
http://forums.microsoft.com/msdn/showpost.aspx?postid=14221&siteid=1 Also, from your test, you mentioned that the error occured even before soap
extension be able to log the message ,correct? That means the problem
occurs at the very begining (at client) when the runtime try parsing the
serialized soap XML content. Based on the code snippet you provided, the
webmethod's signature is as below:
==============
HelloWorld(HelloWorldRequest helloWorldRequest)
==============
So the only possible cause if the HelloWorldRequest class(regardless of
any environment &platform problem), would you provide detail definiation of
this body class. And is that particular problem client always pass some
particular string data into the HelloWorldRequest instance?
In addition, for that problem machine, you can check its .net framework
version and latest service pack install status, compare it with other
working client to see whether there is any difference.
Please feel free to let me know if you have any other finding on this.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx. ==================================================