I have a portal which I recently upgraded from 3.1.1 -> 3.7, and then from 3.7 to 4.5.3.

For the most part things seemed to go very well.

However, I had a report that a portal admin could not log on. I saw two errors in the Event Viewer that indicated "object not found." I investigated the user account and found that she was a member of Admin and Subscriber roles, but not a member of the "Registered Users" role.

When I attempted to add her to the role via the Manage Roles interface, she received an email indicated she had been added to the role, but she in fact was not. No errors were produced by this action.

Anyone have any insight?

Actually, I was mistaken that she wasn't in the "registered users" role ... she is.

I've discovered that the problem is that I had to do a bit of manual removal of portals in the database, since trying to delete them from host | portals gave me errors (object not found) ... I thought (hoped) that some referential integrity in the db would take care of all, but not so. I have a number of user accounts in the aspnet area which I have to remove. And it's not as simple as just finding those that aren't in the dnn users table ... this user, for example, has four entries in aspnet_users as a remnant of early DNN versions.

So - I have to do some careful work to remove them. I think I have figured that the application id in the aspnet_applications is equivalent of the portalid, with the exception that the null portal id in portals would match the 'dotnetnuke' application id in aspnet_applications.

I guess I'll have to find which applicationids exist in aspnet_applications which are orphaned in terms of not matching existing portalids, and then remove all users who, by backtracking joins, are associated with those applicationids.

I'll figure I'll get a cursor going and use the aspnet_users_delete sproc as a template to do it in the correct order.

If anyone has gone before down this path, glad to see any code or listen to any advice.