Hi,
Try tracing the message that is received at the server side. Also, it
isn't clear which side is throwing your "root missing" error message.
Since there are two messages and two senders involved (you send message
that represents your request, the server receives it. The error could
happen right here. The server sends a message back, and this message also
could be poorly formed.
Also, this problem can happen if you are reusing the envelope and adding a
second body child. The trace will let you see this.
Install a trace extension (available from gotdotnet.com) on your service
via a web.config change. Then run the trace.axd utility at the vroot of
your service in a browser, and send the message from your client. Then
send it again. Then refresh the trace.axd page. There should be two
requests logged, and you can compare what you expect to see to what you do
see to help you determine what the probable causes are.
Be sure to have trace="on" in your web.config as well.
Best regards
Dan Rogers
Microsoft Corporation
--------------------
>From: "Balasubramanian Ramanathan" <rbmanian@eth.net>
>Subject: ...Root Element is missing Error!
[quoted text clipped - 9 lines]
>NNTP-Posting-Host: a81-84-62-179.netcabo.pt 81.84.62.179
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09
phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.aspnet.webservices:27353
>X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
>
[quoted text clipped - 9 lines]
>
>Thanks & Regards