this error shouldn't happen (obviously) - was it working for you during testing?