BSB (Booking Synchronisation Buffer) 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 Console Gateway Failed!
Error:  The holiday property is not available over the specified period.
Detail: Erin Barnes 21/08/2009-24/08/2009 at Boronia 1/30 Nettin Circuit (YBI-8-7-264 BSB1157)
Failed Comparisons:
Compared: Inactive=false/518 CG[21/08/2009-24/08/2009]  with YBI[21/08/2009-24/08/2009] and CG[Jason Ting] with YBI[Erin Barnes] (0)


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 Gateway via the CSI. Reports > System Logs > BSB Transfer Log

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 Console Gateway booking is made Inactive.


Troubleshooting Common Error Messages

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


Booking Transfer to Console Gateway Failed!

Error:  The booking file is currently open by a Gateway user.

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

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

 

Booking Transfer to Console Gateway Failed!

Error:  A booking with the specified ID could not be found.

Interpretation: The Console Gateway Booking ID attached to the booking has been corrupted in some way.

Solution: Check the Unlink box on the booking in YesBookit and update the booking. This will allow Console to assign a new Booking ID to the booking.

 

Booking Transfer to Console Gateway 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 Console Gateway’s Property Ref for the particular property into the BOID field and then update the property. Return to the booking and update the booking.

 

Booking Transfer to Console Gateway Failed!

Error:  Invalid PropertyReference

Interpretation: The property BOID in YesBookit does not match the Property Ref. in Console Gateway.

Solution: Change the BOID in YesBookit so that it is identical to Gateway's Property Ref.

 

Booking Transfer to Console Gateway Failed!

Error:  The holiday property is not available over the specified period.

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

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

 

Booking Transfer to Console Gateway Failed!

Error:  Could not allocate booking date

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

Solution: See above

 

Booking Transfer to Console Gateway Failed!

Error:  A booking with this reference already exists.

Interpretation: Console Gateway has re-allocated the same Booking ID to another booking. (Usually only seen if a 'Restore' is done on the Console Gateway database and the Back Office Synchronisation was not disabled in YesBookit)

Solution: Check the Unlink box on the booking in YesBookit and update the booking. This will allow Gateway to assign a new Booking ID to the booking.

 

Booking Transfer to Console Gateway Failed!

Error:  The property is in the process of being booked by another request. Try again.

Interpretation: Another booking for the same property is tying up the Console GW record.

Solution: Update the booking again in YesBookit.

 

Booking Transfer to Console Gateway Failed!

Error:  Failed to insert new contact record.

Interpretation: There may be a field in the booking form that has too many characters for Console GW to accept.

Solution: Check the fields in the booking form in YesBookit and try to identify the offending field. Fix and Update the booking.

Did this answer your question?