Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
When web service requests fail, the database server generates standard errors that appear in your browser. These errors are assigned numbers consistent with the protocol standards.
If the service is a SOAP service, faults are returned to the client as SOAP faults as defined in the SOAP version 1.1 standard:
When an error in the application handling the request generates a SQLCODE, a SOAP Fault is returned with a faultcode of Client, possibly with a sub-category, such as Procedure. The faultstring element within the SOAP Fault is set to a detailed explanation of the error and a detail element contains the numeric SQLCODE value.
In the event of a transport protocol error, the faultcode is set to either Client or Server, depending on the error, faultstring
is set to the HTTP transport message, such as
404 Not Found, and the detail element contains the numeric HTTP error value.
SOAP Fault messages generated due to application errors that return a SQLCODE value are returned with an HTTP status of
If the client cannot be identified as a SOAP client, then the appropriate HTTP error is returned in a generated HTML document.
The following are some of the typical errors that you may encounter:
|301||Moved permanently||Server||The requested page has been permanently moved. The server automatically redirects the request to the new location.|
|304||Not Modified||Server||The server has decided, based on information in the request, that the requested data has not been modified since the last request and so it does not need to be sent again.|
|307||Temporary Redirect||Server||The requested page has been moved, but this change may not be permanent. The server automatically redirects the request to the new location.|
The HTTP request is incomplete or malformed.
Authorization is required to use the service, but a valid user name and password were not supplied.
You do not have permission to access the database.
The named database is not running on the server, or the named web service does not exist.
The maximum connection idle time was exceeded while receiving the request.
|411||HTTP Length Required||Client.LengthRequired||The server requires that the client include a Content-Length specification in the request. This typically occurs when uploading data to the server.|
|413||Entity Too Large||Server||
The request exceeds the maximum permitted size.
|414||URI Too Large||Server||
The length of the URI exceeds the maximum allowed length.
|500||Internal Server Error||Server||
An internal error occurred. The request could not be processed.
The HTTP request method is not GET, HEAD, or POST.
|502||Bad Gateway||Server||The document requested resides on a third-party server and the server received an error from the third-party server.|
The number of connections exceeds the allowed maximum.
|Envoyer votre avis sur cette page par email.||Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1|