Tracing Web Services Call-Out Problems
If an error occurs when calling out to a web service, Uniface generates error
-150 and provides details about the SOAP error in
$procerrorcontext.
| Error | Description | Possible reasons |
|---|---|---|
| Loading WSDL file failed | The URL of the WSDL cannot be loaded when activating the SOAP signature. | The URL is not valid or the Web server hosting the Web service is not running or is unavailable. |
| -150, UACTERR_UNKNOWN | Uniface creates the SOAP envelope to send the request to the Web service, and to receive and parse the returned reply. If an error occurs in this sequence, Uniface returns this error along with the error message received from the SOAP connector. | The error text that is returned gives a clue to the error. For example, a common error is caused by null values in parameters other than strings. For details, see the next section. |
SOAP Connector U1.0
If you use the Uniface SOAP connector U1.0, you can also use the TCP/IP trace utility of the Microsoft SOAP Toolkit to view the SOAP messages between a SOAP client and a service on the server.
To configure this utility:
- Make a local copy of the WSDL file and edit it.
- Change the SOAP signature so that the Web service call-out uses the modified WSDL.
For more information, see the documentation provided with the Microsoft SOAP Toolkit.
Alternatively, you can use another utility such as TCPMon (http://ws.apache.org/commons/tcpmon/download.cgi) to monitor SOAP messages.
