Out of curiosity, did you folks try logging in again after the 3102 error before trying this fix? I've run into 3102 multiple times today, but just trying a second time has gotten me in each time.


Just want to make sure this is a legitimate workaround for the issue, and not people happening to log in normally.