Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 10.0.1 » SQL Anywhere Server - Programming » SQL Anywhere Web Services

Using automatic character set conversion Next Page

Handling errors


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:

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:

NumberNameSOAP faultDescription
301Moved permanentlyServerThe requested page has been permanently moved. The server automatically redirects the request to the new location.
304Not ModifiedServerThe 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.
307Temporary RedirectServerThe requested page has been moved, but this change may not be permanent. The server automatically redirects the request to the new location.
400Bad RequestClient.BadRequest

The HTTP request is incomplete or malformed.

401Authorization RequiredClient.Authorization

Authorization is required to use the service, but a valid user name and password were not supplied.

403ForbiddenClient.Forbidden

You do not have permission to access the database.

404Not FoundClient.NotFound

The named database is not running on the server, or the named web service does not exist.

408Request TimeoutServer.RequestTimeout

The maximum connection idle time was exceeded while receiving the request.

411HTTP Length RequiredClient.LengthRequiredThe server requires that the client include a Content-Length specification in the request. This typically occurs when uploading data to the server.
413Entity Too LargeServer

The request exceeds the maximum permitted size.

414URI Too LargeServer

The length of the URI exceeds the maximum allowed length.

500Internal Server ErrorServer

An internal error occurred. The request could not be processed.

501Not ImplementedServer

The HTTP request method is not GET, HEAD, or POST.

502Bad GatewayServerThe document requested resides on a third-party server and the server received an error from the third-party server.
503Service UnavailableServer

The number of connections exceeds the allowed maximum.