Error Response Matrix

Some errors are more common than others, because they involve the data sent in the RQ by the consuming client/API. Other errors are not likely to be returned, as they are due to internal processes outside of the EMD Exchange API, which have auto-correcting capabilities. However, both types are provided in the table below, in case you do see them in your environment.

Error Code	ErrorMessage	Short Text	Reason	Solution
ExchangeEmdRQ Primary Errors
49000	AREX WS Generic Error	PROCESSING ERROR DETECTED - RETRY - (ERC 9400), Exception while invoking getSecurityAttributes FromATH method	There is a problem with your security token	Contact the Sabre APIs Support desk.
49100	AREX WS Validation Error	EMD NOT VALID FOR EXCHANGE	You are attempting to exchange an EMD which is already exchanged	Check coupon status of EMD in Sabre green screen, or by using TKT_Electronic DocumentServicesRQ.
49112	Invalid PNR selection Criteria	CHECK AE ITEM, VERIFY SELECTED AE ITEMS - NO ELECTRONIC TICKET ASSIGNED	This error occurs when the RQ contains a name or segment which causes the internal logic to fail. If no segment is specified, the system assumes all segments	Check PNR in green screen or using GetReservationRQ to verify the content of the PNR. Also check dates of the itinerary segments/flights. If you feel your RQ is valid, but continue to get this response, contact the Sabre APIs Support desk.
49216	AREX WS Generic Error	AIRLINE SYSTEM UNABLE TO PROCESS TRANSACTION AT THIS TIME	Either a connectivity issue on the airline’s side exits, or the EMD is no longer present in the airline’s database. Sabre keeps a record of the EMD for 13 months after issuance, but the airline my delete sooner	Retry the request after a few minutes. If the problem persists, contact the Sabre APIs Support desk.
49700	Post calculation error	NEED FORM OF PAYMENT, UNABLE TO PROCESS- TKTDOC	The result of the exchange will be an additional collection.	Resend RQ using the form of payment element. See section 3.3.1
49801	PSS returned an error while fulfilling the refund	TKT PRT NOT ASSIGNED/USE W*	You are attempting a fulfilment and either the ticket printer is not assigned, or it has run out of EMD stock control numbers	Be sure your session set-up orchestration includes designating to a Sabre ticket printer and/or check with your agency’s Sabre SME to ensure that ticket numbers have been assigned to your PCC.
49901	Invalid PNR RS with missing fields	No PNR in AAA	There is something wrong with the internal orchestration between the PNR service and EMD Exchange service on the Sabre side	Retry request. If the problem persists, contact the Sabre APIs Support desk.
ExchangeEmdRQ Secondary Errors
41002	Connect to server timed out	I/O error: Connect to server timed out; nested exception	Internal server error	Retry fulfillment request. If the problem persists, contact the Sabre APIs Support desk.
9500	AREX WS validation warning	PROCESSING ERROR DETECTED – RETRY – (ERC 9500)	Internal communication error between Sabre and airline	Retry fulfillment request. If the problem persists, contact the Sabre APIs Support desk.
17000-17011	various	EMD module	A step in Sabre’s internal EMD fulfillment process has occurred	Retry fulfillment request. If the problem persists, contact the Sabre APIs Support desk.
17012	Missing agreement between carriers	IetHub EMD module	The carrier does not participate in EMD Exchange, or there is incorrect data in Sabre’s carrier agreement table.	When new airlines are activated for EMD Exchange, you will be notified via Sabre’s Agency eServices. If you feel you have received this error for a valid EMD Exchange participating airline, please contact the Sabre APIs Support desk.
23001-23004	various	EMD Offline File	The background process to create a record of the EMD Exchange transaction for the agency settlement plan (ARC, BSP, etc.) has encountered a problem. If an EMD was issued, it might not be reconcilable with your settlement plan.	Contact the Sabre APIs Support desk.
28000-28001	various	IetHub EMD module	The process which tokenizes and detokenizes credit card numbers has failed and the EMD transaction was not fulfilled	Retry exchange fulfillment request. If the problem persists, contact the Sabre APIs Support desk.
28002-28007	Various	IetHub EMD module	One of the communications processes between Sabre and the carrier has an issue.	Contact the Sabre APIs Support desk.
30001-30010	Various	EMD-BSO module	One of the Sabre internal processes to update the Sabre PNR after the new EMD has been dispensed has encountered a problem.	Check the PNR in Sabre green screen or using the GetReservationRQ service to ensure all the crucial data from the EMD Exchange transaction is present. If data is missing, VOID the EMD resulting from the exchange (within void period), and perform exchange again. If the problem persists, contact the Sabre APIs Support desk.
140001-140009	Various	TKT DS EMD Association	The routine that associates the EMD to the ETKT has encountered a problem.	Check the PNR in Sabre green screen or using the GetReservationRQ service to ensure the ETKT and EMD are correctly associated. If not, VOID the EMD (within void period) and perform the EMD exchange again. If the problem persists, contact the Sabre APIs Support desk.