I'm also getting this error message after the most recent patch (0.32...).
About the same moment of occurance, few minutes after logging in.