Status Codes and Errors

Error types

Several types of errors are possible.

  • Sabre APIs errors — these types of errors occur within the Sabre APIs infrastructure, and are caused either by clients or Sabre APIs. The infrastructure detects and generates these errors, and returns them as SOAP faults, with or without ebXML headers.
  • Business application errors — Business applications that are situated behind the Sabre APIs infrastructure generate errors which are caused by clients or the Sabre system. They are returned to clients in ErrorRS format.
  • System errors generated by clients — Clients cause these errors which are external to Sabre APIs. They occur in the development environment, and are returned to the client.

Sample error response

Here is a sample SOAP-based Sabre APIs error response:

  1. faultcode — provides a coarse-grained error categorization which contains the string, "Server.SystemFailure," which means that the error was caused by an internal problem/process.
  2. …/StackTrace — provides additional details which contains the string, "USG_SERVICE_IS_BUSY," which is indicative of a throttling related error.
<?xml version="1.0" encoding="UTF-8"?>
    <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
        <soap-env:Header/>
        <soap-env:Body>
            <soap-env:Fault>
                <faultcode>soap-env:Server.SystemFailure</faultcode>
                <faultstring>System is currently unavailable. Please try again later.</faultstring>
                <detail>
                    <StackTrace>com.sabre.universalservices.base.exception.ApplicationException: errors.xml.USG_SERVICE_IS_BUSY
                    </StackTrace>
                </detail>
            </soap-env:Fault>
        </soap-env:Body>

Common errors

When a response contains the <soap-env:fault> node, an HTTP status code of 500 is returned. If no SOAP fault exists, HTTP Status Code 200 is returned. The following table contains a list of the most common error messages that a SOAP API customer is likely to encounter. Please note that this is not a comprehensive list. However, the errors omitted from this list are internal, system-related errors that generally cannot be generated or corrected through client action.

Error string included in …/StackTrace Cause Corrective action

SC_SERVICE_UNAVAILABLE

Internal

  1. The client application needs to stop processing for at least 500 milliseconds before attempting to retry the message.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com.

USG_AUTHENTICATION_FAILED

Invalid credentials presented in SessionCreateRQ

  1. The client application needs to stop processing and the application's credentials need to be checked/corrected.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com for additional assistance.

USG_AUTHENTICATION_
NOT_ALLOWED

Credentials in the request rather than a Binary Security Token

  1. The client application needs to stop processing and the application's SOAP envelope need to be checked/corrected.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com for additional assistance.

USG_AUTHORIZATION_FAILED

Not permitted to access the requested service

  1. The client application needs to stop sending the service call that is generating this error.
  2. Please contact Sabre APIs support at webservices.support@sabre.com for additional assistance.

USG_CONNECTOR_IS_BUSY

 

Internal limit of concurrent requests for a given service family has been reached

  1. The client application needs to stop processing for at least 500 milliseconds before attempting to retry the message.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com.

USG_CONVERSATION_
ID_REQUIRED

eb:ConversationId element is missing or null in SOAP header

  1. The client application needs to stop processing and the application's SOAP envelope need to be checked/corrected.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com for additional assistance.

USG_COULD_NOT_COMPLETE
_REQUEST

Internal

  1. The client application needs to stop processing for at least 500 milliseconds before attempting to retry the message.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com.

USG_IIOP_OBJECT_NOT_EXIST

Internal

  1. The client application needs to stop processing for at least 500 milliseconds before attempting to retry the message.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com.

USG_IIOP_TRANSIENT
_EXCEPTION

Internal

  1. The client application needs to stop processing for at least 500 milliseconds before attempting to retry the message
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com.

USG_INVALID_ACTION

Incorrect service name in the <eb:Action> node of the SOAP envelope

  1. The client application needs to stop processing and the application's SOAP envelope need to be checked/corrected.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com for additional assistance.

USG_INVALID_EBXML

Required ebXML element or attribute is missing or incorrectly formed in SOAP envelope

  1. The client application needs to stop processing and the application's SOAP envelope need to be checked/corrected.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com for additional assistance.

USG_INVALID_SECURITY_TOKEN

Session has been closed or has expired and the Binary Security Token is invalid

  1. The client application needs to stop utilizing this session, and open a new one.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com for additional assistance.

USG_INVALID_SESSION

Occurs when client attempts to use a session in the middle of the close process

  1. The client application needs to stop processing, and the application's workflow needs to be updated to eliminate the simultaneous usage of single sessions.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com for additional assistance.

USG _IS_BUSY

Internal limit of concurrent requests for some combination of PCC/IP/Service name been reached

  1. The client application needs to stop processing for at least 500 milliseconds before attempting to retry the message.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com.

USG_NO_RESPONSE_FROM_
JMSRECEIVER_IN_TIME

Internal

  1. The client application needs to stop processing for at least 500 milliseconds before attempting to retry the message.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com.

USG_PASSWORD_CHANGE
_REQUIRED

Password change is required

  1. The client application needs to stop processing, and the client's CREATE agent needs to reset the application 's password.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com for additional assistance.

USG_PASSWORD_NOTFOUND

<wsse:Password> node is missing or null

for SessionCreateRQ

  1. The client application needs to stop processing and the application's SOAP envelope need to be checked/corrected.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com for additional assistance.

USG_RESOURCE_UNAVAILABLE

Client has exhausted available sessions (TAM pool)

  1. The client application needs to stop attempting to open new sessions and close unused, existing sessions.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com.

USG_SECURITY_ICE_ERROR

Internal

  1. The client application needs to stop processing for at least 500 milliseconds before attempting to retry the message.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com.

USG_SERVICE_IS_BUSY

Internal limit of concurrent requests for a given service has been reached

  1. The client application needs to stop processing for at least 500 milliseconds before attempting to retry the message.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com.

USG_SERVICE_PROVIDER
_ERROR

Internal

  1. The client application needs to stop processing for at least 500 milliseconds before attempting to retry the message.
  2. If step 1 does not resolve the issue, please contact Sabre APIs support at webservices.support@sabre.com.

Errors related to versions

Request payloads must include the Version attribute and valid versions of the APIs being consumed, in the correct format. If the request is successfully processed, the requested version number is returned with the document root element in the response payload. If this requirement is not accurately fulfilled, error messages are returned in the nodes as follows:

Error Cause Corrective action
errors.INVALID_VERSION Returned if the payload sends an invalid version for the Web service Send a valid version for the API in the correct format
errors.MISSING_VERSION Returned if a version is not present Include the following in the document root element of the payload:
  • The Version attribute
  • A valid version number in the correct format

Docs Navigation