Web Service Error Messages

Error message:

Deserializing parameter <parameter name>: Could not find deserializer for type {<namespace>}<xml type name>

Cause:

This error occurs for an RPC-oriented method if the type specified in the WSDL file does not match with the type specified by the response message (in case of an RPC-oriented method call the type name occurs in the message). The namespace and the type must be the same.

Solution:

If the web service provider is a USoft web service and the service is published in the Definer, make sure that the namespace used in the Authorizer is the same as the namespace used in the Definer.

Error message:

A fatal error occurred during XML parse at line <line number> column <column number>. Invalid document structure.

Cause:

This usually happens if the USoft web client expects an XML message as parameter and the value is not in XML format.

Solution:

If the web service provider is a USoft web service and the method is a Document-oriented method or an RPC-oriented method with complex parameters, check that the values of output parameters are XML values.

Error message:

The request was unsuccessful due to an unexpected condition encountered by the server.

Cause:

This is a generic message that occurs if the Microsoft XML component is not installed, the Rules Service is not started, or the host and port number specified by the web service provider are not correct.

Solution:

•Check that the Microsoft XML component is installed.

•Check the host and port number specified for the web service.

•Check that the Rules Service is running.

If these checks do not identify the problem, refer to "Web Service Debugging Tips" for information on how to obtain more details of the cause of the problem.