...
...
...
| Table of Contents |
|---|
General Overview of Error Handling
...
It is expected that your PMS/CRS/RMS has a robust error handling process. This includes a queuing mechanism and a robust retry strategy.
Please read the below to make sure you have a good understanding on the requirements for error handling over SMX for PMS.
Application Level Error Handling
...
| Code Block | ||
|---|---|---|
| ||
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<OTA_HotelResNotifRS EchoToken="4528545b-f875-5c77-9205-22631b68f15a" TimeStamp="2018-09-28T01:48:44+00:00" Version="1.0" xmlns="http://www.opentravel.org/OTA/2003/05">
<Errors>
<Error Type="4">Authentication failed - PMS {REQUESTORID} does not exist</Error>
</Errors>
</OTA_HotelResNotifRS>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope> |
Solution: Confirm you are sending your messages to the correct web service endpoint for your PMS.
...
| Code Block | ||
|---|---|---|
| ||
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<OTA_HotelResNotifRS EchoToken="4528545b-f875-5c77-9205-22631b68f15a" TimeStamp="2018-09-28T01:47:17+00:00" Version="1.0" xmlns="http://www.opentravel.org/OTA/2003/05">
<Errors>
<Error Type="4">Authentication failed - PMS {REQUESTORID} received request with invalid username/password</Error>
</Errors>
</OTA_HotelResNotifRS>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope> |
Solution: Confirm you are sending your messages to the correct credentials for your PMS/Hotelier.
...
| Code Block | ||
|---|---|---|
| ||
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<OTA_HotelResNotifRS EchoToken="4528545b-f875-5c77-9205-22631b68f15a" TimeStamp="2018-09-28T01:48:28+00:00" Version="1.0" xmlns="http://www.opentravel.org/OTA/2003/05">
<Errors>
<Error Type="6">Inconsistent PMS codes. PMS '{WS_URI}' does not match RequestorID '{REQUESTORID}'</Error>
</Errors>
</OTA_HotelResNotifRS>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope> |
Solution: Confirm you are using the correct RequestorID in your message payload.
...
| Code Block | ||
|---|---|---|
| ||
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<OTA_HotelResNotifRS EchoToken="4528545b-f875-5c77-9205-22631b68f15a" TimeStamp="2018-09-28T01:44:44+00:00" Version="1.0" xmlns="http://www.opentravel.org/OTA/2003/05">
<Errors>
<Error Type="6">PMS {REQUESTORID} is not authorized to access hotel with HotelCode={HOTELCODE}</Error>
</Errors>
</OTA_HotelResNotifRS>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope> |
Solution: Confirm you are using the correct HotelCode in your message payload.
...
The above shows the response for a reservation missing OTA_HotelResNotifRQ / HotelReservations / HotelReservation / ResGlobalInfo / BasicPropertyInfo @HotelCode
Solution: You will need to adjust your implementation to include the missing information/data.
...