MSSOAP errors

[Doug]

On a server that we run automated apps on, that has VB code that uses
the MSSoap tool kit to access a web service, we periodically get these
errors:

Soap error: XML Parser failed at linenumber 1, lineposition 0, reason
is: No data is available for the requested resource.

Soap error: Loading of the WSDL file failed.

Soap error: One of the parameters supplied is invalid..

This happens at varying times and only for a very short time but it
causes our applications to go nuts. Then everything clears out and
it's fine.

Does anyone know what these errors are caused by?

[=?Utf-8?B?RHVhbmUgQXJub2xk?=]

I think that possibly you have a Function or Subroutine that uses parameters
in the SOAP service that's being accessed by a client application. The
application is passing the wrong type of parameter to the Function or
Subroutine, like Long when it should be Interger, String when it should be
Long or something like that, which is casusing the problem. Or some object
that's not Serialized is being passed to the SOAP Service.

You can set the SoapService.Timeout = -1 'Infinite timeout so you can debug
the SOAP service and see what is happening when it's accessed.

Duane :)

"Doug" wrote:

On a server that we run automated apps on, that has VB code that uses
the MSSoap tool kit to access a web service, we periodically get these
errors:

Soap error: XML Parser failed at linenumber 1, lineposition 0, reason
is: No data is available for the requested resource.

Soap error: Loading of the WSDL file failed.

Soap error: One of the parameters supplied is invalid..

This happens at varying times and only for a very short time but it
causes our applications to go nuts. Then everything clears out and
it's fine.

Does anyone know what these errors are caused by?

[Doug]

I think that possibly you have a Function or Subroutine that uses parameters

in the SOAP service that's being accessed by a client application.

This is all our code does below, I'm not sure what would be passed in
wrong though?

Dim objSoap as New MSSOAPLib30.SoapClient30
objSoap.MSSoapInit (strWebServicePathValue)
objSoap.WebServiceMethodName(strValue)

You can set the SoapService.Timeout = -1 'Infinite timeout so you can debug
the SOAP service and see what is happening when it's accessed.

The Soap Client doesn't appear to have a Timeout value. The only
methods, properties that the Soap Client has are:
ClientProperty
ConnectorProperty
Detail
FaultActor
FaultCode
FaultCodeNamespace
FaultString
HeaderHandler
MSSoapInit
MSSoapInit2