Ah. This is a somewhat different error than was described in the thread you linked to.
It sounds like you might be getting caught by the bug that was reported here:
The best bet to find out when the fix is released will be to subscribe to the change logs as described here:
