FelisLachesis
DIS Veteran
- Joined
- Nov 3, 2014
A friend of mine just had his 180 days open up, going Christmas week, and staying 9 days down there.
We realized I'll be there for a couple days while he's there, and we wanted to book Crystal Palace for The 2nd.
My 180 day window hasn't opened up yet, but his has, and he's trying to book his ADRs. Most everything else he wants he got, but CP is causing an error. He checks for 1/2/18, and the time. The Available Times appears, the time we want shows up. He clicks on that time, and then the error message (with a picture of Lady and the Tramp)
---------------------------
"Sorry for the "Paws""
We seem to have run into a problem booking your dining reservation. Please try again later or call (407) WDW-DINE or (407) 939-3463.
---------------------------
Even taking two people out of the reservation (ignore my girl and me) the message appears. Reducing it to two people or one person still causes the same error.
Booking for 2017 is fine, but I won't be there, then, so that's why we want to book this for 2018.
Any ideas what's causing this error, other than something weird with moving to a new year?
We realized I'll be there for a couple days while he's there, and we wanted to book Crystal Palace for The 2nd.
My 180 day window hasn't opened up yet, but his has, and he's trying to book his ADRs. Most everything else he wants he got, but CP is causing an error. He checks for 1/2/18, and the time. The Available Times appears, the time we want shows up. He clicks on that time, and then the error message (with a picture of Lady and the Tramp)
---------------------------
"Sorry for the "Paws""
We seem to have run into a problem booking your dining reservation. Please try again later or call (407) WDW-DINE or (407) 939-3463.
---------------------------
Even taking two people out of the reservation (ignore my girl and me) the message appears. Reducing it to two people or one person still causes the same error.
Booking for 2017 is fine, but I won't be there, then, so that's why we want to book this for 2018.
Any ideas what's causing this error, other than something weird with moving to a new year?