Learn More





Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Help: Check and Replace User DB RelationshipsHelp: Check and Replace User DB Relationships
New Post
2/17/2014 4:16 AM

Hello Everyone,

I have a problem with User DB Relationships. It appears that the old style tables (UserPortals and UserProfile) are missing a field which is causing the error below .

It seems like registration is working fine when it is set to public. The user is created, and is able to log in and everything. However, when it is set to "Verified", it doesn't appear to be creating the user properly in the database, causing the user to be placed in the database, but it appears that it doesn't complete the registration process. The user is unable to log into the site, and doesn't receive any sort of registration email or anything.

If I try to delete the users, his email is deleted from dbo.Users but not from dbo.aspnet_Membership. I check this with:

SELECT * (or DELETE) from dbo.aspnet_Membership
where email not in
(select email from dbo.Users)

The problem seem similar to this:

in fact if I run these scripts below, I have 10.884 entries:

SELECT     * FROM  UserProfile WHERE     (UserID NOT IN (SELECT     UserID  FROM          Users))

and also... (13 entries)

SELECT     * FROM  UserPortals WHERE     (UserID NOT IN (SELECT     UserID  FROM          Users))

What are the difference between old and new UserPortals and UserProfile Tables? 

How can I check my Tables to verify the integrity?

Is it possible to correct the database errors and change it to the new UserPortals and UserProfile tables?

Thank you very much for your support,
any help is apreciated
Best regards
















UserAgent:Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko

DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke


InnerException:Object reference not set to an instance of an object.







DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Entities.Users.UserInfo.GetProperty(String propertyName, String format, CultureInfo formatProvider, UserInfo accessingUser, Scope currentScope, Boolean& propertyNotFound) at DotNetNuke.Services.Mail.Mail.SendMail(UserInfo user, MessageType msgType, PortalSettings settings) at DotNetNuke.Entities.Modules.UserModuleBase.CompleteUserCreation(UserCreateStatus createStatus, UserInfo newUser, Boolean notify, Boolean register) at DotNetNuke.Modules.Admin.Users.Register.CreateUser() in \httpdocs\DesktopModules\Admin\Security\Register.ascx.cs:line 412 --- End of inner exception stack trace ---


Name Server:GENERICUK016

New Post
2/17/2014 4:00 PM
AFAIK that's behaviour by design - when a site is using user verification the full user record is not created until the account is verified (the user must do so via the verification email - ) - once verified the user is updated as expected.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
New Post
2/18/2014 1:39 AM
To check the tables, I would use the reports module first to locate the users missing an email address...If I am reading the question right... where email addresses are not entered you would want a sect statement like this...
from users
where email <=' '
then you can go into admin>user accounts, search for the users with no email address and delete or edit the accounts... This may be the long way around it... but you should be able to find them for sure with this..... Let me know if im going in the right direction please....
New Post
2/18/2014 4:11 AM
I just compared with a new install of DNN 7.2.1. There are Foreign Key Constraints from UserPortals, UserProfile, UserRoles and UserPortals on to the users table, with ON DELETE CASCADE, i.e. all your queries should have returned no records. I assume that the FK had not been in place from the beginning and adding it during an upgrade failed due to existing data.
There is, however, no constraint between aspnet tables and dnn users due to the loose coupling of providers, which might result in existing records in aspnet_users / aspnet_membership, where username is not contained in DNN users table - you might delete those records manually. I also suggest to delete orphaned records in other tables and add FK constraints as contained in new installs.

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group   European Network of DotNetNuke Professionals

Speed up your DNN Websites with TurboDNN
New Post
5/21/2015 7:35 AM
Hi [email protected], did you ever resolve this issue?
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Help: Check and Replace User DB RelationshipsHelp: Check and Replace User DB Relationships

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
Try Evoq
For Free
Start Free Trial
a Demo
See Evoq Live
Need More Information?