Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

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 ...Bizarre registration failures in 6.0Bizarre registration failures in 6.0
Previous
 
Next
New Post
10/5/2011 3:41 PM
 
I've been running a DNN site very successfully for several years now. I have about 18,000 signups.

A couple of weeks ago I upgraded to 6.0 and since then about one signup in 4 is failing. 70 failures so far. Basically the symptoms are that if something is wrong such as duplicate user name or password too short or wrong captcha the user doesn't always get a message to say what is wrong when the click "register". Then when they work out what is wrong themselves (or call us for advice) the signup works, but the firstname/surname/email/displayname are all blank in dnn_users. They often get a message saying "Registration is not currently available" at this point, I think because the email address can't have a confirmation email sent to it, but in fact a dnn_users record has been set up, but without all the handy stuff that makes user management easier.

Does anyone have any idea what could be causing this? The site is 12pay.co.uk if you want to take a look at the signup page. I'd be very grateful for any solution because I can see this causing us a lot of grief in the future if we don't sort it out. We aren't going to be able to send newsletters or password reminders to 1/3 of our clients who've signed up since we upgrade to 6.0.

Tom McClelland
 
New Post
10/5/2011 8:06 PM
 
please check admin->event viewer to see if there were any logged issues. FYI there was an issue in 6.0 where the email address was applying an unnecessary validation that caused registration issues, this was resolved in 6.0.1, i'd recommend an upgrde to the 6.0.2 release (released today) to see if that resolves it

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
10/6/2011 2:38 AM
 
Thanks for the reply. I'm already on 6.0.1. The event viewer logs a failure to send the email, because the "to" field is empty (though the email box contained a valid email address when I clicked register). I can make this happen at will by doing the following:

  1. Attempt to sign up using a user ID that someone else has already taken.
  2. Click "register"
  3. The system displays the message that the user ID has already been used by someone else
  4. Alter the user name to a new unique one. Don't alter anything else.
  5. Click "register" again.
  6. dnn_users gets populated with blank firstname/surname/displayname/email and the following pageload exception occurs because of that (this is the only error recorded in event viewer and it appears to be a symptom rather than a cause)

ModuleId: 454

ModuleDefId: 75

FriendlyName: User Registration

ModuleControlSource: DesktopModules/Admin/Security/ManageUsers.ascx

AssemblyVersion: 6.0.1

PortalID: 0

PortalName: 12Pay

UserID: -1

UserName:

ActiveTabID: 58

ActiveTabName: Register

RawURL: /Register.aspx?returnurl=http%3a%2f%2fwww.12pay.co.uk%2fUserLogin.aspx

AbsoluteURL: /Default.aspx

AbsoluteURLReferrer: http://www.12pay.co.uk/Register.aspx?returnurl=http%3a%2f%2fwww.12pay.co.uk%2fUserLogin.aspx

UserAgent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider

ExceptionGUID: f99b8bfc-cf45-4eaf-8054-cb5db6cb1bc5

InnerException: The parameter 'to' cannot be an empty string. Parameter name: to

FileName:

FileLineNumber: 0

FileColumnNumber: 0

Method: System.Net.Mail.MailMessage..ctor

StackTrace:

Message: DotNetNuke.Services.Exceptions.ModuleLoadException: The parameter 'to' cannot be an empty string. Parameter name: to ---> System.ArgumentException: The parameter 'to' cannot be an empty string. Parameter name: to at System.Net.Mail.MailMessage..ctor(String from, String to) at DotNetNuke.Services.Mail.Mail.SendEmail(String fromAddress, String senderAddress, String toAddress, String subject, String body) 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.ManageUsers.UserCreateCompleted(Object sender, UserCreatedEventArgs e) --- End of inner exception stack trace ---

Source:

Server Name: JANET0201


Tom McClelland
 
New Post
10/6/2011 2:50 AM
 
OK, I've managed to work out the issue. It only happens (and this is a new failure since 6.0 was installed) if page state persistence is set to "memory". I've switched it to "page" and the problem has gone away.

How can I get memory page state persistence back?

Tom McClelland
 
New Post
10/6/2011 5:43 PM
 
please log it as an issue at support.dotnetuke.com

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Bizarre registration failures in 6.0Bizarre registration failures in 6.0


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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out