Thanks for confirming. We’re going to have to look into this for 2.0.2; seems an error is being saved into a custom field. If you have an option editor of some kind installed, it may be helpful to clear out your PRO-related options (and wipe all custom fields) and test again to see if the issue resolves.
If not, we’ve got this as a high priority issue for 2.0.2 (which we’re working on now and aim to have out within a couple weeks). Apologies for the delay in the interim.