Thanks for reporting this. Would you mind sending access details for the affected site via our secure contact form so I can locate the source of this error. I tested the upgrade on a few sites before releasing 6.2, so I think this issue may depend on user specific settings. It would be great to solve this so you can continue to update.