posted 8 years ago
Its highly unlikely that the endpoint is at http://cwcdev.corporate.act.org/schedule/ALMVTC.WSDL - that is the URI to the WSDL that describes the endpoint. The actual endpoint could be http://cwcdev.corporate.act.org/schedule. However the endpoint's URI can be found inside the port soap binding inside the service definition of the WSDL. It would be a lot easier to diagnose the problem if you posted the contents of the ALMVTC.WSDL file. That basically describes what the request and response should look like. It would also help if you intercepted a successful request/response pair (from the VB Script you posted) with Apache TCPMon and posted the contents here - this is necessary in case the WSDL doesn't tell the whole story and some XML gets stuffed in a "string".