I replied to a very similar post a few days ago:
Also, this error is even documented in our knowledge base:
Did you read these already and see if they answer your questions?