DotNetNuke

Re: Cannot Create Child Portal with 3.0.13

robaxx — Wed, 08 Mar 2006 12:08:55 GMT

Was this ever sorted out?

I've just set up DNN 4.02 for multiple parent portal use and have only been able to create one extra parent portal so far. I tried making another just now and it fails with the same error as in this thread.

I have tried using completely new names and passwords, but still no luck. I'm not going to be digging around in the db.. this is a fresh installation, no upgrades or anything.. it should work as is.

Every day a new drama... arghh :(

Thanks for any help with this one,
Rob

P.s. I've just found the same issue going on in the other forums here:
http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/108/threadid/22878/scope/posts/Default.aspx

Re: Cannot Create Child Portal with 3.0.13

JGranade — Sat, 09 Jul 2005 21:37:36 GMT

This may not be your issue, but I had the same problem with 3.1.0. I wanted to use the same "admin" account for all newly created child sites. What was happening is the child portal was getting created but then it would get deleted because it couldn't create/set the admin account. Here's what's happening: In UserController.vb line 505 it checks if the account is a superuser. For me, the account I was trying to assign to all new child sites was indeed a superuser. That sets the "status" variable to "UserAlreadyRegistered". That status does seem to be handled so the userID is never set so -1 is returned. Now when you get back to PortalController.vb line 142 you have no AdministratorID and the newly created child portal is deleted at line 204.

So you could make some changes to UserController.vb so it could be a SuperUser account. I figured the core team had a reason for not allowing SuperUser accounts to be set as the initial site admin so instead I just use the same non-SuperUser account each time I create a child portal and that seems to work fine.

I hope this helps,

John

Re: Cannot Create Child Portal with 3.0.13

CybrEnergy — Tue, 21 Jun 2005 21:33:02 GMT

I tried that too with no luck. Actually, I can see that the users I create are being added to the aspnet_* tables, they just don't get into the real user table. Something is definitely messed up with the tables. I have been posting about this problem in this thread (http://forums.asp.net/924620/ShowPost.aspx) and have determined that somehow during my upgrade to 3.0.13 my tables got wacked.

tm19 wrote:
This is no help to CybrEnergy, but I have to say that iamian's suggestion worked for me.

I was not having the problem with no e-mail column showing, as some have reported, but the darned thing wouldn't create a child portal without throwing up the name error. At first I started out using "Administrator" as a last name, and "admin" as a user name, both of which I already had in the parent portal; the first name and password were different from anything I had already. It was only when I changed every field to some unique name that the child creation went through. I haven't experimented with this enough to find out whether all the fields have to be unique, or just one or two, to prevent this problem appearing (joys of remote hosting).

Thanks iamian.

(using DNN 3.0.13)

Re: Cannot Create Child Portal with 3.0.13

tm19 — Tue, 21 Jun 2005 19:31:33 GMT

This is no help to CybrEnergy, but I have to say that iamian's suggestion worked for me.

I was not having the problem with no e-mail column showing, as some have reported, but the darned thing wouldn't create a child portal without throwing up the name error. At first I started out using "Administrator" as a last name, and "admin" as a user name, both of which I already had in the parent portal; the first name and password were different from anything I had already. It was only when I changed every field to some unique name that the child creation went through. I haven't experimented with this enough to find out whether all the fields have to be unique, or just one or two, to prevent this problem appearing (joys of remote hosting).

Thanks iamian.

(using DNN 3.0.13)

Re: Cannot Create Child Portal with 3.0.13

CybrEnergy — Mon, 20 Jun 2005 18:48:17 GMT

Usernames and passwords are definitely different than anything that exists in the DB currently. That's definitely not the problem.

Re: Cannot Create Child Portal with 3.0.13

nbc — Mon, 13 Jun 2005 16:00:59 GMT

If the log viewer won't come up you have a problem right there. Try going to Portals/_default/Logs and check the size of your log file. You can rename and download it to your local machine to clear the log file and be able to view it on your local machine. It may give some clues to your problem.

Re: Cannot Create Child Portal with 3.0.13

CybrEnergy — Mon, 13 Jun 2005 14:22:56 GMT

jefkem > I've upgraded to 3.1.0 and it has not fixed the problem.

Ian > I've been making sure that the username, password, etc. are all unique (i.e. not in the DB already). Still get the same error message each time regardless of what I put into those fields.

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.

I'm really hoping that I don't have to reinstall DNN to fix this. Actually, considering my recent upgrade, I'm not even convinced that reinstalling will fix this problem. I've been trying to get into the log viewer to see if there are any errors that may help solve the problem, but I can't even get the log viewer page to come up. It just times out each time.

Re: Cannot Create Child Portal with 3.0.13

iamian — Mon, 13 Jun 2005 13:39:10 GMT

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

Re: Cannot Create Child Portal with 3.0.13

jefkem — Mon, 13 Jun 2005 13:28:42 GMT

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--?

Re: Cannot Create Child Portal with 3.0.13

CybrEnergy — Sat, 11 Jun 2005 11:08:26 GMT

Anybody?

Re: Cannot Create Child Portal with 3.0.13

CybrEnergy — Fri, 10 Jun 2005 18:06:58 GMT

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!

Re: Cannot Create Child Portal with 3.0.13

pmgerholdt — Fri, 06 May 2005 12:19:47 GMT

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.

Re: Cannot Create Child Portal with 3.0.13

pmgerholdt — Wed, 04 May 2005 20:51:48 GMT

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 -

Re: Cannot Create Child Portal with 3.0.13

pmgerholdt — Wed, 04 May 2005 20:18:33 GMT

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 ...?

Re: Cannot Create Child Portal with 3.0.13

uzi — Sat, 30 Apr 2005 19:58:19 GMT

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.