BSB Errors

In a situation where the BSB fails to add or update a booking the system will record the error in the BSB transfer log and provide an alert on the YesBookit screen as well as email notification of the event.

Once the agent OK’s this alert and clicks Save Changes in the booking a brief description of the error will display on the screen.

A more complete description of the error will be seen in the BSB Error email that is automatically generated to the agent:

 Subject: BSB Error:

Booking Transfer to Rockend REST Failed!
Error: Error
Detail: Paul Allen 20/11/2009-12/12/2009 at 43/9-11 Whiting Avenue (YBI-4-839-3 BSB84)
Failed Comparisons:
Compared: 863 RR[20/11/2009-11/12/2009] with YBI[20/11/2009-12/12/2009 and CG[Paul Allen] with YBI[Paul Allen] (1)


In addition, agents have access to the BSB Transfer log inside YesBookit that provides a detailed log of each booking going from the BSB to REST via REST Messenger.

 These errors cannot be overcome by YesBookit and have to be manually corrected. Until the problem is fixed the BSB will report an error every time that particular YesBookit booking is updated. YesBookit ONLY generates booking synchronisation messages when bookings are created, updated, or cancelled. When a booking is cancelled within YesBookit, the corresponding Rockend REST booking is made Inactive.


Troubleshooting Common Error Messages

Below are a number of common BSB Error messages that agents may encounter when they make or update a booking in YesBookit.

 1. Booking Transfer to Rockend REST Failed!

Error:  Booking Cancellation Error – funds require disbursing

Interpretation: The booking record in REST has funds on it so can not be cancelled

Solution: Disburse the funds in REST and then manually cancel the booking or remove the Sundries from the booking in REST prior to cancelling the booking in YesBookit.

 

2. Booking Transfer to Rockend REST Failed!

Error:  Data Locked

Interpretation: The booking record in REST is open so can not be accessed.

Solution: Close the booking record in REST and update the booking again in YesBookit.

 

3.  Booking Transfer to Rockend REST Failed!

Error: No BOID

Interpretation: The property does not have a BOID (Back Office ID) entered in YesBookit

Solution: From Supervisor Home go to Properties > Tariffs click into the relevant property and enter Rockend REST’s PP Key for the property into the BOID field and Save Changes. Return to the booking and update the booking.

 

4. Booking Transfer to Rockend REST Failed!

Error:  Couldn't match with a booking in RR

Interpretation: There is a booking in Rockend REST that does not match either the dates and/or names in the YesBookit booking but that blocks the dates.

Solution: Find the booking in Rockend REST that is blocking the dates and either make it Inactive or if it is a valid booking make changes to the YesBookit booking.

 

5. Booking Transfer to Rockend REST Failed!

Error:  Failed Comparisons

Interpretation: There is a booking in Rockend REST that does not exactly match the dates and/or names in the YesBookit booking but that blocks some or all of the dates in REST

Solution: Find the booking in Rockend REST that is blocking the dates and either fix it or if it is a valid booking make changes to the YesBookit booking.

 

6. Booking Transfer to Rockend REST Failed!

Error:  Data Error has occurred

Interpretation: One of the fields in the booking has a character that REST Messenger does not allow e.g.  &

Solution: Check the fields in the booking and remove the ‘illegal’ character

 

7. Booking Transfer to Rockend REST Failed!

Error:  Bad Response from Rockend REST

Interpretation: There is a possible error or corruption in the REST database

Solution: Contact Rockend

Did this answer your question?