It looks as though the User Account you are trying to specify as the Administrator Account of the new portal already exists.  It then looks like it is trying to associate the new Portals Administrator role to this user, but is having trouble as the password you have entered doesn't match the existing users password.

Try creating the portal again, but with a different user name.

P.S. You may want to remove the portal folder it creates before it gets to this point, (check out the root DNN directory and the /Portals directory)

Hope this Helps,

Yeah, thats what i thought at first as well...

I have tried creating the user first and then adding a protal, i have also tried creating a portal first and entering a new user there. both withe same error. i also tried the different portal templates thinking there might be a problem with the club/organization template.

I looked in the portals folder but the app does not get that far before it throws the error.

Scott

 

I cannot create parent portals either after upgrading to 3.0.13, even when adding an entirely new user as the admin. I get the same error as above.

I've seen a few other references to this but apparently it is not a widespread problem.

 

Remember that 3.0.13 now has a minimum length of 4 (I think) characters for the admin username/password you choose when setting up a new portal. If your name/pwd is too short you get that error message.

yeah, i thought about the min length thing as well. but none of the users i was registering violated the 4 character minimum. to be sure i also set the web.config to turn this off

I ran into this same problem. It took over 8 hours to fully debug, and get my portals fixed.

First, check your DNN Users table for a Email column. Some how mine got deleted during the 3.0.13 upgrade.

Also check the stored procedures 'AddUser' and 'UpdateUser' for the email column.

Recompile the entire DNN3 application using nant or visual studio.net

This last step seemed to fix the issue, after I fixed the users tables the stored procedures, I was still getting the same error creating a new user, creating a portal or child portal.

Also, each time you tried to create a user/portal, the info was populated in the aspnet_ tables, if you tried to add a user, it will error out the DNN User Accounts module, because it saw a user in the membership users table, but can't find a match in the DNN users table.

I'm working on a SQL script that will automatically clean up the aspnet_* tables, fix the email column and stored procedures. However the rebuild of DNN I can't script. Check your dll's creation/modification date, all the DotNetNuke dll's should be very close to the same dates.

Finally got back to look at this.

As you write, there is no "Email" column in my Users table. Additionally, there is no reference to an Email column in either sp 'AddUser' or 'UpdateUser'

Looking at Providers\DataProviders\SqlDataProvider\03.00.13.SqlDataProvider, both of the stored procedures mentioned get dropped and recreated. Both reference Email as input values and column names.

So ... I will add modify table users add column Email nvarchar 256, and drop and recreate the stored procs with snippets from this file ...

I suppose also find a way to update Users.Email by crosswalking from the aspnet_membership/aspnet_users tables ...?

 

I did all of the above with the sql script snippets from the provider sql.

I did not recompile the project at all, only added the email column, dropped and recreated the two sp, and pulled email accounts into users with script provided in the provider sql.

Back to pushing out portals.

Thanks for your guidance, Oliver -

Interesting ... after I went into my first created portal after fixing this - a portal I had attempted to create a couple of times before ... the portal was threefold. It had three home pages; one from the portal template, one from the dnn template, one, with all the other pages, from the club/small group template.

I just deleted a bunch of the pages and all looks ok. Created another new template and it's fine. I had looked in the portals table and not seen any reference to the portal after the previous unsuccessful attempts. What a strange thing.

I had this problem with 3.0.13.  I followed the advice given in this portal to add the email field to the users table, I ran the scripts from the SQL Script file to do this.  In addition to adding the email field, I ran the script to copy the email addresses back into it.  I also ran the 2 scripts to recreate the 2 stored procedures listed here in this thread.

Unfortunately after doing all of that I was still unable to create a new portal.  The error message that I kept getting was:

An Error Was Encountered During The Creation Of Your Portal. This May Have Been Caused By Specifying An Incorrect Password For An Existing User Account. Please Verify Your Details Before You Try Again.

Luckily the same day I was messing with all of this I found that 3.1.0 was released.  After not having any luck on my own I figured that installing the new version would most likely fix my problem.  Unfortunately it did not.  After the 3.1.0 upgrade I'm still getting the same error message when trying to create any kind of new portal (child, parent, etc).  I have read all of the comments about making sure the username, password, etc. are all long enough and have done that.  As far as I can tell, I'm not doing anything wrong.  I have 7 portals with my installation and have never had this problem until the 3.0.13 upgrade.

Can somebody PLEASE help me figure out how I can get this working again?  I've got a new portal that I need to start working on like YESTERDAY.

Thanks!

Anybody?

I have been experiencing this as well--which is odd, i don't remember if this started before or after i upgraded to 3.0.12-

 

will moving to 3.0.1 fix this issue? Are other people having this problem--?

I had the same issues when I was testing multiple portals in creation.  I wanted to use the same username but the same error kept getting thrown at me.  My work around was to make sure the username was different then any others I had used, and just to be safe I would just just the site name for all the text boxes.  So I had   USERNAME for username, password, e-mail, etc for a site, and if I did another site I would use a different word for all the text boxes.  This allowed my portals to be created.  To me it seemed like it would search the username in the SQL database and if it found the same name it would not create the portal.  I never found the time to play around and see if I could figure it out.   So my advice, just make sure the username and possible the firstname and lastname are different then any others you've used before.

Ian