Emirates booking error
 

I keep getting 'Sorry, seat availability has changed. Please restart the booking process using the Search by Schedule option.' error whenever I want to book a flight. The error has been like that since 3 days ago. How to solve it? I tried Ie and mozilla but with no luck still. T.T

Have you tried different dates / flights?

yup, I did. I suspect it was the route I choose causing the issue. Do I need to call emirates for a fix or they will fix it eventually?

I am having exactly the same problem with returns from BNE. The site is showing availability.

When I book my preferred return I am then getting the "Sorry, seat availability has changed. Please restart the booking process using the Search by Schedule option".

I was already using that anyway. And I have now found that where the returns from BNE are showing availability I get the message whichever flight I try to book.

Call your local office. I once got this when looking to change flights for my original booking. Took the agent almost an hour, and he mentioned something to do with overriding the system.

Took me over 12 days to resolve, just a few tips;-
-Try to find an equivalent ticket on a different date (route/class/ 4 month/12-4 month/ period) when searching by price (I found just 1 week in the whole year).Go through the flight selection process and note the final price.
-Then search by schedule on the same date(s) check the price, initially when I tried, the 'schedule' fare was nearly $100 more than the 'price' fare, this was eventually made the same, but still more expensive than prior to the website upgrade..

Still getting bounced.

I am endeavouring to book via the Schedule option.

I book the outbound (LHR-BNE)without a problem and then get to select the return. Seats are shown as available. I click "select this flight"and get bounced to the same page with this message

Sorry, seat availability has changed. Please restart the booking process using the Search by Schedule option.

Whatever I then click on I get bounced back to the same page/message.
Hopeless

I am not sure what to do because the last time I spoke to customer service I was told that they cannot match the website prices.

Any idea on how long these glitches take to sort or is that a "how long is a piece of string" question?

PS I have cleared cache and am using a different browser. Same old same old.

dogsrock- Yes I used to get the same message, and if you select single journeys for the same flight there is no problem.
After a few email exchanges with Emirates, the system became more consistent, not sure if they did anything or if it was co-incidence.

Got the same problem last week trying to book GLA to SIN return flights for my inlaws.

Used the emirates mobile site and managed to book them their flights.
Then received tickets by email and the tickets are one way.

Luckily I had not closed the booking confirmation screen.

Called emirates they asked me to email a screen capture of my booking confirmation.
Emailed them it and called back.

Online booking problems are dealt with in Dubai. They told me they would investigate taking 2 to 3 days.

This was a week ago now.

My booking now shows the returns as confirmed but the ticket only shows one way.

We are supposed to be meeting my wifes parents in singapore for this trip. Flying from Perth.

We are unable to book anything else for this trip until Emirates fixes the booking.

The hotel we planned to stay at has gone up 30 percent..
We had two rooms on a cruise on hold that we have had to let go.


Are Emirates usually this slow/incompetent when dealing with booking errors caused by their site?

Just a tips which worked 99% by me:

Try to use multiple destinations instead of return. For instance,

KCH to MAN. Instead of choosing return, choose multiple destination and put Kch- Kl - Dubai - Manchester - Dubai- Kl - Kch. That should fix it cause the problems seems to occurred at certain destinations if you buy as a return flights.

Are you guys trying to book flights straight through dubai (airside transit) or are you trying to book via stopovers?

After so many years, how come this error still exists?!