The issue seems to be the same as this one here:
The development version of the plugin gives a better error in this case.