Re: SOAP Toolkit client problems with DotNet Service



Sounds like the fully qualified name of your object has changed when you
repointed it.
try changing your proxy's business objects to the new namespace.

HTH.

--
With Regards
Shailen Sukul
..Net Architect
(MCPD: Ent Apps, MCSD.Net MCSD MCAD)
Ashlen Consulting Services
http://www.ashlen.net.au
"Michael Russell" <mr_b15h0p@xxxxxxxxxxx> wrote in message
news:eVWMEZnNHHA.5016@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,
I'm trying to get a client working with my ASP.NET web service. The
client's been working great up to this point with a SOAP Toolkit-generated
service based on a VB COM library.

On the client side, I'm calling the web service here:
--
Dim soapClient As SoapClient30
Dim xmlList As IXMLDOMNodeList

Set soapClient = GetSoapConnection
Set xmlList = soapClient.GetGroups(SYSTEM_NAME)
--
and at that last line, I get a "424 - Object required" error.

I haven't modified the code at all except to point to the new WSDL.

In the debugger I can see that "soapClient.GetGroups(SYSTEM_NAME)"
contains a list of Nodes, so it's calling the service and successfully
retrieving the message, but it refuses to process it.

Any guidance on this would be GREATLY appreciated.


.



Relevant Pages

  • Re: Application hangs
    ... Public soapClient As New SoapClient30 ... Set soapClient = New SoapClient30 ... my code hangs here ...
    (microsoft.public.vb.general.discussion)
  • Re: Application hangs
    ... Public soapClient As New SoapClient30 ... Set soapClient = New SoapClient30 ... Msgbox soapClient.Testconnection ...
    (microsoft.public.vb.general.discussion)

Loading