SRWRuntime Error Codes
Whenever your Red App is interacting with SRWRuntime, one or more runtime errors may occur. When an error occurs, the ServiceContext status is set to errors
. Every error has a code and a description. You can retrieve the errors by calling getErrors() on ServiceContext . Sample code that shows how to call the getErrors() method is shown below.
if(serviceContext.getStatus().equals(ServiceStatus.ERROR))
{
for(IError error : serviceContext.getErrors())
{
logger.severe(error.getCode()" "error.getDescription()); }
}
The list of SRWRuntime errors follows.
Code | Description |
---|---|
AUTH001 |
Authorization failed, caller is not authorized to use the service. |
AUTH003 |
Authorization failed. Action code "ACTION_CODE" is not allowed. |
|
|
BILL002 |
Incorrect request type. |
BILL003 |
Mandatory field is not given. |
BILL004 |
The text field exceeds its maximum length. |
BILL005 |
Currency required when fee, net amount or gross is set. |
BILL006 |
|
|
|
BUS003 |
The service you are trying to register already exists. |
BUS004 |
The service you are trying to unregister is not in the registry. |
BUS005 |
The workflow you are trying to register already exists. |
BUS006 |
The workflow you are trying to unregister is not in the registry. |
BUS007 |
Missing parameters in register request. |
BUS008 |
Missing parameters in unregister request. |
BUS014 |
Event cannot be null. |
BUS015 |
An error occurred while parsing JSON. Please check if it is valid. |
|
|
EMU001 |
Request provided for emulator service is incorrect type. |
|
|
HOST000 |
Host connection exception occurred. Specific details available in error object. |
HOST001 |
Invalid request class provided |
HOST100 |
Host connection exception occurred during locking process. |
HOST101 |
Invalid request class provided during locking process. |
HOST102 |
Provided lock id is owned by a different requestor. |
HOST103 |
Lock already released. |
HOST104 |
Lock already locked by the requestor. |
HOST105 |
Provided lock id is invalid. It does not match previously stored lock id for the requestor. |
HOST200 |
SDS connection failed. |
HOST201 |
Invalid request class provided for SDS connection. |
HOST202 |
Null value for application ID, subset ID or action code. |
|
|
SHDN001 |
Review the Sabre legal advisory about Red App shutdown. |
|
|
STATS002 |
Exceeded threshold value, execution was blocked. |
|
|
SSO001 |
An unknown error occurred. |
SSO002 |
Incorrect request class provided. |
SSO003 |
Null value for service provider ID. |
SSO004 |
Empty response retrieved from Single Sign-On service. |
SSO005 |
An error returned by Single Sign-On service. |
SSO006 |
Unauthorized service usage. |
SSO007 |
Communication layer error occurred. |
|
|
SWS001 |
There is a service error, for example, the service times out or returns an authorization error, or a connection error occurs |
SWS002 |
The service returns an empty response |
SWS003 |
An incorrect type of request is provided |
SWS004 |
The provided payload is null |
SWS005 |
The provided action is null |
SWS006 |
User is not signed-in in Emulator. |
SWS007 |
Connection to Sabre Web Services has timed out. |
|
|
REST2SG001 |
General error occured |
REST2SG002 |
An incorrect type of request is provided |
REST2SG003 |
The provided path is null or empty |
REST2SG004 |
The provided HTTP Method is null or empty |
REST2SG005 |
The provided payload is null or empty |
REST2SG006 |
The provided content type is null or empty |
REST2SG007 |
The provided url is null or empty |
REST2SG008 |
The service returned no response |
REST2SG009 |
The service returned general service error. |
REST2SG010 |
Connection to service has timed out |