Skip Navigation

Errors

In case of communication problem between SR360 and a client application one of the following errors can be returned:

NATIVE000 - Unknown Error. This error is returned when none of the more specific errors can be used.

NATIVE002 - Unauthorized service usage. This error is returned when the application is not authorized to use a service.To avoid this error it is necessary to provide a required authorization entry in the redapp.xml file.

NATIVE003 - Not signed in. This error is returned when user is not signed in to SR360. Many services require you to sign in.

NATIVE004 - Session already locked by different RedApp. This error is returned when the host session is currently locked by different Red App, e.g. when some other Red App have sent a host command and is still waiting for the response.

NATIVE005 - Lock already released. This error is returned when the client application tries to perform an operation on a lock which has been already unlocked. For example, when the client application provides an expired lock ID while sending host command.

NATIVE006 - Invalid locking timeout value. This error is returned when the client application tries to lock a session with invalid lock timeout value. See Messages List for details on session locking requests.

NATIVE007 - Cannot unlock. Session locked by different RedApp. This error is returned when th client application tries to unlock a session which is still locked by another Red App.

NATIVE008 - Threshold exceeded. This error is returned when the threshold specified in the redapp.xml file has been exceeded. In this case, the client application should call the service less often or take steps to increase threshold for your application. See this section for more details.

NATIVE009 - Host problem. Connection error occurred during accessing Sabre Host.