There's a patch and suggested solutions here:
This is based on a few bug reports that included the same error message.