Per Dan Tull's comment, I marked this topic as acknowledged (and added bug metadata to the topic) so that we make error checking on this more robust in the future.
The solution to the problem is
here if you encounter it.
Thanks everyone for your help on reporting this one and providing the workaround/solution.