That is part of my problem and why I am lost.
not using WSDL.
service. I spoke with another person yesterday who sent data to this
"Martin Honnen" <mahotrash@yahoo.de> wrote in message
news:udpTJrICFHA.3936@TK2MSFTNGP09.phx.gbl...
>
>
> Mark wrote:
>
> > It appears something is wrong with my soap message
> > itself. I'm using the
> > HttpWebRequest and HttpWebResponse objects to send/receive this data.
>
> Why? If you are using .NET (as HttpWebRequest suggests) then simply
> create a proxy class to use the web service, .NET has a tool called
> wsdl.exe to do exactly that to avoid anyone having to deal with SOAP
> itself (which is complex). The wsdl.exe tool reads the WSDL file
> describing the web service and generates .NET source code for a proxy
> class which you can compile and then include in your .NET project to
> easily access the web service transparently calling methods on the proxy
> without ever dealing with SOAP.
>
> As for your earlier message that looked like you were using VBScript,
> even there MS has a toolkit named SOAP toolkit that helps you with
> accessing web services without the need to construct the raw SOAP from
> hand. Look on
http://msdn.microsoft.com/ for SOAP toolkit, download it
> and check the examples on how to build a SOAP client with script.
>
>
>
> > The error I'm getting is
> >
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <soap:Envelope xmlns:soap="
http://schemas.xmlsoap.org/soap/envelope/" > > xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance" > > xmlns:xsd="
http://www.w3.org/2001/XMLSchema"> > > <soap:Body>
> > <soap:Fault>
> > <faultcode>soap:Client</faultcode>
> > <faultstring>Unable to handle request without a valid action
> > parameter. Please supply a valid soap action.</faultstring>
> > <detail />
> > </soap:Fault>
> > </soap:Body>
> > </soap:Envelope>
>
> Well SOAP over HTTP needs a custom HTTP header named SOAPAction which
> (untested and written from memory) needs to be alike
>
> SOAPAction: urn:Example1/HelloWorld
>
> for your web service so if you really want to use HttpWebRequest or
> Msmxl2.XMLHTTP to access a web service then you need to make sure you
> set that HTTP header (not SOAP header!) before sending your request.
>
> But as said, there are tools with both COM based application (like VB or
> VBScript or JScript) and .NET to free you from thinking about that
> stuff, you simply call a method and get a result in the language of your
> choice and the whole SOAP creation and parsing is done by the tools
> reading the WSDL description of the web service.
>
>
>
> --
>
> Martin Honnen
>
http://JavaScript.FAQTs.com/