The problem is apparently module settings.  I checked with a core team member who was having the same problem.  I told them to check module settings of the upgraded module vs a new instance of the module.  I am waiting for the steps he actuallly did, but he already told me he fixed his problem from there.

Edit Add - It also involved looking in the ModuleSettings table for those .xml files.

I will set this on the list to investigate for next release.

Below is what Liegh told me he did to fix his error:

i set the moduleID of the erroring mod to the moduleID of the Address settings, then set the new moduleID settings to the erroring moduleID.  Once that was done, i deleted the old settings and then deleted the new instance of the module.  (phew!)

I had to do this by hand as there is a constraint on the modulesettings table.

Russ

Did you go to ...