This just happened to me this morning and I am on Firmware 1.20.
My local distributor/sales rep has no idea how to solve it at this point. It would have been nice if the fix – reboot proceeder would have been posted here, as we are a mid size church, its Sunday morning and we are dead in the water for the day.
Paul
