On Tue, 16 Mar 2004 10:31:44 -0600, james <[EMAIL PROTECTED]> wrote: >If there is no difference in the data request your troubled client is >making, then I would capture the entire client request to a log file and >check for malformed XML or header information. > >I have seen this happen when the web service provider timed out during >the data collection stage before sending the response to the requesting >client, but since you are only seeing this with one client I would >suspect the client request XML format. I have found several cases where >XML can be parsed using straight DOM syntax, but the .NET XML parser >will reject. The number one cause of this in my experience has been >repeating element names in child or sibling elements. >
Thanks james. I hadn't thought about the web service not receiving all the information. Maybe the client cannot transfer the information fast enough, and something has given up waiting. =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
