Hello, guys!

I'm in the middle of the process of upgrading my DNN 3.1.1 site to 3.3.7 and I ran into several problems.

First problem: my site has 5 portals and each portal has many users:
3363          dnn_0
1             dnn_-1
2239          dnn_3
1982          dnn_4
2604          dnn_5
2606          dnn_9

but after an upgrade, it seems that some users have changed their portal:
48            dnn_0
2205          dnn_3
1969          dnn_4
2604          dnn_5
2606          dnn_9
3363          DotNetNuke

Can somebody tell my why is there a new portal named "DotNetNuke" and why did upgrade process "moved" my users around???

Second problem: my 3.1.1 website uses UCanUse PortalMapper for keeping users in sync and it works like a charm. But when I start an upgrade process, I get an error which won't go away until I remove:
<add name="UcuDnnMembershipModule" type="UCanUse.HttpModules.UcuDnnMembershipModule, UCanUse.HttpModules.UcuDnnMembershipModule" />

from the <httpModules> section. After an upgrade, I can't put it back because I get the same error.

Third problem: well, this is more a question: in my 3.1.1 web.config, I configured membership, roles and profile in <memberrolesprototype> section. But, a web.config in 3.3.7 version contains additional sections in <dotnetnuke>: <members>, <roles> and <profiles>. What are they for?

Please, help! Any comments, ideas or good wishes are welcome!

Thanks!

Sebastinan, thank you for your reply.

Can you be more precise in what changes were made in DNN 3.3.0 regarding user handling?

Yes, I do have multiple users: I have 5 portals in my DNN, which means I have 5 applications defined in dbo.aspnet_Applications (plus one application reserved for host accounts). In turn, I'm having the same user defined 5 times in aspnet_Users, once for each aspnet_Application. On DNN level, I'm having each user listed 5 times in UserPortals, once for each portal. Of course, there are users that are not members of all portals (some are members of 3 portals, for example).

So why does new application appears in upgrade process and why do users change portal membership? What does upgrade process do? I really really need to fully understand the membership process in 3.1 and 3.3 beacuse I must make the upgrade. Is there any documentation on the issue?

How would Bulk User Manager tool help me? I should exprt the users prior the upgrade and then import them back after an upgrade? Or somehow else?

Thanks!